Search Issue Tracker
By Design
By Design in 2.8.X
Votes
0
Found in [Package]
2.8.1
Issue ID
SPLB-358
Regression
No
Spline Bounds from Gizmos are rendered bigger when compared to user implemented Spline Bounds
Steps to reproduce:
1. Open the attached “SplineBoundsBug.zip” project
2. Open the “SampleScene”
3. In the Hierarchy Window select the “Spline” GameObject
4. Open Scene View
5. Enable Gizmos
6. Observe the Scene View
Expected result: Both the red and green bounds of the Spline match
Actual result: The red bounds (from the Splines package) are bigger compared to the green bounds (user implemented)
Reproducible in: 2.7.2 (6000.0.44f1, 6000.1.0b11, 6000.2.0a7), 2.8.0 (6000.0.44f1, 6000.1.0b11, 6000.2.0a7), 2.8.1 (2022.3.63f1, 6000.0.44f1, 6000.0.51f1, 6000.1.0b11, 6000.1.8f1, 6000.2.0a7, 6000.2.0b7)
Reproducible on: Windows 11
Not reproducible on: No other environment 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
- Reuse Collisions Callbacks is not enabled by default when opening a new project with HDRP template
- Bloom and Exposure Artifacting around GameObject appears when setting Scale of Z Axis to 0
- [Android][IL2CPP][ARMv7] Struct field value corrupts when invoking a generic delegate with a large struct by value
- Highlights persist throughout Options Panels in the Rendering Debugger Window
- Typing numbers in Matrix node’s numeric fields stretches Node
Resolution Note:
The bounds of a spline is calculated by enclosing all knots at their control handles. The normally results in a bounds that is a bit larger than the spline itself, but it is also guaranteed to contain the spline, and is fast to calculate.
Resolution Note (2.8.X):
The bounds of a spline is calculated by enclosing all knots at their control handles. The normally results in a bounds that is a bit larger than the spline itself, but it is also guaranteed to contain the spline, and is fast to calculate.