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-2280
Regression
No
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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
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.