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
- Mouse inputs cannot be inputted when searching the Shortcuts Menu by type "Shortcut"
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
Add comment