Search Issue Tracker
Fixed
Fixed in 6000.0.30f1, 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
- Warning of an unknown Script missing is logged when selecting VFX in Play Mode
- Vertical and horizontal scrollbars appear and disappear when dragging an attribute to a different position within the Shader Graph Hierarchy
- AudioSource.PlayDelayed() does not work with Audio Random Containers
- Compatible with the VFX Graph Shader Graph can't be dragged and dropped into the "Output" block from the Project window
- [Silicon] Freeze/crash on BrotliDecoderDecompressStream when using System.IO.Compression.BrotliDecoder.TryDecompress
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.0a7):
Fixed the Clipping Planes float fields behavior for CameraEditor when using BiRP.
Resolution Note (fix version 6000.0.30f1):
Editor: Fixed the Clipping Planes float fields behavior for CameraEditor when using BiRP.