Search Issue Tracker
In Progress
Fix In Review for 6000.0.X, 6000.2.11f1, 6000.3.0b8, 6000.4.0a4
Votes
0
Found in
6000.0.57f1
6000.2.2f1
6000.3.0b1
6000.4.0a1
Issue ID
UUM-116904
Regression
No
Entering a big number into the "Target Frames Per Second" in Profiler's Preferences inconsistently converts it either to 1FPS or 1000FPS
How to reproduce:
1. Create a new Unity project
2. Go to Window -> Analysis -> Profiler
3. Under the "Highlights", Target Frame Time -> Custom -> Target Frames Per Second
4. Enter the number with at least 5 symbols, press enter and observe the results
5. Enter the number with at least 16 symbols, press enter and observe the results
6. Compare the results
Expected results: Both times the shortened number is the same
Actual results: The value is shortened to the 1000 for the first time and to the 1 the second time
Reproducible with: 6000.0.57f1, 6000.2.2f1 , 6000.3.0b1
Reproducible on: macOS Sequoia 15.6 (M1)
Not reproducible with: 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