Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3.0a12
2019.4.0f1
2020.2
Issue ID
1262917
Regression
Yes
LightProbe asset data is replaced by the currently opened Scene values when switching to a different Scene
How to reproduce:
1. Open the attached project's Scene labeled "LightProbe32"
2. Inspect the LightProbe assets, located in the "Scene" folder
3. Switch to the Scene labeled "EmptyScene"
4. Inspect the LightProbe assets, located in the "Scene" folder again
Expected result: LightProbe asset data doesn't change based on the currently opened Scene
Actual result: LightProbe asset data change based on the currently opened Scene
Reproducible with: 2019.3.0a12, 2019.4.4f1, 2020.1.0b16, 2020.2.0a18
Not reproducible with: 2018.4.25f1, 2019.3.0a11
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
Resolution Note (fix version 2020.2):
Fixed in Unity 2020.2.0a21
Resolution Note (fix version 2020.1):
Fixed in Unity 2020.1.5f1 and above
Resolution Note (fix version 2019.4):
Fixed in Unity 2019.4.10f1 and above