Search Issue Tracker
By Design
Votes
0
Found in
2018.2.5f1
Issue ID
1081079
Regression
No
Quads inside of a Cube GameObject get lit up incorrectly
How to reproduce:
1. Open the project attached by the user (LightTest.zip)
2. Open the "LightTest" Scene
3. In the Scene View, navigate to the inside of the "Cube" GameObject
4. Notice how the Quads inside are lit up incorrectly and display artifacts
Expected result: The Quads inside are not lit up at all
Actual result: The Quads inside incorrectly and unevenly lit up
Reproducible with: 2017.4.0f1, 2017.4.12f1, 2018.1.9f2, 2018.2.11f1, 2018.3.0b4, 2019.1.0a3
Notes: The problem persists on the "Progressive" Lightmapper settings, but does not reproduce with the "Enlighten" setting. When setting the Lightmapper to "Enlighten", the first bake will still produce the problem, but moving the light a little bit seems to fix it on subsequent bakes.
The rotation of the Light and the Quads doesn't seem to make an impact on the problem, despite what the user reported.
The problem seems to only reproduce with a Cube GameObject, as when the Quads are in other kinds of GameObjects, their lighting behaves normally.
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
- 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
Resolution Note:
The artifacts are caused by double-sided GI not enabled for the enclosing Cube gameobject. thus, leading to invalid lightmap texels for all objects inside of it.