Search Issue Tracker
Fixed
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
- 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:
Fixed a bug where the spline instantiate inspector was throwing an exception when the selection contained objects without that component.