Copyright © 2026 Unity Technologies
Thank you for this report. After investigating this we have found that there are two issues at play here. 1) Missing Reflection Probes This is actually as designed. In the traditional Forward and Deferred code paths, we pick only 2 reflection probes per object (there are technical reasons for this choice which I cannot go into here). Generally, this doesn't work very well for large objects. The plane in the attached test project is an example of this. It can only pick 2 reflection probes for the entire plane and this is why some of them seems to be missing in the final rendering. Both Forward+ and Deferred+ have lifted this limitation by picking reflection probes per screen space tile (or cluster) instead of per object. We recommend you switch to either Forward+ or Deferred+ to resolve this issue. Alternatively, you may chop large objects into smaller ones to allow for more fine grained reflection probe picking. 2) Artifacts After Clearing Lighting Data We found that if we bake reflection probes and then clear all lighting data, we would see the blocky artifacts that are mentioned in this bug report. This is indeed a bug and we will investigate this further. In order to simplify the coming investigation and fixing process, we will create a new separate bug report specifically about this issue (i.e. it won't missing problem 1, described above). For this reason, we will close this present bug report.
How to reproduce:
1. Open the “ReflectionProbe.zip“ project
2. Open the “TerrainDemoScene“ Scene
3. Find and focus on the “Plane (1)/Cube (1)“ GameObject
4. Observe the Scene view
Expected result: Reflections look similar to “Plane/Cube“ GameObject and have no artifacting
Actual result: Heavy artifacting and no reflections near the cube
Reproducible in: 2023.1.0a1, 6000.0.57f1, 6000.2.3f1, 6000.3.0b1
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Workaround: Generate the lighting
Note: The behavior is a bit different in 2023.1.0a1 (there is no artifacting), but it looks similar to 6000.0.0f1, so I believe this is an indication of this still being reproducible
Issues you vote on will appear here