Search Issue Tracker
Fixed
Fixed in 6000.0.39f1, 6000.1.0b7, 6000.2.0a4, 7000.0.0a20
Votes
0
Found in
6000.0.37f1
6000.1.0b5
6000.2.0a2
Issue ID
UUM-96983
Regression
Yes
Incorrect numbers appear when typing certain values into Focal Length field
How to reproduce:
1. Open the attached “IN-93491” project
2. Open the “thing” Scene
3. Press on the “Main Camera” in the Hierarchy
4. In the Inspector, change the Focal Length to “2222”
5. Observe the result
Expected result: The numbers enter as typed
Actual result: The numbers differ from the input
Reproducible in: 2023.2.0a14 ,6000.0.37f1, 6000.1.0b5, 6000.2.0a2
Not reproducible with: 2022.3.57f1, 2023.2.0a13
Reproducible on: Windows 11, macOS 15.2 (Silicon)
Not reproducible on: No other environments tested
Note: Occurs with numbers 2, 4, 5, 7, 8, 9
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
Add comment