Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
2
Found in
2019.4.40f1
2020.3.35f1
2021.3.6f1
2022.2.0b1
2023.1.0a1
2023.2.0a1
2023.3.0a3
Issue ID
UUM-1554
Regression
No
[XR SDK] Scene is not rendered to HMD when using Camera.SetTargetBuffers()
Reproduction steps:
1. Open the attached project ("1346277Repro.zip")
2. Open the "Scene" scene
3. Select "Main Camera" Game object
4. Make sure the "Disable VR On Play" component Disable property is set to false
5. Enter Play mode
Expected result: Scene is rendered
Actual result: Both eyes are rendered black
Reproducible with: 2019.4.28f1, 2020.3.13f1, 2021.1.14f1, 2021.2.0b2, 2022.1.0a1
Not reproducible with: 2018.4.36f1 (XR SDK not available)
Tested:
- MockHMD
- Oculus Rift S
Notes:
- With Multi Pass rendering mode both eyes are rendered black
- In Single Pass Instanced rendering mode left eye is rendered grey, right eye black
Comments (1)
-
sewy
Jul 26, 2022 14:53
Any ETA on this? It was reproduced by Unity a year ago and it is bummer for VR developers. We cannot ship good VR games with half of the functionality bugged due to low prio.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The issue doesnot happen with the unity version after 2023.1 anymore, it is fixed. The user provided script also has issues with the latest releases, and it needs to be updated accordingly.
Resolution Note (2023.3.X):
The issue doesnot happen with the unity version after 2023.1 anymore, it is fixed. The user provided script also has issues with the latest releases, and it needs to be updated accordingly.