Search Issue Tracker
Fixed
Fixed in 6000.0.59f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1
Votes
0
Found in
6000.0.55f1
6000.1.15f1
6000.2.0f1
6000.3.0a4
Issue ID
UUM-114294
Regression
No
"GPU Time Threshold" in VFX Graph Heatmap Parameters can be set to a negative value
How to reproduce:
1. Open the attached project "VFXAET"
2. Open the "SampleScene" scene and a "New VFX" VFX Graph
3. Set the VFX target to "GameObject"
4. Open the Graph Debug Information tab
5. Navigate to the "GPU Time Threshold" under the VFX Graph Heatmap
6. Try setting the field value to a negative number
Expected results: The field can't be set to a negative number
Actual results: The field can be set to a negative number
Reproducible with: 6000.0.55f1, 6000.1.15f1, 6000.2.0f1, 6000.3.0a4
Reproducible on: macOS Sequoia 15.5 (M1)
Not reproducible on: No other environment tested
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