Search Issue Tracker
Active
Fixed in 6000.0.44f1, 6000.1.13f1, 6000.2.0a4
Under Consideration for 2022.3.X
Votes
1
Found in
2022.3.57f1
6000.0.36f1
6000.1.0b5
6000.2.0a2
Issue ID
UUM-96421
Regression
Yes
Renderers outside Light Probe hull use incorrect Ambient Probe values when "Renderer Light Probe Selection" is set to "Use Ambient Probe" and "Light Probes" on Mesh is set to "Blend Probes"
Reproduction steps:
1. Open the attached “BrokenAmbientProbeValues.zip“ project
2. Open the “SampleScene”
3. Observe the Game view
Expected result: Both Spheres are rendered the same
Actual result: The Sphere on the right, with “Light Probes” set to “Blend Probes”, is rendered dark
Reproducible with: 2022.2.0a1, 2022.3.57f1, 6000.0.36f1, 6000.1.0b5, 6000.2.0a2
Not reproducible with: 2021.3.48f1, 2022.1.0b1, 2022.1.24f1
Reproducible on: Windows 10 (User reported), Windows 11
Not reproducible on: No other environment tested
Notes:
- Also reproduces in the Player
- "Renderer Light Probe Selection" property can be found in Edit > Preferences > Graphics
Comments (2)
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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
unity_1D4395716672639296FF
Feb 13, 2025 10:02
Currently working on 2022.3.20 and I have this issue. Cannot move to Unity 6 so it would be great if it can be fixed in 2022 as well
JMoschos
Feb 05, 2025 08:15
I’d really appreciate it if this fix was also applied to 2022.3.X. It would be a big help for those still on 2022.3.X and not ready to move to 6000.X yet, preventing issues without forcing an upgrade.