feat: route stereo video through eye-specific surfaces#1
Draft
Conversation
This file contains hidden or 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
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.
Summary
RawImagepath inVideoStreamReceiverWhy
The current
RawImageplus customunity_StereoEyeIndexshader path is too brittle on Quest and is the likely reason both stereo views end up alternating or leaking into both eyes. This change moves the actual stereo imagery onto dedicated left/right renderers that can be culled by eye-specific cameras.What changed
RawImagepathIRISStereoLeftandIRISStereoRightNotes
f59927ca446f0b58ffdc78539ae873fb082ec561inPackages/packages-lock.json.