Search Issue Tracker

By Design

Votes

0

Found in [Package]

1.7.3

Issue ID

BOLT-1668

Regression

No

[Visual Scripting] Adding UnitDescriptor makes custom unit not appear in Fuzzy Finder

Package: Bolt

-

Reproduction steps:
1. Open project the attached user's project "CustomUnitTest-2021.1.zip"
2. Run Edit > Project Settings > Visual Scripting > Regenerate Nodes
3. Open "Assets/New State Graph.asset" and show Fuzzy Finder. You can see that there is no "YourNode" unit
4. Delete "YourNodeDescriptor.cs" or comment out "YourNodeDescriptor" class definition
5. Run Edit > Project Settings > Visual Scripting > Regenerate Nodes
6. Open "Assets/New State Graph.asset" and show Fuzzy Finder. You can see that "YourNode" unit is shown correctly

Expected results: custom unit should appear in Fuzzy Finder regardless of its UnitDescriptor
Actual results: adding UnitDescriptor makes custom unit not appear in Fuzzy Finder

Reproduces on: Visual Scripting 1.7.3 (2021.1.16f1, 2021.2.0b5, 2022.1.0a4)
Could not test on 2019.4.29f1 and 2020.3.15f2 due to Bolt 1.4.15 not having the option to Regenerate Nodes and package errors when downgrading

  1. Response avatar

    Resolution Note:

    As explained in the documentation, the UnitDescriptor must be placed in an Editor folder. It is by the design that the node doesn't appear in the fuzzy finder if the Descriptor is not in an Editor folder as if a runtime assembly has a dependency on an Editor assembly this will prevent the player to build.

  2. Response avatar

    Resolution Note:

    No tests needed, the issue is as designed

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.