Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.1.X
Votes
0
Found in
6000.0.22f1
6000.1.0a7
Issue ID
UUM-82982
Regression
No
[APV] The anti-seam system doesn’t process ShadowMask and SkyOcclusion data
*Steps to reproduce:*
1. Open the attached project.
2. Open the Assets/Scenes/SkyOcclusion.unity scene
3. Look at the GameView with the Camera in the scene
4. Using the Rendering Debugger, Display the Bricks in the Probe Volume section
5. Notice the seams between the purple and orange bricks
6. In the Lighting Window, and Adaptive Probe Volume tab, disable SkyOcclusion and Generate Lighting
7. Notice that the seams are gone
8. Open the Assets/Scenes/ShadowMask.unity scene
9. Look at the GameView with the Camera01 in the scene
10. Using the Rendering Debugger, Display the Bricks in the Probe Volume section
11. Notice the seams between the purple and orange bricks
12. Look at the GameView with the Camera02 in the scene
13. We are now seeing the realtime shadow, since we moved closer to the scene. Notice how the seams are gone, because we are only looking at baked indirect lighting, the anti-seam mechanism works for this.
\\
*Actual results:*
A clear seam is visible between subdivision levels when looking at ShadowMask and SkyOcclusion:
!image-2024-09-25-18-04-53-821.png|thumbnail!
ShadowMask :
!image-2024-09-25-18-04-00-561.png|thumbnail!
*Expected results:*
ShadowMask and SkyOcclusion data should be interpolated between subdivision levels, creating a smooth transition
When only using Baked Indirect, the data is interpolated : !image-2024-09-25-18-06-50-056.png|thumbnail!
\\
*Reproducible with versions:*
*Not reproducible with versions:*
*Can’t test with versions:*
\\
*Tested on (OS):*
\\
*Notes:*
*
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment