Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.1.0a13
2019.3.0f3
Issue ID
1214077
Regression
Yes
[2019.3] Changing lightning settings via API doesn't update them in the Lightning window
How to reproduce:
1. Open the attached project
2. Window > Rendering > Lightning Settings
3. Enable Realtime GI, Baked GI and disable "Prioritize View" under the Lightmapping settings (Progressive CPU lightmapper)
4. GlobalIllumination > Change BakedGI, Mixed B, Pr view
5. Check the Lightning window
Actual result: The values changed via script are not applied to the lightning settings.
Expected result: The values are changed.
Reproducible with: 2019.3.0f6, 2019.3.0a1, 2019.2.20f1, 2019.1.14f1, 2019.1.0a13.
Regression introduced in : 2019.1.0a13.
Not reproducible with: 2020.1.0a21, 2020.1.0a1, 2019.1.0a1, 2019.1.0a12, 2018.4.16f1.
Notes:
- The values are updated if re-import of asset is called.
- Calling window.Repaint() doesn't update the values.
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Resolution Note (fix version 2019.3):
Fixed in 2019.3.5f1