Fix darkened texture output in GTFO VR #141
Open
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
onSubmit would return VRCompositorError_TextureUsesUnsupportedFormat when DXGI_FORMAT_R10G10B10A2_UNORM used with oculus HMDs
fix upscaling crashing oculus HMDs
|
I added this in my fork, along other updates and improvements: https://github.com/RavenSystem/VRPerfKit_RSF |
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.
In GTFO VR, we use an ancient version of OpenVR/SteamVR and/or the devs prefer to use full float targets, so we end up with an exotic texture input format -DXGI_FORMAT_R16G16B16A16_TYPELESS
If using VRPerfkit, this resulted in a darkened output.
If we handle this case too and use the 10/10/10/2 output format, we get results identical to the native output.