Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
14.0.2
Issue ID
1420168
Regression
No
Inconsistent API Field names for enabling the effect between HDRP Volumes
How to reproduce:
1. Create a new project with the HDRP package
2. Open APITest script
3. Try to enable the Screen Space Reflection Volume by using the ".enabled" field
4. Observe that Screen Space Reflection Volume can be enabled using ".enabled"
5. Try to enable Global Illumination Volume using the same field name
Expected results: Field names with identical purposes match between different Volumes
Actual results: Global Illumination uses ".enable" instead of the previously used ".enabled"
Reproducible with: 2019.4.38f1(7.7.1), 2020.3.29f1(10.9.0), 2021.3.1f1(12.1.6), 2022.1.1f1(13.1.8), 2022.2.0a11(14.0.2)
Notes:
1. This applies to some other Volumes as well - Fog/PathTracing/RecursiveRendering/VolumetricClouds
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:
Reclassified as featured request and added to the backlog