Search Issue Tracker
Fixed
Fixed in 2022.3.68f1, 6000.0.44f1, 6000.1.13f1, 6000.2.0a4
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 (3)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
JMoschos
Oct 17, 2025 08:42
I appreciate that this has been fixed, but it's frustrating to see the 2022.3.68f1 fix is only available in the Enterprise version. I reported this issue and would really like to be able to use the fix without needing to either upgrade to Unity 6000.x (which may not be feasible for my project right now) or purchase an Enterprise license.
It would be great if critical bug fixes like this could be made available to all 2022.3.x LTS users, not just Enterprise customers. Those of us still on 2022.3.x often have good reasons for not upgrading yet, and it feels counterproductive to lock fixes behind a paywall when community members are actively helping identify issues.
Is there any chance this fix could be included in a regular 2022.3.x release?
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.