Search Issue Tracker
Fixed
Fixed in 6000.3.5f1, 6000.4.0b5, 6000.5.0a5, 6000.6.X
Votes
10
Found in
6000.0.68f1
6000.2.9f1
6000.3.4f1
6000.4.0b5
6000.5.0a5
6000.6.0a1
Issue ID
UUM-129941
Regression
Yes
APV Probe Adjustment Volume produces artifacts through out the scene
Steps to reproduce:
- Clone the project [https://github.com/iM0ve/Spotlight-HDRP/tree/APV] make sure to use APV branch.
- Open the project, load Main and Day scenes
- Manually add Probe Adjustment Volume as shown in the screenshots OR use the prefab I attached to the ticket.
- Generate Lighting
Actual results:
Lighting artifacts present (trunk.jpg)
Expected results:
No lighting artifacts present (6.0jpg)
Reproducible with versions:
6.2+
I think It broke between 6.0 and 6.1 beta
Not reproducible with versions:
6000.0.64f1
Tested on (OS):
Windows
Notes
- When doing regression testing, might need to remove some packages from the projects manife.json file, so that it would compile with older unity versions.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed incorrect Adaptive Probe Volume baking when Probe Adjustment Volume components with Sample Count adjustments are used.
Resolution Note (fix version 6000.6):
Fixed incorrect Adaptive Probe Volume baking when Probe Adjustment Volume components with Sample Count adjustments are used.
Resolution Note (fix version 6000.5.0a5):
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.4.0b5):
Fixed in 6000.4.0b5
Resolution Note (fix version 6000.3.5f1):
Fixed in 6000.3.5f1