Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.7.8
Issue ID
UVSB-2415
Regression
No
Visual Scripting ignores assembly definitions when regenerating nodes
To reproduce:
1. Open the project “VisualScriptingTest”
2. Select “TestObject” in the Hierarchy
3. Click the “Edit Graph” button in the Inspector
4. Expand the Script Graph window
Expected result: Four classes are generated and the “ClassUsingEditor” class can be found in the fuzzy search
Actual result: The “ClassUsingEditor” class is being ignored and cannot be found in the fuzzy search
Reproducible with: 1.7.8 (2021.3.8f1, 2022.1.13f1, 2022.2.0b4, 2023.1.0a6)
Could not test with: 2020.3.38f1 (Package errors)
Reproduced on: macOS Monterey 12.5 (Intel)
Notes:
- From the two classes with editor code in them, only the one in "IgnoredAssembly" didn't get generated, the class in the Scripts folder was generated fine
- The method Codebase.IsUserAssembly(string name) should prevent this from happening but it only checks if the assembly is "Assembly-CSharp" or "Assembly-CSharp-firstpass".
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
- Scene view audio toggle doesn't work after disabling and enabling audio source component with audio random container
- Pitch changes while paused messes up scheduling of the audio random container
- Crash on detail::ComputeShaderSnippetKey when entering the Play mode
- Unable to interact with Material Inspector window when creating a new Material and renaming it
- Shadow artifact is cast onto GameObjects in the Scene view when the Scene view lighting is disabled
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UVSB-2382