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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
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.