Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in [Package]
master
Issue ID
1317196
Regression
No
[HDRP] When multiple scenes are used, Lighting tab can show incorrect information about Static Lighting
In the lighting tab, we display the Static lighting of whatever scene is active (marked in bold in the hierarchy). However, instead of using the active scene, we use the latest for Static lighting. This can result in misinformation and confusion.
1) Open SceneA
2) Notice:
- The cube receives blue tint
- Static lighting is set to HDRI sky
- Warning on the Visual environment is correct (HDRI)
3) Now additively add SceneB
4) Notice:
- The cube has a red tint because it's affected by the Gradient sky in scene B
- Static lighting is still set to HDRI sky (incorrect information)
- Warning on the Visual environment is correct (Gradient Sky)
Expected: The static lighting is actually using what is set active (bold in the hierarchy) OR We display the correctly display information in the Lighting tab
Actual: UI Lighting tab says HDRI sky is used, in reality, Gradient sky is used.
This is a UX bug that can cause confusion. But I would understand that this can prove to be difficult/risky to implement and not be worth it.
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment