As a Roblox developer, it is currently too hard to …
Use Graphic Level 2 with FFlagRenderUnifiedLighting13.
If Roblox is able to address this issue, it would improve my development experience because …
Every “weak” device that used Graphic Level 2 before, for performance and framerate, can remain on Graphic Level 2.
FFlagRenderUnifiedLighting13 causes Graphic Level 2 to act like Graphic Level 3.
It causes Graphic Level 2 to now do:
- Enable Normal Maps, and other Texture Maps (this would previously only be on Graphic Level 3)
- Enable Sun Rim Light, or whatever it is, (this would previously only be on Graphic Level 3)
Graphic Levels do control and enable more than one feature:
- They can increase the render distance
- Enable more graphic effects, such as bloom, normal maps and etc.
- Change the Particle Rate and the Beam curve smoothness
- most likely some other stuff

FFlagRenderUnifiedLighting13 causes Graphic Level 2, to act like Graphic Level 3. I don’t even know what Graphic Level 3 becomes at this point.
This means that you’d have to go to Graphic Level 1.
But Graphic Level 1, removes Bloom, makes Particle rates even slower and Beams even worser, etc., it’s basically much worser and the render distance probably goes lower as well compared to Graphic Level 2.
But since Graphic Level 2, becomes Graphic Level 3 now… then you’re basically attacking the Graphic Settings. And everyone that uses that Graphic Setting. e.g. on Mobile, etc.
The reason, why I noticed Graphic Level 2 to “become” Graphic Level 3, is because I was “attacked” by this change, pretty much. ![]()
I noticed that the experience worsened, then I realized that the Graphic Level changed its behavior. Why does Graphic Level 2 have to become Graphic Level 3, if you can just go on Graphic Level 3? ![]()
Expand/Collapse
I do hear that Roblox tries to like do something dynamically, but it’s not there yet, and if it’s not there yet, then don’t merge the commit ![]()
And Render Scale is not a solution to this problem. Render Scale will work, but if I want to turn off the pixelated things, then how would I do it, if it’s done forcefully? ![]()