View Full Version : Object Saver vs Memorizer

11-27-2014, 09:53 AM
I have a level that I am working on that will eventually contain 30 distinct stage. Each stage contains its own scoring that will be added to the total. I want people to be able to revisit them to try and improve their tallied score, so some form of memory is needed.

The scoring will most likely be done with Binary ( know, Blasphemy), so that means I will need something around 316ish bits of precision (10 bits for each stage, and 16 for the final total).

I would like to use the object saver to save each stage score, and perhaps a memorizer for the final score in case I want to use that score somehow into another level later. Does the object saver also save logic? Right now I am getting errors saving profile data whenever I try to use it, so I can't really test.

Using just the memorizers would be fine, but it would mean having a minimum of 11 of them in the level if I share bits from them between sections (e.g. bits 1-10 for stage 1, 11-20 for stage 2). Since we are topped out at 50 labels on the memorizers, this seems a bit much.

Should I go ahead with the memorizers, or wait to see about the object savers? Is there another way to create this memory?

P.S.- Analog isn't out of the question if there is a better way. With the object saver not working it's not really feasible to use it right now, and I would still need to convert to binary to store a value in the final memorizer anyway.

11-27-2014, 01:07 PM
Memorisers will store analog values, so all your scores could be stored on just 1 Memoriser. You can use a Score Sensor to convert your score into an analog value. However, there are other techniques for creation score based analog values that may be more suitable for your particular application.

The Object Saver will save the state (and analog values) of all the components on a circuit board or object that they are attached to. If you're having issues when you use it then it might be a good idea to hold off using it until it gets patched.

11-27-2014, 03:02 PM
good to know! I just always assumed it was pure digital.I'll have to look into analog a bit more then. I know the basics, but will need to figure the best way to store up to around 30-50k. I'm guessing it will likely be dividing down (multiplying by percentages) until I am dealing with the 10000ths level then converting that to a display?

I'll have to look at the score sensor too. I want to avoid using the level score until the end. Can the score sensor be used in a context other than the level score?

11-27-2014, 08:17 PM
The issue you've really got with this is a memorizer can work between levels right?

11-27-2014, 10:16 PM
oh no, I don't mind it working between levels. Being able to carry the final score across levels is actually something I want to do, so I was going to use 1 of them anyway. I just didn't want to use 10 of my 50 to maintain permanence in one level. Now that I know they can take analog signals that makes it much easier. At least until the object savers are sorted out.