Track: anti-aliasing — TAA/TSAA, SMAA variants, and runtime controls #969
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
SakulFlee/Orbital#969
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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
Track the remaining anti-aliasing work as one workstream: temporal anti-aliasing (TAA/TSAA), the remaining SMAA variants, and the quality/runtime controls around them.
The renderer currently supports:
OffLow,Medium,High, andUltrapresetsThis issue is the umbrella for deciding which temporal and spatial variants are worth implementing, and in what order.
Goals
TAA / TSAA
Temporal AA needs more than a post-process shader toggle:
TSAA can be treated as the temporal supersampling variant of the same foundation. It should be evaluated for quality and cost before committing to a specific sample count.
Acceptance criteria:
SMAA
SMAA 1x is spatial and is already implemented. Its quality presets are now exposed (
Low/Medium/High/Ultra); see #966.Still to evaluate:
Acceptance criteria:
Runtime controls
Related
Out of scope
This issue does not require implementing every SMAA variant. The outcome may be TAA plus SMAA 1x, with T2x/S2x/4x documented as not pursued if the cost/benefit is poor.
Status from rendering-panel testing:
FloatingPanel::overlayforwarding fix in #972.ModuleRuntimeand produce the expected info-level renderer logs.Next step is a high-contrast AA test view (thin diagonal geometry, tight checker/grid, fixed camera) and a pass/target verification. The log proves the renderer setting changes; it does not yet prove the FXAA/SMAA pass is reaching the presented surface. Shadow-map filtering/PCF is a separate concern from post-process AA.
Add the view-aligned froxel flicker to the TAA scope.
Temporal volumetrics
The volumetric grid is view-aligned and currently has no temporal history. As the camera moves, a short spot cone moves across froxel cells, producing the full/half/none popping still visible at longer ranges. The linear-depth and adaptive-slice fixes reduced the spatial spacing, but did not remove the temporal component.
The TAA/TAA foundation should cover:
This is shared work with the temporal history/reprojection needed by TAA proper.
SMAA and FXAA
SMAA 1x and FXAA are spatial post-process passes. They run on the final LDR scene color and cannot prevent the volumetric cone from popping between frames; they can only smooth the resulting screen-space edges.
So temporal froxel accumulation belongs in the TAA workstream, not the spatial SMAA presets.