Search Issue Tracker
Active
Votes
0
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ScrollView speed is slower when entering Play mode
- UI Builder elements disappear and "Semantic - Unknown template name" error appears when changes to "Template" parameter are saved
- 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"
- ArgumentNullException error occurs when selecting a Camera in the Hierarchy with the Scene view open
- Clicking 'Open Editor Log' through the Console fails to open redirected Logs when relative Log files exist outside of the Project root
Add comment