fix(volumetrics): adapt depth slices to max distance #981
No reviewers
Labels
No labels
Context: Bug
Context: Enhancements
Platform: Android
Platform: Linux
Platform: Web
Platform: Windows
Platform: iOS
Platform: macOS
Release
Target: CI
Target: CLI
Target: Dependency
Target: Engine
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
SakulFlee/Orbital!981
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/volumetric-adaptive-depth"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Scales the froxel depth-slice count with the configured maximum distance.
The flicker pattern was not caused by max distance directly; it was the fixed number of depth slices being spread over a larger world-space range:
That matches the observed “flicker interval” growing with max distance.
The renderer now targets roughly 0.15 world units per depth slice for the normal quality tiers:
X/Y resolution still follows
VolumetricQuality;Customquality keeps its explicit grid size. This preserves the longer range while keeping short spot cones stable.Validation
cargo test -p orbital_renderer --all-targetspasses.cargo check --workspacewith the workspace clippy driver and-D warningspasses.rustfmt --checkpasses.Related: #976, #978, #979.
Smart test results
Result: PASS
Scope: orbital_renderer
Reason: directly changed crates
Elapsed: 2m 26s
Workflow run
Overall: 17 tests, 17 passed, 0 failed, 0 skipped
Nextest: 17 tests, 17 passed, 0 failed, 0 skipped
Doctests: no tests reported