Search Issue Tracker
Fixed
Fixed in 2.5.X
Votes
0
Found in [Package]
2.5.1
Issue ID
SPLB-236
Regression
Yes
Not all Splines are being changed and the “NullReferenceException“ error appears when moving multiple Splines points if Splines contain different Spline Components
How to reproduce:
1. Open the user’s attached “SplineTest.zip” project
2. In the Hierarchy window, select all 3 “Spline” GameObjects
3. In the Scene window, select the Spline editing tool
4. Select points of each Spline and try to move them
5. Observe the results
Expected result: All splines are moved together, and no errors
Actual result: Just the one Spline is moved, and the “NullReferenceException” error appears
Reproducible with: 2.3.0, 2.5.1 (2021.3.33f1, 2022.3.16f1, 2023.2.4f1, 2023.3.0b1)
Not reproducible with: 2.2.1 (2021.3.33f1)
Reproduced on: macOS 13.6.3 (Intel)
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
- Shader Graph Swizzle Node Input/Output and Mask Update Incorrectly After Undo
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
Resolution Note (fix version 2.5.X):
Fixed a bug where the spline instantiate inspector was throwing an exception when the selection contained objects without that component.