Search Issue Tracker
Fixed
Votes
0
Found in
2020.3.48f1
2021.3.27f1
2022.1.24f1
2022.3.4f1
2023.1.2f1
2023.2.0a20
Issue ID
UUM-41323
Regression
No
Prefab Editing Environment ambient probe is ignored when entering Prefab Mode
*Steps to reproduce:*
# Download and open the attached project ([^PrefabEnvironmentLightingBug01.zip])
# Open Project Settings > Editor > Prefab Mode,
# Make sure that the Regular Environment field is set to use the PrefabEnvironment scene
# Go to Assets > ExampleAssets > Prefabs
# Select any Prefab asset, and in the Inspector window, press Open
*Expected result:*
* Prefabs inherit ambient probe lighting from the PrefabEnvironment scene
*Actual result:*
* No indirect lighting and reflection data is present, resulting in pitch black shadows, and no reflections
*Notes:*
* Reproduces in: 2019.4.40f1, 2020.3.48f1, 2021.3.20f1, 2022.1.24f1, 2022.3.4f1, 2023.1.0f1, 2023.2.0a20
* Tested in URP on a Windows machine
* Prefab mode in scene context is not affected
* This issue greatly diminishes the usefulness of custom prefab environments. It's nearly impossible to set up a decent lookdev environment for prefabs
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-35086