Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.46f1
2021.3.21f1
2022.2.10f1
2023.1.0b7
2023.2.0a7
Issue ID
UUM-29789
Regression
No
Reflection Probes can end up in an invalid state and stop working
The internal state of a Reflection Probe is not properly reset when it is disabled and enabled. If a Reflection Probe is disabled during an update, the ReflectionProbe::m_IsScheduled will be stuck to true forever. The ReflectionProbe::ScheduleRender() method will then always return the renderID of the previous job that was cancelled when the probe was disabled.
It can easily be reproduced using the attached project.
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
- EnsureRunningOnMainThread error in TessellationJob.ApplyInset
- MultiColumnListView causes a memory leak when repeatedly shown and hidden
- Position Node with Object Space has a wrong value when there are multiple active GameObjects with the same shader
- [URP][RG] Fullscreen blit is not working when Render Graph is enabled
- EditorUserBuildSettings is corrupted when changing Editor version of the project
Resolution Note:
Reflection probe bugs have been deprioritized for the current releases as we're looking towards a more holistic solution.