Search Issue Tracker
Won't Fix
Votes
0
Found in
2.8.2
Issue ID
UUM-134469
Regression
No
"Data Points" +/- buttons not accessible when both "Float Data" and "Data Points" sections are expanded
How to reproduce:
1. Open the attached ”SplinesBug.zip” project
2. Open the “SampleScene“
3. In the Hierarchy tab, select the “Spline” GameObject
4. In the Inspector tab, in the “Spline Container” component, expand the “Float Data“ section
5. In the “Float Data“ section, expand the “Data Points” section
6. Observe the “Data Points” section
Actual result: The +/- buttons of "Float Data" and "Data Points" overlap each other
Expected result: The +/- buttons of "Float Data" and "Data Points" are fully visible
Reproducible with: 2.3.0 (2022.3.71f1), 2.8.2 (6000.0.67f1, 6000.3.8f1, 6000.4.0b8, 6000.5.0a6)
Could not test with: 1.0.1 (2022.2.0a12) (No “Float Data” and “Data points sections”), 2.2.1 (2022.2.0a12) (Multiple missing type/namespace reference errors)
Reproducible on: macOS 15.3.2 (24D81) (M1 Max)
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
- 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 reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.