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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Reclassified as featured request and added to the backlog