Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.5f1
Issue ID
UUM-6660
Regression
Yes
RTX shaders no longer receive the STEREO_INSTANCING_ON keyword when using SPI VR
Reproduction steps:
- Open the user's attached project
- Enter Play mode
Expected result: No error appears
Actual result: Errors appear in the Console
_Ray Tracing Shader "RaytracedRender_URP": Property "RenderTarget" has mismatching output texture dimension (expected 2, got 5). Dispatching ray generation shader "RaytraceRenderRayGeneration" failed\!_
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
_Ray Tracing Shader "RaytracedReflections_URP": Property "RenderTarget" has mismatching output texture dimension (expected 2, got 5). Dispatching ray generation shader "ReflectionRayGeneration_Forward" failed\!_
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
Reproduced with: 12.1.6 (2021.3.2f1), 12.1.7 (2021.3.5f1)
Not reproduced with: 10.9.0 (2020.3.36f1), 12.1.6 (2021.3.1f1)
Could not test with: 7.7.1 (2019.4.40f1) (project crashes), 13.1.8 (2022.1.6f1), 14.0.3 (2022.2.0a17) (can’t test due to other errors related to cameraColorTarget)
Reproducible on: Windows 11
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
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2021.3.X):
There are no fixes planned for this Bug
Resolution Note (2021.3.X):
The Ray Tracing Shader error is expected in the new version.
We won't allow to bind texture that has a dimension (e.g. RWTexture2DArray) to a shader resources that has another dimension (e.g. RWTexture2D).
This is consistent with other shader types. For example Compute Shaders don't allow this.
Also multi_compile is not supported in raytrace shaders.
#pragma multi_compile _ STEREO_INSTANCING_ON in RaytracedReflections_URP won't do anything.
As a workaround you can create 2 different ray generation shaders, 1 for each type of output - RWTexture2DArray and RWTexture2D and bind the correct render target to the shader resource.