Search Issue Tracker
Won't Fix
Unknown (hidden) 2020.3.X, 2021.2.X, 2022.1.X, 2022.2.X, 2023.1.X
Votes
0
Found in
2020.3.31f1
2021.2.16f1
2022.1.0b12
2022.2.0a8
2023.1.0a1
Issue ID
UUM-1343
Regression
No
LIGHTMAP_ON keyword is still active when lightmaps are not used
How to reproduce:
1. Open the attached project "LightMapOffR.zip"
2. Open the "Scene" Scene
3. Open the Lighting window (Window > Rendering > Lighting)
4. Press the "Generate Lighting" button in the Scene tab
Expected result: The LIGHTMAP_ON variant is not selected for rendering
Actual result: The GameObjects appear black, indicating that LIGHTMAP_ON is still enabled but no lightmap is being read
Reproducible with: 2020.3.31, 2021.2.16f1, 2022.1.0b12, 2022.2.0a8
Could not test with: 2019.4.37f1 - due to errors in the Console window
Note: The shader is 'sabotaged' in order to make the keyword state more obvious with a color force to blue
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
- Crash on "block_merge_next" when entering PlayMode in a scene from the "POLYGON War Map - WWI - Low Poly 3D Art by Synty" package
- [Win ARM] URP projects fail to build that have a space in the name
- [Android][OpenGL]Soft Shadows contain artifacts when the OpenGL Graphics API is used
- The particle system prewarm flag is ignored when calling the Start function after the Stop function
- The Scene view flickers when moving around if there are visible Hair Shaders
Resolution Note:
After investigation it turned out this issue was down to some shader keywords being baked into some materials, thus the renderer was always selecting them. Multiple attempts were made to reproduce this outcome but it couldn't be done and seems this might have happened during material updates during engine version changes. The customer was informed the best way to fix this was to manually remove the keywords from the material, which they were happy with as a solution.