-
Notifications
You must be signed in to change notification settings - Fork 0
Closed
Description
Temporal Antialiasing is once again proving to be problematic in its implementation. When using VK_PRESENT_MODE_IMMEDIATE_KHR the scene looks correctly anti-aliased and is relatively sharp, but the scene visibly jitters around - likely cause by incorrect jitter compensation somewhere in the pipeline.
However, when using VK_PRESENT_MODE_FIFO_KHR the scene looks stable, but aliasing during camera movement becomes particularly bad (I think it's to do with incorrect velocity calculations as a result of camera movement, not to be mistaken with camera looking).
The difference in behavior between the 2 present modes potentially indicates that this is a synchronization issue, though I'm not sure where the source is. Further investigation needed.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels