Updates to Roblox Studio sometimes end up resetting some Studio Settings to their default values and enabling Beta Features without even informing the user. How dare that happen without the users consent, let alone informing them if there’s a technical excuse for doing so (which after so many years is now a void excuse for laziness or neglecting the user’s control of the program they installed and use).
This has been an issue for as long as I’ve been developing on Roblox and is INSANELY FRUSTRATING and damaging to my workflow and violating my customisation and control over the software on my machine that I use.
The most recent change reset my camera speed settings and re-enabled soft snaps, and forcefully enabled the new studio UI, however I’ve had many other settings changed in the past with no pattern in relation to features that are changed in recent updates.
TL:DR Roblox Studio updates should not affect Studio Settings or enable Beta Features, yet do and have for MANY years.
Studio Settings should NOT be tampered with as the user will change them to customise the program to better suit them for many reasons such as accessibility or ease of use.
Beta Features should default to disabled and ONLY the users active choice to go into the beta features settings and enabling a BETA feature should result in them being enabled.
The Next Gen Studio Beta was moved from an opt-in model to an opt-out for Beta channel users model. So it was explicitly run as opt-in from August of last year until now, when it was swapped over. Only users that have the “Auto-enable upcoming features” toggle would have received this Beta. Those without the toggle set will not see any difference.
There’s a lot of settings that can and will change, including Studio Settings and those under game settings/Workspace settings. There are a lot of systems & APIs that are under development, and sometimes this means moving off of old systems and onto new ones. Generally these are done either as “two-phase” (rollout to beta, including Beta channel users, then enable for everyone) or “three phase rollouts” (opt-in, opt-out, release). And some changes are released after targeted testing, wide phase no opt out, etc.
With every rollout we understand there’s potential disruption - and in the case of Next Gen Studio Beta we know the potential for disruption was especially high. That’s why we’ve had it under an opt-in for almost 9 months and waited until the functionality and tooling (custom tabs esp.) were at a state we felt it was ready for a wider audience.
The simplest solution here is to unenroll from the “auto enable” toggle, and then only beta’s you elect to participate in will be enabled (for Studio functionality). Otherwise you will continue to receive all Betas as they move out. To get an idea of what’s coming/what’s been released, keep an eye on the updates forum, and utilize the “:what’s new” feature in Studio.
I have a similar problem. I didnt hceck if it happens for all settings but my language keeps going back to sysytem defaults, no matter how many times i change it (studio in my language has some weirdness in it making it difficult to use sometimes). It started happening like 2 months ago.
My system: WIndows 10
I also found out that i could be the windows user name having language-specific letters in it, but the problem still occurs even after changing the user name
Well that could be a separate issue, but I assure you it wasn’t the intent. What other features were enabled from Beta that you did not explicitly turn on?
And just to clarify - you didn’t set the “auto-enroll” function, and you didn’t see it set (and then later disabled it)? Its never once been set to “on”, yet the next gen studio beta was set to on last week?
I’ve had many features enabled over the years, I don’t remember most of them especially as most are now core features.
I’ve never been aware of the auto-enroll slider, and I rarely go around messing with things I don’t understand, and when I do, I reset them to the default when I notice no difference or a negative result.
How long has the auo-enroll slider been implemented on the platform? Has its default state ever changed, and when implemented and updated what was it set to for existing users (i.e. not new users)?
As far as I’m aware the state shouldn’t change without you changing it., its completely controlled on the client side.
In some cases we do roll out betas to a % of users regardless of the auto-enroll state, and those users can disable the beta from the beta features dialog (it won’t be reenabled unless possibly Studio is uninstalled or the data wiped).
For Next Gen Studio, it seems there was an additional inadvertent roll out for this phase that was only intended for auto-enroll users. So I think that explains why it was suddenly switched on in your case despite not having the auto-enroll flag enabled. That has since been corrected, but either way your turning the beta off will keep the feature off for now until its rolled out to the wider audience prior to ship and turning it on permanently.
I’ve had this issue too. Not only were my script editor and camera configurations changed, but many other properties such as AreUnalignedPartsShown which was enabled out of no where, making studio barley navigable.
Glad to know that I’m not the sole person experiencing this issue.
Even worse, the problem has occured for instance properties in the past too… particularly a year or two ago where the position of text labels within a surface GUI were reset to 0, which broke text in my games for a while until I finally noticed the issue…
From what I know, not sure if it is related or not to this, but the camera speed is resetted whenever I restart my PC or there is an update in studio (I’m a scripter so I don’t use camera a lot).
So e.g.: I always set it to 1, but every so often when I go back checker, its back to a (maybe?) random number other than what I’ve set it to