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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment