Search Issue Tracker
Fixed in 2021.2.X
Votes
1
Found in
2020.2
2020.2.0b14
2021.1
2021.2
Issue ID
1298508
Regression
No
[GI] Lightprobes are missing when "enter playmode options" is enabled in the Editor
[Update: this bug was initially found in HDRP graphics compositor, but it looks that it is related to light probes]
I have tested this on latest Trunk (2021.2.0a2)
When the "Enter Play Mode Options" are enabled in Editor settings, the LightProbeContext is missing all light probes and the SH coefficients (unity_SHAr, unity_SHAg, etc) that are passed to the shaders are not correct (or consistent with the coefficients when this option is disabled). See the comments for some additional notes.
How to reproduce:
1. Create a new HDRP project
2. Enable the Enter Play Mode Options (Edit -> Project Settings -> Editor)
3. Enter Play Mode
4. Walk to the last room in the Game view (See attached "1298508_repro.mp4")
Expected result: The chair and plant GameObjects are not bright
Actual result: The chair and plant GameObjects are very bright
Reproducible with: 10.2.2 (2020.2.2f1), 11.0.0 (2021.1.0b2, 2021.2.0a1)
Could not test with: 7.5.2 (2019.4.18f1), 8.3.1 (2020.1.17f1) - Graphics Compositor not supported
Note:
- The issue is not reproducible if "Reload Scene" property is checked in the Enter Play Mode Settings
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
- Crash on "The GUID inside 'Assets/asset.png.meta' cannot be extracted by the YAML Parser." when opening the project
- Shadows disappear when looking at a certain angle in Scene view and using Cloud Shadows with Volumetric Clouds
- Tree leafs are not shown in Scene/Game view when using newly created Tree as a Brush on Terrain
- StackOverflowException freezes or silently crashes the Editor
- Microsoft Surface Device freezes when detaching and reattaching physical keyboard attachment to a Microsoft Surface device in Standalone Player for Windows
Resolution Note (fix version 2021.2):
Fixed in 12.0.0 (2021.2.0a18)