Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0b6
Issue ID
913217
Regression
Yes
Procedurally generated geometry fails to use shaders
Geometry generated using DrawProceduralIndirect API fails to use assigned shaders correctly and returns black output.
Repro steps:
1. Oped attached projects "Scene" scene
2. Enter Play mode
3. In the "Grid resolution" enter 24 and press "Start"
4. See that the object is spawned and it's white/grey
5. Exit Play mode
6. Click on "File" -> "Build Settings" -> "Build and Run" (Build to "Standalone")
7. Press "Play!"
8. In the "Grid resolution" enter 24 and press "Start"
Reproduced with: 5.6.0f3, 5.6.1p1, 2017.1.0b6, 2017.2.0a1
Regression introduced in: 5.6.0f3
Did not reproduce on: 5.5.3p4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Add comment