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
- UI Toolkit Editor Window Creator becomes deformed and stretched when the “Enter” key is pressed
- “Assertion failed on expression: 'IsFinite(distanceForSort)’” is spammed in the Console when changing Trail GameObject position to a very high number
- VFX Graph Node documentation icon is pixelated
- Cutout box is covered in a shadow when the object that houses the cutout is casting shadows
- “Metal: Fragment shader missing texture binding at index 0 (_MainTex / Hidden/Preview Alpha)” warnings are thrown when selecting some TextMesh Pro Font Assets
Resolution Note (fix version 1.8.1):
fixed in 1.9.0