FSR 2.2 temporal upscaling and antialiasing #12768
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective
Solution
Wgpu does not have a great interop story with native graphics APIs at the moment. I'm only 30% sure this is in any way sane, and it may break due to horrible race conditions or deadlocks with multithreaded resource access or changes to rendering. I've tried to make it as safe as possible, but it may be breakable if users are doing custom rendering or as the codebase develops over time.
TODO
Changelog
bevy_core_pipeline::FsrPlugin
and associated types which provides a better TAA/TSR solution thanbevy_core_pipeline::TemporalAntiAliasPlugin
. FSR is guarded behind thefsr
feature flag, and it is only supported on certain platforms - read the docs for details.