Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
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
- Shader Graph Swizzle Node Input/Output and Mask Update Incorrectly After Undo
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
Add comment