Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Reflection probe bugs have been deprioritized for the current releases as we're looking towards a more holistic solution.
Resolution Note (2023.2.X):
Reflection probe bugs have been deprioritized for the current releases as we're looking towards a more holistic solution.