Search Issue Tracker
Fixed
Fixed in 1.8.1
Votes
3
Found in [Package]
1.7.7
1.7.8
Issue ID
UVSB-2382
Regression
Yes
Nodes from runtime assemblies that reference Unity editor are not visible in the fuzzy finder
h3. Steps to reproduce:
# Create a new project.
# Install the Cinemachine package.
# Initialize visual scripting and create a new graph.
# Bring up the fuzzy finder.
h3. Results:
Cinemachine nodes are not visible in the fuzzy finder. They need to be added individually through the type options before they are visible.
h3. Expected Results:
As per Rohit:
We provide some way for users to indicate to users that they want nodes from an assembly to appear in the fuzzy finder, even though it would normally be hidden in AOT safe mode. Right now it's all or nothing (AOT Safe mode on or off), which isn't great when the user really just wants specific assemblies to be excluded from the filter
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
- Errors are logged when importing an asset at a path with Firebase
- Entering too big of a number in 2D Renderer Lightmode Tags freezes the Editor
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
Resolution Note (fix version 1.8.1):
fixed in 1.9.0