Search Issue Tracker
Fixed in 2021.3.35f1
Fixed in 2021.3.X, 2022.3.X, 2023.2.X, 2023.3.X, 2023.3.0a11
Votes
0
Found in
2021.3.31f1
2022.3.11f1
2023.1.16f1
2023.2.0b13
2023.3.0a9
Issue ID
UUM-52930
Regression
Yes
Graphics.RenderPrimitives does not work when using Surface Shaders
How to reproduce:
1. Open the “IN-54270_repro“ project
2. Open the “SampleScene“
3. Enter Play Mode
Expected result: “ProceduralSurface“ and “ProceduralRender“ GameObjects look the same
Actual result: “ProceduralSurface“ GameIObject looks incomplete
Reproducible with: 2021.3.30f1, 2021.3.31f1, 2022.3.11f1, 2023.1.16f1, 2023.2.0b13, 2023.3.0a9
Not reproducible with: 2021.3.29f1
Reproducible on: Windows 10
Not reproducible on: macOS
Note: macOS reproduces a different issue (could be related)
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 (fix version 2023.3):
The emulation path for providing vertexbuffers for draws via api that does not provide vertexbuffers handles instancecount correctly.
The shader itself should be changed into
#if !defined(SHADER_TARGET_SURFACE_ANALYSIS)
instead of D3D11 specific tag. That makes it work on all platforms.
Resolution Note (fix version 2022.3):
Graphics: Surface shader path has correct parameters set when emulating vertexbuffers.