THE SHORT ANSWER
Roblox has increased the minimum draw distance from 200 to 500 studs at the lowest graphics quality level, with faster ramp-up at early quality tiers. Terrain water now remains transparent at all quality levels, and beams no longer aggressively reduce segments on low-end devices. Changes apply automatically to all experiences; developers should test in Studio and avoid reading SavedQualityLevel, which may be deprecated.
- Minimum draw distance jumps from 200 to 500 studs at quality level 1
- Draw distance at quality levels 2-4 roughly doubles: 800, 1,200, and 1,600 studs respectively
- Terrain water transparency preserved across all quality levels
- Beam segment count no longer scales down aggressively on low-end devices
- UserGameSettings.SavedQualityLevel API slated for deprecation
Roblox has shipped the first concrete step in its long-term plan to let the engine scale graphics quality smoothly across device capabilities. Starting today, the lowest automatic quality level renders geometry out to 500 studs — up from 200 — and the ramp between the first few quality tiers is significantly steeper.
Draw Distance Overhaul
The change is immediate and universal. At the engine's internal quality level 1 (mapped from the player's 1-10 graphics slider), draw distance is now 500 studs. Level 2 jumps to 800, level 3 to 1,200, and level 4 to 1,600. For reference, the old curve sat at 200, 250, 300, and 450 studs across those same four steps. The company cautions that exact numbers may shift as auto-scaling improves, so building around specific stud counts is not recommended.
Water and Beams Get Consistency Fixes
Two visual features that previously degraded hard on low-end hardware now behave more predictably. Terrain water keeps its transparency at every quality level instead of turning opaque. Beams, which used to slash segment counts aggressively as quality dropped, now scale segment count more gradually, preserving shape and motion cues.
What Developers Need to Do
Nothing is required to enable the changes — they apply to every live experience. However, the engineering team recommends three actions:
- Open Studio Settings > Rendering > Editor Quality Level and step through each tier to verify your scenes look correct.
- Check StreamingEnabled target radius; if distant objects still don't appear at higher quality levels, they may simply not have streamed in yet.
- Stop reading UserGameSettings.SavedQualityLevel to gate visual effects. The API is marked for future deprecation because it fights the automatic scaler rather than cooperating with it.
Roadmap Context
Today's update is explicitly framed as a baseline improvement before finer-grained creator controls arrive. The eventual goal is a system where developers can flag which features — lighting, shadows, draw distance, particle density — matter most for their specific experience, letting the engine preserve artistic intent while still adapting to each device. A horror game, for example, might prioritize shadow fidelity over horizon distance.
Feedback on edge cases where auto-scaling still breaks visual intent is being collected on the Developer Forum thread.