Search Issue Tracker
Fixed
Fixed in 6000.2.0a6, 7000.0.0a20
Votes
0
Found in
6000.2.0a1
Issue ID
UUM-91548
Regression
No
[Rendering Debugger] Results are not updated unless the camera has rendered
Steps to reproduce:
- Open Rendering Debugger
- Open Volume
- Select a Camera that is not rendering and a component from a global scene volume
- Select a parameter in the volume component, change it,
- Result is not updated when the parameter is changed, only the column in the scene parameter.
See attached video : [^2024-12-19 09-04-39.mkv]
Actual results:
Parameter in the Result Column is not updated unless the camera is being rendered
Expected results:
This is a limitation in the Volume debugger, but it should notify that the values might not be updated unless the camera renders.
Reproducible with versions: 6000.1, 7000.0
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
Add comment