Edit: Seems to be caused by an FFlag intended to fix an issue. Added solution to bottom of this post.
Expected Behavior
I’m just editing code in Studio and expect for a successful AutoSave to be created/updated whenever I’m testing. It was working as expected until recently. As of making this post is the first I’ve noticed the saves failing.
Actual Behavior
My last functioning AutoSave is from February 5th, 2022. Anything created after that is 0 KB and therefore cannot be opened.
Any attempt to open these AutoSaves results in this prompt:
I found a very recent post reporting the same issue, but it was in the wrong category (i.e not a bug report):
Issue Area: Studio Issue Type: Other Impact: High Frequency: Constantly
I’m now hearing from multiple other friends on discord that this is suddenly happening for them as well.
If you’re a developer reading this post then you might want to make sure that your auto-saves are working, or else you might be in for a bad surprise when your studio crashes.
Thank you for Bug reporting this, i’ve been using Studio daily for 8+ months now, and i couldn’t report any of the multiple bugs i found since Devforum is not giving ““new”” members permission to do so, so i could only resort to misplaced posts (that one you saw)
I’ve Apparently found a fix tho, open recent version, revert back to an older save, delete everything from older save, paste everything from the recent one there, bug stopped happening.
don’t know if its permanent, but it’s the same place with the same things, but the bug isn’t happening.
Your workaround only applies if you’re editing a game published to the website and have been publishing saves to it (and therefore have older save versions). I generally code from files stored on my computer, so I can’t do that. Even then, the “workaround” is to just to be sure to constantly save to file rather than opening up an autosave after crashing and then continuing to save over the top of it. It’s still pretty frustrating either way, though.
Studio causes my computer to blue screen a lot, so I rely on autosaves pretty heavily.
Any updates on this? is someone looking into it? this is making it impossible for me to work consistently, specially with the amount of crashing that has been happening since some of the early January updates.
This isn’t the fist time something like this happened. Only solution right now is to mash ctrl+s like a maniac until it turns into a reflex. You should also backup your places. I upload mine to an empty discord server every 2-3 days.
is there a way to revert to a previous version because i dont think its your beta features thats the problem
its probably the version itself its still happening to me tho
Disabling the flag fixes the issue. Ironic how it has Fix in it’s name when it breaks something. You can override your fast variables by creating a Folder called ClientSettings in your studio install with a json file called ClientAppSettings.json
Warning: Modifying fast flags may result in data corruption or other strange behaviour as they’re used to control features that are not completely ready yet.
Just tried it out and it worked. You’re my saviour, thanks a ton. I don’t want to mark your answer as a solution yet though because it’s a workaround and I’m hoping for an employee to stumble across this thread and actually fix the issue. I added a quote at the top of my thread pointing to your post though.
Oof. I’m laughing in between the tears caused by all of the code that I lost on the night that I discovered this issue. I’m fine. Really.
