Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
12.0.0
Issue ID
1319956
Regression
No
[HDRP][DXR] Incorrect passes are rendered when Path Tracing override is enabled
How to reproduce:
1. Open the "AreaLightCulled.zip" project
2. Open the "HDRPShowcasePictures" Scene
3. Select the "DefaultSettingsVolumeProfile" Asset from the Project window
4. Enable "Path Tracing" in DefaultSettingsVolumeProfile
5. Observe the GameObjects in the Scene view
Expected result: Correct passes are rendered
Actual result: Incorrect passes are rendered
Reproducible with: 10.4.0 (2020.3.2f1), 11.0.0 (2021.1.2f1), 12.0.0 (2021.2.0a12)
Could not test with: 7.5.3 (2019.4.24f1) - Due to errors from packages
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:
The reason why they do not appear at all in raster mode is that they are being assigned a material with a null base color alpha