If you are using the V1 escape menu (which appears for some people due to Roblox’s A/B testing), when you press escape, the menu fails to show the players connected, and the developer console shows an error.
Edit: updated post title to reflect what was happening more accurately.
This is also happening to me, I can’t leave, nor reset, NOR close Roblox completely.
You can use the Task Manager and find the RobloxPlayerBeta.exe (or Roblox Game Client)and end the process.
To open the Task Manager press CTRL + SHIFT + ESC or CTRL + ALT + DELETE and select the Task Manager option (Windows Only)
same for me… its very annoying
I hope this get’s fixed soon honestly
same with the V1 of the menu (which appears without fflags in some instances since)
Thanks for the report! I filed a ticket in our internal database.
FFlagFixReportButtonCutOff set to true is the reason menus break aswell
You guys are literally using an old unsupported version of the menu (2015 V1) then complain that they’re broken… and no they’re not A/B testing these old menus, you must’ve forced enabled it by adjusting FFlags or by bloxstrap.
why do they still exist if roblox isnt willing to maintain them?
They don’t still exist… the people using them are accessing them through modifying their client by turning on a flag. They are not publicly available unless you do this, which is not recommended.
If they still exist through a flag it must be intentional that they work
Its not like people are using Synapse X to inject the old code in, they are editing a singular XML file to change a “true” to “false”
Playing Roblox in VR still forces the V2 menu, so it wasn’t completely abandoned. They still maintain it to add new VR features.
However, I just tested launching Roblox in VR and the menu worked fine. I’m also unable to get the V2 menu to launch outside of VR; it forces the V1 menu instead, which always breaks from a script error.
So the issue here seems to be with the V1 menu, not V2.
Yeah, I forced enable the V2 menu using the FFlag {"FIntNewInGameMenuPercentRollout3": "1000"} and I am not getting the bug at all.
I got confused by the Bug Report title, my apologies. It only affects the 2015 V1 menu which is no being longer maintained. I think the reason the OP wrote that it is the V2 escape menu that is broken probably has to do with how enabling the V2 menu in Bloxstrap enables the V1 menu instead because the FFlag to enable the V2 menu changed and Bloxstrap didn’t get updated to support it. I also got confused by this.
I am not sure why didn’t Roblox remove the FFlag that enables the V1 escape menu, but the V2 escape menu is still being maintained and used for VR, I apologize for the confusion. Also the bug only affects the V1 escape menu not the V2 menu. The V1 menu isn’t used anywhere which could be the biggest proof that it’s no being longer maintained. It has been completely replaced by the V3 menu since last year. The bug isn’t on an actively maintained and most importantly officially used menu 
Bloxstrap has 3 different warnings when you try to edit the Flags. A bunch of them really don’t play well and can just completely crash your client whenever you open it.
These are not settings. They are not intended to be widely-used. They are internal configuration. They are usually called “Feature Flags” because they enable/disable Features for staged rollout, if it turns out one Feature doesn’t work properly with another or two together makes the client unstable, then it’s very easy to temporary disable them and fix them in the next release… which you see quite a lot if you look hard enough in #bug-reports.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
