Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.4.15
1.5.2
1.6.2
1.7.7
Issue ID
UVSB-2283
Regression
No
Importing Visual Scripting Assets before opening visual scripting graphs throw errors.
Importing Visual Scripting Assets before opening visual scripting graphs throw errors.
When importing new visual scripting assets in a project where you never opened visual scripting, a bunch of errors start to log about.
*Reproducible on:*
* All VS versions
* Unity version: 2020+
{*}Steps to Reproduce{*}:
# Create a new project in 2022 (Spline package only work from there)
# Import the spline package from the zip file in the package manager
# Import the spline sample from the package manager
# Open the scene "Assets/Samples/Splines/1.0.0-pre.8/Spline Examples/Scenes/9 - Visual Scripting/Visual Scripting - Spline Evaluation.
# In the Hierarchy, click on the Game Object AnimateAlongSpline. You should start to see error.
# Press play
# Now you should see other errors.
*To make it work*
Open a script graph, now unity will build the node library and no error will occur.
*Expected results*
Everything should work fine even if the user never opened a script graph in the project.
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
- Compiled Shader code has self-assignments and redundant code in the Shaders that use "enable_d3d11_debug_symbols"
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
- "Unable to get the list of approved APIs." is thrown when testing the App Packages with Windows App Certification Kit
Resolution Note:
Not reproducible on 1.7.7. Node library regeneration occurs when selecting object in hierarchy.
Only occurs on 1.7.6 and earlier.