Search Issue Tracker
Fixed
Fixed in 1.7.3
Votes
0
Found in [Package]
1.5.2
1.6.0
1.6.1
1.7.1
1.7.2
Issue ID
UVSB-1617
Regression
No
Custom Nodes not being added to the node db
Reproducible on:
- Unity version: 2021.2.0b2 and 2021.1.13f1
- VS version: 1.7, 1.6
- Platfor: Windows 10 and macOS Catalina
Steps to Reproduce:
- Create a new project (most probably a "new" project is not necessary but was the step that we could repro steadily)
- Create a new custom node, right-click on Project->Create->C # script
- Open the created script and copy-paste the following code and save
{code:java}
using Unity.VisualScripting;
public class MyNode : Unit
{
protected override void Definition() //The method to set what our node will be doing.
{
}
}
{code}
- Regenerate Nodes from Edit->Project Settings->Visual Scripting
- CReate a new Script graph
- Click to open the fuzzy finder
Actual Outcome:
- The newly created node does not appear on the fuzzy finder
- The node does not appear on the nodes DB
Expected Results:
- Custom nodes should appears on the fuzzy finder.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 1.7.3):
https://github.cds.internal.unity3d.com/unity/com.unity.visualscripting/pull/419