Search Issue Tracker
By Design
Votes
0
Found in
2023.2.0a20
Issue ID
UUM-42358
Regression
Yes
Ambient Probe no longer updates in realtime
*Steps to reproduce:*
# Download and open attached project ([^AmbientProbeBug01.zip])
# Open SampleScene
# Go to Assets > Materials and select the TreasureIslandWhiteBalanced material
# Change the Rotation property
*Expected result:*
* Ambient lighting and reflections are updated in realtime
*Actual result:*
* There's no ambient lighting in the scene (see the attached videos for reference)
*Notes:*
* Reproduces in: 2023.2.0a20. This was introduced some time in the 2023.2 release cycle
* Does not reproduce in: 2019.4.40f1, 2020.3.48f1, 2021.3.27f1, 2022.1.24f1, 2022.3.4f1, 2023.1.0f1
* Affects URP and Built-in RP
* HDRP uses a custom SkyManager solution, and thus it's not affected
* Ambient probe still updates in realtime when using Gradient and Solid Color modes. Reflections are not updated, though
* In order to get the ambient lighting and reflections working, one would need to bake the lighting. This is not ideal, since lightmap baking is not supported in runtime. It also impairs iteration speed, since updates are no longer realtime
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
- [Android][iOS] The keyboard closes and re-opens when consecutive input fields are selected
- Complex Sub Graph connected to a Voronoi node is ignored when the shader gets applied as a Material
- Compute Shader property not set error when entering play mode with path tracing and PBR sky
- "WebGL Publish" detects WebGL module and allows building when it is installed without restarting the project
- Editor is non-responsive and flickers when multiple Water System instances are enabled
Resolution Note:
Thank you for the bug report.
The Built-In Skymanager was removed based on extensive discussions on its previous (dys)function, the design paradigms that we are choosing to follow and the trade-offs between the previous design and the current state.
Our avoidance of any 'automated' systems is explicit and deliberate and we actually cannot wait until there is an implementation from URP's side of any other such system as we (the Light Transport team) do not control their priorities or roadmap. We prefer to clarify our systems and tools now rather than offer overlapping tools and mixed paradigms in an already overcrowded Editor experience.
I understand that this seems like a 'serious regression' but there is no functionality that has been lost here, in fact the design has been made much more clear. Each scene begins with the default ambient lighting and any change to the lighting, as would be the case with any baked lighting (and this is baked, serialized lighting) will have to be explicitly baked through the Lighting Window.
This workflow avoids confusion as to ambient lighting not being present in various scenarios (prefab view, playmode, etc.) After numerous bug reports to this incidental feature (which was introduced as a bugfix) we have decided to remove it and that decision (for better or for worse) is not something that we can revert at this point.