The Next Gen Studio Preview is sometimes enabled even though it shows it’s disabled.
I’ve had the same issue with the Next Gen Explorer too.
I’m using Windows 10.
Expected behavior
Beta Features should respect the option in the Beta Features menu.
4 Likes
There are some cases where betas are rolled out to larger and larger groups as we get closer to ship. These should happen in stages and it shouldn’t be a frequent thing. If you had next gen disabled prior to last week it may have been enabled despite having previously been disabled.
That said, if you are seeing it constantly flip on and off, it might be an issue with the registry or settings. It should not be changing frequently.
Except it hasn’t been enabled, it was still disabled. And even then, that shouldn’t happen. If I have it disabled, it should stay disabled.
You can see in the screenshot that I have automatically enable upcoming beta features disabled.
1 Like
Again, this isn’t always going to be the case. As beta periods are coming to an end and the project is readying for launch, we will enable the feature to a wider and wider audience. Think of this as sort of “soft launch” that still has an off-ramp if critical workflows break. There are features (esp. when it comes to HW) that work pretty much everywhere except for a small sliver of users - we’d like to identify those before they break someone permanently on launch and they don’t have an “escape hatch” to move back out of the feature.
Did you read my previous comments carefully?
I disabled both auto-enable upcoming beta features and the feature itself.
I’m saying these options should be either respected or the check box should at least show it’s enabled, which it doesn’t currently.
I did - but as I explained it can be set on. Is it still on after restarts? Does it keep coming back after disabling? What if you enable/disable and shut down and restart? There’s a number of conditions going on here, we can do anything without any information. If its completely disconnected and can’t be turned off, we can take a look - a log will help. Also, do you have any flags overridden?
1 Like
You didn’t ask me to provide you with more information, but sure, I can.
If I just restart studio it does nothing. The check box is off and next gen studio is on.
To disable it, I have to enable it, restart Studio, disable it, and restart Studio again. It doesn’t update the check box like I explained already.
It’s been several days, those logs are already overwritten. And it’s just that the check box is wrong, I don’t see why that would be in the logs anyway.
None.
Logs don’t get overwritten on either client or studio. They’re named by day, hour, and minute since the client/studio instance booted up, at least the last time I checked…
I can confirm that I have this issue aswell, I have next gen explorer ticked off in the Beta features tab, yet sometimes when I open another place file it magically re-enables itself without the box being ticked. However I notice that this issue exists with other Beta features aswell but to a lesser degree.
1 Like
Are there any updates on this? As of now this is still happening and it’s getting pretty annoying at this point…
1 Like
Can you detail which plugins this continually occurs with? Is it just the Explorer or others?
Also, for the place that it happens with, does it “flip flop” between old/new explorer if you go to another place? Is it only one specific place? Does that specific place ever have the old explorer, or sometimes it gets the new one?
It is mainly just the explorer.
Sorry, not to belabor the point, but its important to be specific - if its not just explorer, what other beta’s can it be? The reason I ask is because I know there are some unique rollout stuff the Explorer team has been doing, so want to make sure the problem is specific to that or possibly something odd going on with settings/registry on your side.
2 Likes
I found that the following beta features have this behaviour: unified lighting, next gen explorer and revamped asset manager. The features enabling themselves (despite clearly being turned off in the panel) is random for the most part, BUT I noticed that these issues occur more often when a new place is opened or when a local place file is opened. It can even occur more often when I open a new studio session under a different account and open a different place file from that account than the one I was already working on. I hope this can clear some things up!
However my previous reply only mentioned the explorer because it’s what I use the most, so I noticed that before anything else.
Hi! I’m looking into this further. Can you confirm for me if you’re using multiple accounts on the same computer (or if you have multiple computers with the same account that you use regularly)?
I use multiple accounts for Roblox Studio on the same computer.