Search Issue Tracker
Not Reproducible
Votes
1
Found in
2019.1
2019.1.10f1
2019.2
2019.3
Issue ID
1171519
Regression
No
Baked lighting is rendered black when loading a scene with baked lightmaps from another scene
To reproduce:
1. Open attached project
2. Build and run for Android
Result: baked lightmaps appear completely black, if the scene was loaded from another scene
Reproduced in:2019.1.14f1, 2019.2.1f1, 2019.3.0a11
Reproduced on devices:
VLNQA00122, Samsung Galaxy S9 (SM-G960F), Android 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00219, Samsung Galaxy Note9 (SM-N960U), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00125, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
Note1: could not test on 2019.3 due to errors: "Component could not be loaded when loading game object. Cleaning up!"
Note2: could not test on 2017.4 and 2018.4 due to Lightweight package issues
Note3: Measures that do not help:
•Deleting Library folder
•Clearing GI cache,
•Clearing baked data and Generating again
•Generating lighting via Auto-Generate
•Resetting packages to defaults
•Loading the scene with different methods (Application.LoadLevel, async loading)
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