Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
master
Issue ID
1398529
Regression
No
[HDRP] Lighting window shows not the actual settings that would be used for baking, happens in multi scene environments
HDRP uses the last loaded scene to bake sky lighting. The Lighting tab shows the active scenes settings. This leads to confusions.
Repro:
1) Open scene WhiteSky
2) Additively load RedSky
3) Open Lighting settings
4) Notice it shows WhiteSky will be used for baking (which not true)
5) Bake lighting
Result: Scene is baked with red sky
Expected: The scene uses the settings that are actually displayed in Lighting tab (White Sky)
Additionally we have a warning that says that the last loaded scene will be used for baking, preferably we could get rid of the warning and enforce behaviour that would not allow incorrect setups.
Slack discussion of the topic:
https://unity.slack.com/archives/C0108P9UH6H/p1643104955073000?thread_ts=1642163016.058900&cid=C0108P9UH6H
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
- SerializedPropertyChangeEvent is invoked when initially binding PropertyFields in custom Editor
- UI Panel is not visible when HDR and STP filter are enabled
- Crash on GfxDeviceD3D11Base::DrawBuffersIndirect when opening a specific project
- OnTriggerExit2D is called in Play mode when undoing component adding
- Builds fail with "Execution failed for task ':launcher:checkReleaseDuplicateClasses'" error when the newer version of the In-App Purchasing package is installed on a specific project
Resolution Note:
Unfortunately there isn't much we can do with the current system.
Showing and using the active scene in the Env panel is not an option because we don't have that information at runtime and we still need the static sky there. So that would lead to potential discrepancies.
I thought about showing only the "last loaded" as explained in the warning but then, you have no way to cleanup the other scenes if you have more than one, which would lead to the same discrepancies at runtime since we don't control load order.
What we need is a more centralized baking manager where this kind of things could be stored. Until we make more progress on this, we'll postpone this particular case.