Search Issue Tracker
By Design
By Design in 2.2.X
Votes
0
Found in [Package]
2.1.0
2.2.0
2.2.1
Issue ID
SPLB-200
Regression
No
Spline Overlay Element Inspector has cut off values when the entered values are longer
How to reproduce:
1. Open any project with Splines installed
2. In Scene Hierarchy create a Spline > Draw Spline Tool
3. Draw a couple of Knots
4. Reenter the tool and select a Knot
5. Enter a long value and see its scientific notation
Actual result: The Overlay menu cuts off some of the Z value
Expected result: The Overlay menu either expands for the whole scientific notation to be readable
Reproducible with: 2.4.0 (2021.3.31f1, 2022.3.11f, 2023.1.16f1, 2023.2.0b14, 2023.3.0a9)
Reproduced on: Windows 11
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration, we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues.
However, we know each case is different, so do please continue to log any issues you find, as well as provide general feedback on our roadmap page to help us prioritize.
Resolution Note (2.2.X):
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration, we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues.
However, we know each case is different, so do please continue to log any issues you find, as well as provide general feedback on our roadmap page to help us prioritize.