Search Issue Tracker
Duplicate
Votes
0
Found in
Issue ID
1261700
Regression
No
[PLM] Changing the Environment Volume Profile settings does not trigger a new bake
Steps to reproduce:
1. Open an existing HDRP project
2. Navigate to Lighting Settings and bake the lighting
3. Navigate to the Environment tab in the Lighting Settings window
4. Click on the Profile field to select the Volume Profile
5. Begin changing the Volume Profile settings
6. Click on Generate Lighting again
7. Notice that lighting is not rebaked
Notes:
- Affects both the CPU and the GPU lightmappers
- Clearing baked data and rebaking fixes the issue
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Add comment