Search Issue Tracker
In Progress
Fix In Review for 6000.0.X, 6000.1.X
Fixed in 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
- Error "Light baking failed with error code 5 (Convergence data not available while rendering lightmaps)" thrown in Console when generating lighting for specific GameObjects
- Copy and Paste options for an Animation Property value are disabled in the Right click contextual menu
- Asset is not found when searching the Label "NewLabel" in Search Window
- "Compute dispatch: missing texture ID..." and "Compute dispatch: missing UAV ID..." warnings are thrown after changing the platform in High Definition 3D template
- Text is culled by size when Content Size Fitter is small and rich text is used
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.