Performance Presets¶
Use presets before touching advanced controls. They are the safest way to get a stable starting point.
Start With This Order¶
BalancedPerformanceif frame rate is unstableQualityif image quality is too low and the GPU has headroomCustomonly after one of the built-in presets is already close
Available Presets¶
| Preset | Best for | Trade-off |
|---|---|---|
| Performance | Integrated GPUs, low-memory systems, and first stability checks | Lowest detail, strongest frame-rate bias |
| Balanced | Most evaluations and day-to-day editing | Middle ground between quality and stability |
| Quality | Strong discrete GPUs and visual review passes | Highest GPU pressure |
| Custom | Targeted tuning after a preset gets close | Requires manual validation |
What Changes Between Presets¶
| Area | Performance | Balanced | Quality |
|---|---|---|---|
| Visible density | Lower | Medium | Higher |
| Distance detail | Shorter | Moderate | Longer |
| Streaming pressure | Lowest | Moderate | Highest |
| Stability bias | Strongest | Balanced | Lowest |
Hardware Expectations¶
| Preset | Typical hardware fit | VRAM expectation |
|---|---|---|
| Performance | Integrated GPUs or smaller discrete GPUs | Lowest |
| Balanced | Mid-range discrete GPUs | Medium |
| Quality | Higher-end discrete GPUs | Highest |
| Custom | Depends on the final settings | User-defined |
These expectations cover the splat system only. The engine, the scene, and any other rendering features still consume additional VRAM.
Choosing a Preset¶
flowchart TD
Start([Start]) --> Stable{Need the safest first result?}
Stable -- Yes --> Balanced[Use Balanced]
Stable -- No --> Headroom{GPU headroom available?}
Headroom -- No --> Performance[Use Performance]
Headroom -- Yes --> Fidelity{Need higher fidelity than Balanced gives you?}
Fidelity -- No --> Balanced
Fidelity -- Yes --> Quality[Use Quality]
Balanced --> CustomCheck{Need targeted tuning after this?}
Performance --> CustomCheck
Quality --> CustomCheck
CustomCheck -- Yes --> Custom[Switch to Custom]
CustomCheck -- No --> Keep[Keep the preset]
When to Use Custom¶
Switch to Custom when:
- a specific parameter combination matters more than the built-in trade-offs
- you are profiling one setting at a time
- the project targets a known hardware profile and you need a tuned configuration
When Custom is active, start from the settings that already work and change one control at a time.
Practical Order¶
- Preset
- Max splat count
- Render distance
- Advanced streaming or sorting controls only if needed
Validate Changes¶
- Use Build / Test / CI Command Reference when you need the maintained validation commands.