-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overwriting the this.context.composer
breaks XR views
#101
Comments
The composer does not support webxr: mrdoob/three.js#18846 We could probably internally switch back to normal rendering when in WebXR to fix that |
Thanks, is there a default way to reset it when we enter/exit XR? |
You can monitor |
Then I assume I would remove pass like |
I have tried removing the UnrealBloomPass here when entering/exiting AR but AR is still not working, not sure if I've missed something else or found a bug?
|
You would need to remove the composer from the context I think |
That's perfect, is good for peace of mind for future changes to the composer if I add more post processing |
We'll have to revisit this at some point for actually using the composer in XR; there's some three samples that actually do that as far as I'm aware. Current stand-alone VR headsets are probably all too weak for in-VR render passes though, so more of a future problem. |
@ROBYER1 could you verify that the latest version works without having to manually remove the composer? |
Confirmed this is now fixed |
Exporter 2.39.3-pre, Unity 2022.1.16f1
Tested on Android Chrome, Xperia 1 Using the below script as PostProcessing.ts in scripts added to a gameobject in the scene, toggling AR view doesn't show the place on surface marker, then pressing the back button in the browser to return to the previous normal 3d view shows the regular view in a squashed cube-shaped window on the bottom half of the screen.
The text was updated successfully, but these errors were encountered: