Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.2
2019.3
2019.3.0b8
2020.1
2021.1
Issue ID
1199915
Regression
No
Blender Meshes get illuminated too brightly when Directional Light Cookie isn't set to "None"
Steps to reproduce:
1. Download and open attached project
2. Open "SampleScene" scene
3. Select "Directional Light" in the Hierarchy window
4. In the Inspector window, change Cookie to "None" (To see how bright the walls should be)
5. Change Cookie back to "cloud_cookie"
Expected outcome: The brightness of both walls in the scene view doesn't change
Actual outcome: The walls in the scene view become much brighter
Reproducible with: 2018.4.13f1, 2019.2.14f1, 2019.3.0f1, 2020.1.0a15
Could not test with: 2017.4 (Project errors when downgrading, assets can not be loaded)
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (2021.1.X):
When using baked lighting, make sure that your second UV channel contains properly authored lightmap UVs. Otherwise, you will experience lightmap artifacts due to badly authored UVs. You can either manually author UVs in a DCC program of your choice, or have Unity generate them for you automatically in the mesh importer settings.
Also, please keep in mind that baked light cookies are only supported in Unity 2020.1 versions and newer.