Search Issue Tracker
Fixed in 6000.0.30f1
Fixed in 6000.0.X, 6000.1.X, 6000.1.0a7, 7000.0.0a10
Votes
0
Found in
6000.0.25f1
6000.1.0a2
Issue ID
UUM-85583
Regression
Yes
The Camera's Clipping Planes Far value's condition of being greater than the Near value gets enforced when typing the value
Reproduction steps:
1. Create a new project
2. In the Hierarchy window, select the “Main Camera” GameObject
3. Set the Near value of Clipping Planes to 40
4. Try entering any number into the Far value field of Clipping Planes
5. Observe the results
Expected Result: The Far value becomes 40.01 when the field is unfocused and if the Far value is smaller or equal to 40
Actual Result: The Far field value becomes 40.01 when still typing
Reproducible with: 2023.2.0a14, 6000.0.25f1, 6000.1.0a2
Not reproducible with: 2021.3.45f1, 2022.3.51f1, 2023.2.0a13
Reproducible on: Windows 11 Pro
Not reproducible on: No other environments tested
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Long Property names are not truncated in the Add Property dropdown in the Animation window when the Long Property name does not fit
- [iOS] High CPU load when device keyboard is open
- Selected Animation clip in the Animation window changes when the Domain Reload is triggered
- Animation window scrollbar keeps resetting when the scrollbar width is changed after adding an event
- LocalizationSettings.InitializationOperation hangs when re-entering Play Mode with Domain Reload disabled
Resolution Note (fix version 7000.0.0a10):
Editor: Fixed the Clipping Planes float fields behavior for CameraEditor when using BiRP.
Resolution Note (fix version 6000.1):
Fixed the Clipping Planes float fields behavior for CameraEditor when using BiRP.
Resolution Note (fix version 6000.0):
Editor: Fixed the Clipping Planes float fields behavior for CameraEditor when using BiRP.