If so then we should have a better graphics settings menu, i know some people who are on true potato low end devices that struggle with seeing anything in front of them because of the way graphics 1 - 3 works, it disrupts your experience a lot in any game that uses any somewhat long-range mechanics, if it should be this way then we should get the option to use a more detailed and customizable menu instead of the simple slider we have right now.
If they just brought this back and fixed it, nobody would be complaining here.
Wow isnât it amazing that local fast flag support is being removedâŚ? Atleast give us the option for no framerate limit, because what is this bs.
I believe videos like from Sharkblox and also several news accounts recently tweeted this. I am not really up to date with this thread but thatâs what i heard
Where did this come from? Are they really removing the ability to use fastflags??
Most people wonât be affected by this except cheaters
Hello, I have a question about the framerate cap feature. Is it possible change the cap using keybinds instead of opening escape menu and switching between 60/120/144/240 values�
There is a fast flag for that. You can re-enable UI hiding.
(Taken directly from the bloxstrap wiki, however this wonât be of much use considering all of them are being removed.)
GUI hiding
Relevant flag(s): DFIntCanHideGuiGroupId
This is a group-based FastFlag, therefore you must be in a Roblox group for it to work. It can be made to work with any group youâre currently in - see the flag editor for that, but if you donât feel like doing that, and want to avoid confusion, you can just join the Bloxstrap group. Here are the following keyboard shortcuts it provides for toggling the visibility of GUI elements.
Key combination | Action |
---|---|
Ctrl + Shift + B | Toggles GUIs in 3D space (BillboardGuis, SurfaceGuis, etc) |
Ctrl + Shift + C | Toggles game-defined ScreenGuis |
Ctrl + Shift + G | Toggles Roblox CoreGuis |
Ctrl + Shift + N | Toggles player names, and other BillboardGuis that show up above a player |
Pro tip: Ctrl + Shift + G + C + N makes for a nice screenshot
Enabling this will show a freecam option in the menu. That option isnât supposed to actually work, so just ignore it.
Iâve been using Alt+Enter for true fullscreen on Roblox since 2019, and back then, you didnât need to install a ClientAppSettings.json
â the "FFlagHandleAltEnterFullscreenManually"
was already set to false
by default. Everything worked perfectly without any manual setup.
Later on, the situation changed. There was a period when Roblox completely removed the "FFlagHandleAltEnterFullscreenManually"
flag from the client itself. I remember the exact version when this happened â it was âversion-da93e2c4e15845b1â.
At that point, even if you manually installed a ClientAppSettings.json
and set "FFlagHandleAltEnterFullscreenManually"
to false
, it still wouldnât bring back true fullscreen, because the flag literally didnât exist anymore in the client release.
We had to reach out to the Roblox client engineering team about it, and around October 2022, a Roblox engineer confirmed that they would re-add the flag back into the client.
https://devforum.roblox.com/t/add-support-for-fullscreen/2014033/29?u=eagisa
So basically, thatâs the history behind it. Hope this clears it up a bit!
Too bad they didnât set it to false
after they have added it back. It would be great for them to fix the bugs related to it and set it to false
by default the moment they plan to remove or limit client ability to adjust FFlags.
Yeah, the reason they didnât set the flag to false
by default when they added it back is because we actually told the Roblox client engineer to just reintroduce the FFlag into the client first â since, like you mentioned, there were still bugs with Alt+Enter and true fullscreen. So we agreed itâd be best if they just added the flag back in, and weâd handle setting it to false
locally through ClientAppSettings.json
. That way, it was completely up to the user and didnât cause issues for everyone by default.
Sadly, what you said is just IMPOSSIBLE, due to how roblox sees itâs future. Hoping for something to change, but for now I mess only with render distance flag, to get 40 FPS with max render distance