Search Issue Tracker
Fixed
Fixed in 1.8.1
Votes
0
Found in [Package]
1.8.0
Issue ID
UVSB-2459
Regression
Yes
Assembly disappears from Node Library after domain reload
h3. Reproduction Steps:
- Open the attached project.
- Go into the project settings and into the Visual Scripting settings.
- In the Node Library, add the assembly NewAssembly
- Enter play mode or perform any action to trigger a domain reload.
- Go back to the Visual Scripting settings and look at the Node library again
h3. Actual Outcome:
NewAssembly is removed from the Node Library.
Note that if you add a Type Option from the NewAssembly then it would remain in the Node Library after the domain reload. However we encounter a different issue.
If you add NewAssembly to the Node Library and New Behaviour Script to the Type Option, if you remove them and trigger a domain reload, NewAssembly reappears in the Node Library.
h3. Expected Outcome:
After the domain reload, NewAssembly should still be in the Node Library
h3. Reproducible on:
VS 1.8.0 on 2021.3.16f1, 2022.2.2f1, 2023.1.0a25. Not reproducibly on VS 1.7.8
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
- StackOverflowException occurs and tests fail to load when the Test Runner window is opened while System.Windows.Forms.dll and System.Deployment.dll are present in the project
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note (fix version 1.8.1):
Fixed in 1.9.1