Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.2.X
Votes
0
Found in
2018.2.0b5
Issue ID
1044712
Regression
No
Custom Surface Shader does not handle Shadow correctly when used from DrawMeshInstancedIndirect
Steps to reproduce:
1. Open user attached project "DMIIObjects_SurfShader_DebugEnv.zip"
2. Load Scene "ReproScene"
3. Enter Play Mode
4. Toggle the Emission on any of the DMII Materials under Assets/ForceGraph/Materials (e.g. "Mat_Cube_DMII") off and on
Expected result: Shadows should not be switching positions
Actual result: Shadows should are switching positions
Reproduced with: 2017.1.1f1, 2017.2.1f1, 2017.4.5f1, 2018.1.4f1, 2018.0.b8, 2018.3.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment