Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.5.0b5
Issue ID
837471
Regression
No
Realtime GI Lightmaps Not Updated In The First Frame
The scene with only Precomputed Realtime GI enabled fails to display correct lightmap values after loading from a scene with light probes. Realtime GI Lightmaps are not updated in the first frame.The bug does not occur if the scene is loaded first when the standalone build is launched. It is not possible to reproduce the bug in the editor and the issue does not consistently appear. The bug occurs in both color spaces (Linear/Gamma).
It is observed that the scene takes awhile to load the data. Even though a workaround is possible by changing the refreshing mode of reflection probe, the same result can be observed while loading the scene with Realtime GI enabled.
Steps for the reproduction:
1) After opening the project attached in the case, ensure that lighting is built and has lightmaps.
2) Go to File > Build Settings and Build the project.
3) When the standalone build is launched, click on the 'Light Probes' button to load the next scene.
4) Then, click on the Realtime button to load the scene with Precomputed Realtime GI enabled.
5) Observe the bug (May have to switch between the scenes back and forth to reproduce the issue as it does not consistently occur).
Notes:
- This issue demonstrates the combination of two issues. Over-brightness issue is related to #835423
- Workaround is to change the refresh mode of reflection probe from 'On Awake' to 'Every Frame'
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
Add comment