Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2020.1.10f1
2020.2
Issue ID
1287846
Regression
No
2020.1 When changing the Environment Lighting's Ambient Color the Prefab's preview color is affected
Note this is an issue in 2020.1 and earlier versions. In 2020.2.0a18 a large preview refactor landed that renders previews in a separate editor process so the user's scene does not affect the preview.
Reproduction steps:
1. Open the user's attached project "PrefabPreviewAmbient.zip"
2. In the Project window open Assets/Scenes/SampleScene
3. In the Project window select Assets/Cube and observe the Prefab preview color in the Inspector window
4. Go to the Lighting window and select the Environment section
5. Change the Environment Lighting's Ambient Color
6. Go back to the Inspector window, right-click the "Cube" Prefab and click Reimport
Expected result: The Prefab preview color in the Inspector window should not change
Actual result: The Prefab preview color in the Inspector window changed
Reproducible with: 2018.4.28f1, 2019.4.13f1, 2020.1.10f1, 2020.2.0a17
Not reproducible with: 2020.2.0a18, 2020.2.b08, 2021.1.0a2
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (2020.1.X):
This issue has been fixed as part of a major refactor in 2020.2.0a18. This refactor cannot be safely backported. So as this is not a regression and its severity is low it will not be fixed at this time. Sorry for the inconvenience this may cause.