With the removal of changing fflags locally, will true full screen (Alt + Enter) be added back (not borderless windows (F11)? We currently have to add it manually through this fast flag:
"FFlagHandleAltEnterFullscreenManually"
Additional Information below:
Add support for Fullscreen - Feature Requests / Engine Features - Developer Forum | Roblox
I use fast flags to improve my gameplay experience by changing rendering features so my PC does not explode, i feel like Roblox should keep flags that cant be abused as this might be detrimental to thousands of users who use Fast Flags everyday for a better experience.
So uh, why not to block only some fast flags which are being used to “cheat” in games, instead of blocking ALL fast flags at all. For example, lot’s of them are used to improve roblox perfomance on low-end PC/laptop, and they do really help and work (I can personally confirm this as I use them myself.)
Other than custom framerates, downscaling texture quality, disabling anti-aliasing features, using another lighting engine, and using an older rendering engine, I don’t think these flags are really that useful in any kind of legitimate usage.
Lots of said “performance-improvement” flags could also introduce unfair advantages, and sometimes be used for cheating too, such as:
@Dogekidd2012 Hi, just wanted to point out that "FFlagHandleAltEnterFullscreenManually" used to be false by default until 2021, and then for some reason it was changed to true. It would be great if you could consider setting it back to false by default, since it allows true fullscreen (better input latency and FPS) without needing ClientAppSettings.json every update. Thanks!
Tbh, im not mad at roblox removing FFlags, they were meant to be used only by engineers an staff, not the general userbase.
They first have to fix the bugs that appear with Exclusive Fullscreen (True Fullscreen) before enabling this FFlag and there are quite numerous bugs that occur with this fullscreen mode such as webview pages not appearing.
Also, I thought they added it back, what happened? Did they only add the FFlag back and didn’t enable it officially or meant to enable it officially and never did?
That’s right, however it doesn’t change the fact that these FFlags provide functionality that could be very useful for the general userbase and aren’t available by default. If Roblox actually listened to its userbase and added functionality like advanced graphics quality controls and other useful functionality that FFlags offer nowadays and can’t be compensated then nobody is gonna ask to keep the ability to adjust client FFlags anymore.
You shouldn’t have to meddle with internal flags in order to get good performance on low-end computers.
They aren’t removing all fflags. Specific widely used fflags will be put on a whitelist and ideally implemented as client settings in the future.
Dunno where people got the idea that all flags are being removed from (bloxstrap, matt worded his announcement very poorly, maybe on purpose) but this is not happening according to the aforementioned responses.
No clue why this post would suddenly become active other than that.
If you guys remember, something similar to this happened before on a massive scale to the point where even I got baited into thinking bloxstrap was getting people banned.
Well we do, so I don’t really know what to say about that. The most used performance flag seperates graphics quality and render distance, allowing you to see much farther without adding extra unnececary things since you can barely see anything on low graphics quality. Some games are genuinely unplayable since these are tied together.
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.)
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.