Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3
2020.1.0a15
Issue ID
1202484
Regression
No
[UI] Lightmap exposure slider affects all the Scene View windows instead of affecting only the active scene view instance
Steps to repro:
1. Open the attached project and 'SampleScene' scene;
2. Make sure that you have 2 active scene views in the Editor layout, if not, add the second one and attach it to the active Editor window;
3. In the Lighting window press "Generate Lighting" button;
4. When the baking is finished, click on one of the Scene view tabs;
5. Set the Lighting Exposure' slider value to -10.
Expected result:
The lighting exposure is changed only for the active Scene view instance.
Actual result:
The lighting exposure is changed for all the active Scene view instances. See attached video.
Notes:
- Reproducible in 2020.1.0a5, 2019.3.0f2;
- The issue was introcuced with the lighting exposure slider that was added in 2019.3;
- Reproducible on Windows 10;
- Toggling lighting exposure behaviour is different when inputting value in the text field and when changing the slider position: in the first case the exposure changes instantly for all the scene views, in the latter it only changes the exposure of the active scene view (expected), however, when the mouse is hovered on another scene view, the exposure of the scene view that's been hovered on is incorrectly rewritten with the changed value for the initially changed scene view.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.