Search Issue Tracker
By Design
Votes
0
Found in
5.6.1f1
Issue ID
917111
Regression
No
Emissive lights are visible only with LOD 0
To reproduce:
1. Open the project, attached by the tester (emmisiveBug.7z)
2. Open the "Testland 1" scene
3. In the Scene view, focus on Cube_LOD game object
4. Zoom in and out
5. Observe the emmisive lights on the cube
Expected: emissive lights are visible in all LOD levels
Reproduced in 5.6.1f1, 5.6.2f1, 2017.1.0b10, 2017.2.0b1
Could not test for regression due to us not supporting backwards compatibility
By design: LOD0 has a real-time lightmap, which is why the surface shows visible highlights from the emissive spheres surrounding it. LOD1 and up do not have real-time lightmaps but are lit via real-time light probes. The object itself is set to use Blend Probes. That means that the entire LOD1 will receive its indirect lighting via one blend probe which has been interpolated from the closest light probes around it. In order to get more detail, a light probe proxy volume component needs to be added to the LODs and they need to be set to use LPPVs instead of blend probes, then you will get more detailed lighting on the object.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment