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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment