Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2017.4
2018.4.0f1
2020.2
Issue ID
1217671
Regression
No
unity_LightColor getting wrong intensity of light when using vertex lights
Reproduction steps:
1. Open the user's attached project ("Lighting.zip")
2. Open any scene from "Assets/Fail" folder
3. Inspect the light blend in the scene
Expected result: Light intensity is set correctly
Actual result: Light intensity is set incorrectly; layered lights can be seen
Reproducible with: 2017.4.38f1, 2018.4.18f1, 2019.3.5f1, 2020.1.0b1, 2020.2.0a3
Note: From the repro project, these light setups do/do not work:
Working:
- 0 Directional 4 Point (Auto)
- 0 Directional 4 Point (Not Important)
- 1 Directional (Auto) 2 Point (Important) 2 Point (Not Important)
- 1 Directional (Auto) 4 Point (Important)
Not Working:
- 1 Directional (Auto) 2 Point (Auto)
- 1 Directional (Auto) 3 Point (Not Important)
- 1 Directional (Auto) 5 Point (Important)
- 1 Directional (Important) 2 Point (Important)
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
- “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
Resolution Note:
Tested URP vertex lighting with stock URP shader and it works as expected. The port of the shader to URP seems to contain some issues causing lights evaluation to be wrong.