Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0b10
Issue ID
1143642
Regression
No
Disabling lighting in Scene View does not clear baked lighting resulting in broken view when using Mixed modes
Repro:
01 - Ensure Auto is enabled (Lighting Settings >)
02 - Create a Scene with a cube and a plane.
03 - Make these objects Static.
04 - Set the default directional light to be `mixed` mode.
05 - Wait for lighting precompute to complete.
06 - Disable Scene View lighting using the `sun` icon in the Editor UI.
Note:
Baked components of lighting are retained. In Mixed mode this creates an effect which is very hard to read as this is just indirect. This can be seen in the attached screenshot.
Expected:
The original purpose of this feature, if im not mistaken, was to enable the user to disable distracting / dark lighting so that they could more easily work in the Scene. It's supposed to enable a light locked to the camera as a "headlamp" which then enables easier visibility in such cases.
I'd argue that the current behaviour is undesirable. we should be able to see the Scene with no lighting _at all_. Im not sure of the benefit of disabling just the realtime lights when we retain their baked output.
Notes:
- Reproducible in 2019.2.0a11, 2018.3.12.f1, 2019.1.0f1, 2017.4.25f1.
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:
This issue has been identified as having low priority and has been closed without a fix. If the bug has no workaround and is blocking your production, please feel free to reopen it with any additional information you might have. Sorry for the inconvenience this might cause.