Search Issue Tracker
Duplicate
Votes
1
Found in
6000.0.17f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-79141
Regression
No
Build fails with Error "Shader error in 'Hidden/Core/ProbeVolumeFragmentationDebug': undeclared identifier 'unity_StereoEyeIndex" when building HDRP Scene with Oculus XR or OpenXR plug-in
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/OutdoorsScene.unity” Scene
3. Build and Run
4. Observe the Console window
Expected result: No Errors exist and the build finishes successfully
Actual result: Errors like “Shader error in 'Hidden/Core/ProbeVolumeFragmentationDebug': undeclared identifier 'unity_StereoEyeIndex'“ are present and/or build fails
Reproducible with: 6000.0.17f1
Could not test with: 2021.3.42f1, 2022.3.44f1 (Build fails with Error “BuildFailedException: GraphicSetting's HDRenderPipelineAsset Assets/Settings/HDRPDefaultResources/HDRenderPipelineAsset.asset is a non updated asset”. Updating with HDRP Wizard did not solve)
Reproducible on: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- Deleting the Library folder solves the issue
- Reproducible on a new project with 3D HDRP template after adding Oculus XR or OpenXR
-
Resolution Note:
We investigate the issue carefully, and in this case it seems to be resolved as part of another issue.
Thank you for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Duplicate of another internal issue: UUM-36023: Land integration test for https://jira.unity3d.com/browse/UUM-32717
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
This is a duplicate of issue #UUM-85851