Search Issue Tracker
Fixed in 1.0.0
Votes
0
Found in [Package]
1.0.0-pre.9
Issue ID
1410152
Regression
No
[Splines] Value cannot be null error is thrown when a Spline field is declared in a class
How to reproduce:
1. Open users attached project
2. Open Assets > Scenes > SampleScene.unity
3. Select "Spline Example Game Object" GameObject
4. In the Inspector window expand the "Spline" variable
5. Observe the Console window
Expected result: Spline variable is expanded without any errors
Actual result: "Value cannot be null" error is thrown
Reproducible with: 1.0.0-pre.8 (2021.2.16f1, 2022.1.0b10), 1.0.0-pre.9 (2022.1.0b11)
Not reproducible with: 1.0.0 (2022.1.0b12), 1.0.1 (2022.1.0b14, 2022.2.0a9)
Couldn't test with: 1.0.0-pre.8 (2019.4.36f1, 2020.3.32f1) (couldn't resolve console errors)
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 (fix version 1.0.0):
Fixed in: Splines 1.0.0