Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.0f2
Issue ID
896648
Regression
No
Indirect Instanced Rendering does not support Lambertian lighting
When instancing cubes in play mode, the ones that use Indirect Lambert shading become unlit.
Steps to reproduce:
1. Open attached project
2. Enter play mode
3. Observe the bottom line of cubes get instanced with no functional shading
Expected outcome: Using Lambert shading will react to lights and shadows properly
Actual outcome: The cubes that use Lambert shading become unlit, unreactive to lighting
Reproduced on 5.6.0f2, 2017.1.0a6
Unable to test for regression, because script uses Indirect Instace Mesh drawing(Graphics.DrawMeshInstancedIndirect) that is unavailable pre-5.6.x
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (2018.3.X):
User error. Procedural instancing mode disables all instanced properties declared by unity instancing macros. So the surf function in the user's shaders returns a black Albedo color. The Standard lighting model returns a dark grayish ambient color in such case while the Lambert color simply returns black.