Search Issue Tracker
Fixed
Fixed in 6000.0.62f1, 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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment