Quikcsaves are killed on unclean exit
| Case number: | 954892-993115 |
| Topic: | Developer Preview |
| Opened by: | Rav3n_pl |
| Status: | Open |
| Type: | Bug |
| Opened on: | Sunday, July 8, 2012 - 12:30 |
| Last modified: | Thursday, July 26, 2012 - 02:17 |
I step on it few times.
All my scripts are using quicksave 3 for best score, but sometimes on power loss "nothing in quicksave 3" appears hen I try load it.
Restore very best works, but ALL quicksaves are gone.
Assigning to myself. Has this been happening with earlier builds or have you guys just started noticing this?
This is something that has been around since I play.
Only 1 quicksave is available after a crash/hang.
Fresh thing, I think it is somehow related to "eat my hdd space" bug. I never has this b4 (power outage almost every day...)
gotcha, thanks
forgot to actually assign this to myself.
as far as i can tell, the 3 quicksave slots are only distinctly loadable in the same session. if you exit (cleanly or not) you only get the last quicksave. i'll fix this so the save file is different for each slot.
have you guys been able to load your 3 different quicksaves after exiting foldit?
still looking into the bug you ran into that gave the "nothing in quicksave 3" error
Ok, just now lost almost 200pts and top solution...
Save 3 contains some old solution, very best have nothing :( Also unclean exit because of power loss :(
I'm pretty sure all quicksaves are lost whenever you change tracks. It's been like this ever since I've started folding. I've never noticed any quicksaves being saved.
| Status: Open » Open |
This should be fixed when the new devprev gets released. It looks like i has always saved all quicksaves to a single file. Now each slot will be saved to its own file.
Changing tracks won't bring along quicksaves.
Waiting for update... today power loss kill my all day work - I can see I score well but not have solution saved (nothing in slot and very best) on the track :(
In general, you should not rely on quicksaves to store your work. They are intended to be temporary, and conceptually are tied to your session.
Sure, bu why kill very best in the process?
Yes, I had a client C++ runtime error last night that totally lost my Evolver very best. I had been watching the score so I know what the saved high score should have been.
In fact, there were no autosaves of any kind saved for the evolver solution. I had just started working on a shared solution, and had not done any manual saves before it crashed.
In my experience there is at most 1 quicksave file if the game is stopped suddenly.
And that is most of the time not the one I like to see.
Also when you change tracks, quicksaves in the previous track are all gone.