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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 1.8.1):
fixed in 1.9.0