Allow post processes on cameras with output render targets #9109
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RaananW
changed the title
deltakosh
approved these changes
Oct 7, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
XR renders the renderOutputTarget of the camera directly to the device. This was ignored when the post process manager finalized the frame on the XR camera.
To avoid back-compat issues, only rig cameras that have renderOutputTarget defined (i.e. XR cameras) will have the output set to its internal texture..
My recommendation, however, will be to apply this to each camera with a renderOutputTarget. unless I am missing something, this should be the default behavior.
Closing #9038