Search Issue Tracker
Fixed in 2022.2.21f1
Fixed in 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a11
Votes
0
Found in
2021.3.16f1
2022.2.2f1
2023.1.0b7
2023.2.0a8
Issue ID
UUM-29582
Regression
No
Probe volume is not enabled when probe volume settings are enabled
Reproduction steps:
1. Open the “scffhdrp” project
2. Open the “Assets/Sci-Fi Base/Scenes/Scene_HDRP.unity” Scene
3. In the top menu select Window > Rendering > Probe Volume (Experimental)
Expected results: Window is opened and probe volume settings are displayed
Actual results: Window is opened but “The Probe Volume is not enabled. Make sure it is enabled in the HDRP Global Settings and in the HDRP asset in use” error is thrown in the Console
Reproducible with: 2021.3.16f1, 2022.2.2f1
Could not test with:
2020.3.44f1 (com.unity.feature.development: Package [com.unity.feature.development@1.0.1] cannot be found)),
2023.1.0a25, 2023.2.0a3 (there is no “Probe Volume (Experimental)” menu item)
Reproduced on: Intel MacOS 13.1
Note: Settings need to be enabled for the reproduction to occur:
Project Settings > Graphics > HDRP Global Settings > Frame Settings (Default Values) > Camera > Lighting > Probe Volume
Project Settings > Quality > HDRP > Lighting > Light Probe Lighting > Light Probe System > Probe Volumes
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
Add comment