Search Issue Tracker
By Design
Votes
0
Found in [Package]
7.5.1
Issue ID
1292097
Regression
No
[XR SDK] [URP] Custom Render Feature is not initialized when Stereo Rendering Mode is set to Single Pass Instanced
Reproduction steps:
1. Open the attached project ("1292097Repro.zip")
2. Open the "Grass Displacement RenderFeature Demo" scene
3. Make sure XR Plug-in Management->Oculus is enabled
4. Set Oculus Stereo Rendering Mode to Single Pass Instanced
5. Enter play mode
Expected result: Grass is fully rendered
Actual result: Grass is cut off (partially rendered)
Reproducible with: URP 7.5.1, 8.2.0, 11.0.0 (2019.4.16f1, 2020.1.17f1, 2020.2.1f1, 2021.1.0a10)
Could not test with: 2018.4.30f1 (XR SDK not available)
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
- Unity Cloud icon does not appear next to project and does not connect correctly when the project is created with Cloud but closed right after creation
- ScrollerSlider in the Scroller Control is still using UXMLTraits
- Crash on ExtractHandles when shutting down the Editor in a specific scene while Burst jobs are in progress
- Unity Hub closes with no "Project is currently open" window when selecting an already open project from the Projects list
- The Hub freezes indefinitely when copy/pasting a lot of characters in the “Set project display name” Hub window since it has no character limit
Resolution Note:
In the repro project, user script creates the m_GrassDisplacementFX based on the camera descriptor. The m_GrassDisplacementFX later binds to shader as Texture2D.
In XR single pass mode, the camera target descriptor's dimension is texture2DArray. This is the divergent behavior between XR and non-XR. Because of this, m_GrassDisplacementFX is created as texture2DArray and this caused the binding operation to fail.
After modifying the custom code to create m_GrassDisplacementFX as texture2D, custom render feature works as expected.