I was working on my upcoming game when I switched from scripting back to testing, and suddenly everything changed.
Studio crashed — but only on my main account. The window on my alt account, which had a different place open, stayed running with no issues. After I reopened the main place, it loaded and when this process was complete, I was unexpectedly asked to migrate from Compatibility lighting to Voxel lighting.
Yes, that’s right, even though this new experience was created last week with an advanced lighting set-up, it asked me to migrate from an old already sunset system to the substituent Voxel lighting technology. I was confused: I though the components for this migration had already been removed from Studio. I clicked on the “Migrate” button and after the popup closed, I looked at the “Lighting” service and its properties: all the lighting was gone.
ColorCorrections? Disappeared. Properties? Reset. And a RetroTonemapperPreset? Added.
It’s like the modifications never happened in the first place. It was as if Studio treated my experience as an old experience still requiring migration, overwriting all of my changes.
Fortunately, I had saved a local .rblx backup file which was unaffected. This allowed me to copy the instances in lighting from that file back into the Team Create version, which restored my work.
This was a wild ride, and it sure didn’t come out of nowhere. Even before the crash, I noticed lighting disappearing during play testing, despite having no scripts that reset it. At the time, Roblox services seemed unstable (slow loading times with the site) , but the issue was persistent.
I hope this was a one-off bug and won’t happen again, but the behavior was very concerning, so I suggest you look further into this.
Expected behavior
I expect a flawless integration with lighting. I know, problems can arise when rendering in game, but properties or whole instances should never be deleted from the place itself.
A private message is associated with this bug report