Visual Scripting 1.7.7

Unity Engine
,
1

Just out today (Feb 7th 2022). Change log:

  • Fix an NullException error that occurs when creating a Variable right after project initialization.
  • Fix Visual scripting naming in Project Settings and listener.
  • Scene is marked as dirty when a graph is created on a new or exiting GameObject BOLT-1860
  • Fix Flow Variables missing icon
  • Improved node regeneration speed
  • Fix null texture error when switching platform after a build failure
  • Fix null texture error when entering play mode
  • Fix Linux build failing when run from command line
  • Fix Editor Assemblies not detected correctly at Codebase initialization
  • Fix Wait nodes naming inconsistency BOLT-1886
  • Fix constant being stripped in IL2CPP builds BOLT-1638
  • TryConvert now returns true when the conversion was successful BOLT-2105
  • Fix Input system by using correct Input API BOLT-2078

I’ll be giving it a try but it doesn’t look to be addressing the many errors (node integrity, grouping, missing arrows, misplaced V3 fields, near countless other errors that make VS so “challenging”…

2

The two errors when opening the project are gone.

The error on fullscreening the graph seems to be partially fixed? The first time I fullscreened in edit mode, it threw an error. But I can’t reproduce. I get this warning instead now:

Should not be capturing when there is a hotcontrol
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)

The error on full screen is marked as “Fix In Review for Unreleased, 1.7.7” yet the release doesn’t list this fix? Unity Issue Tracker - GUID errors in the console when the user clicks to full screen the graph

Groups seem to be fixed on my end. I can enter/exit Play mode with groups present in my graph - no issues so far.

Smaller literal nodes seem to have weird drawing issues with mini bars on each edge of the node:

But overall, I’m getting A LOT less errors when doing basic things with the tool. Seems the changelog doesn’t list several fixes.