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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment