Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.1.0b7
Issue ID
917094
Regression
No
[Forward] Realtime lights set to Not Important do not work with Shadowmask
Realtime lights set to "Not Important" in Render Mode are not computed correctly in Shadowmask/Distance Shadowmask mode.
Steps for reproduction:
1) Download the project "VertexLightingBug.zip" and open the scene "Bug"
2) Generate the lighting in "Subtractive" mode
3) Observe that realtime point light contribute lighting to dynamic object (i.e. Sphere)
4) Change the light mode to "Shadowmask"
5) Observe that realtime point light does not contribute lighting to dynamic object
Notes:
- Lights that have their Render Mode set to Not Important are always per-vertex or SH. Vertex/SH light should be handled in shadowmask/distance shadowmask mode (i.e. occlusion should be computed on the CPU)
- In the reproduction scene, there is one mixed directional light, one realtime point light and there no light probes.
- On the image attached below, plane is light map static, sphere is dynamic
- It works correctly in deferred rendering path, but works incorrectly in forward rendering path.
- Not a regression, realtime lights set to “Not Important” never worked since the introduction of light modes
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crashes in the wild on Vulkan in CreateDepthSurfaceImpl
- Position and rotation of a GameObject with Rigidbody reset when it is enabled and moved in the same Update call and the frame rate is low
- “Ignoring depth surface store action as it is memoryless” warnings thrown when Capturing new Snapshot while in Play Mode
- Certain textures are not loaded when using the "Load texture data on demand" feature
- [Android][OpenGL] The 2DLight is disproportionately bright on some Android devices when OpenGLES3 is used
Add comment