Search Issue Tracker
Won't Fix
Votes
2
Found in [Package]
1.7.8
Issue ID
UVSB-2397
Regression
No
Custom nodes are being removed from Node Library when generating Custom Inspector Properties
To reproduce:
1. Open the project “VisualScriptingBug”
2. FMOD → Generate Visual Scripting Units
3. Edit → Project Settings → Visual Scripting → Expand ‘Node Library'
4. Notice 'FMODUnity' in the list
5. Edit → Project Settings → Visual Scripting → Custom Inspector Properties → Generate
6. Edit → Project Settings → Visual Scripting → Expand 'Node Library’
Expected result: 'FMODUnity' is still on the list
Actual result: 'FMODUnity' is removed from the list
Reproducible with: 1.7.8 (2020.3.36f1, 2021.3.6f1, 2022.1.9f1, 2022.2.0a18, 2023.1.0a2)
Reproduced on: macOS Monterey 12.4 (Intel)
-
jeanedouard_unity
Oct 14, 2022 17:04
The issue is in the user's project. In the BoltIntegration.BuildBoltUnitOptions() method, BoltCore.Configuration.Save() must be called just before building the UnitBase so that the Preferences Asset is serialized with FMOD nodes.
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
- Crash on BurstCompilerService::CompileAsync when opening a specific project
- [Android] Particles aren't rendered when the shader "Particle/Standard Unlit" or "Particles/Standard Surface" is used on a Material
- Crash on nvoglv64.dll when opening a project
- [RenderGraph] [CameraStacking] Passes are failing when CameraStacking and RG are enabled
- Physics and Raycast have different behavior when enum is exposed in the Editor
Resolution Note:
The issue is in the user's project. In the BoltIntegration.BuildBoltUnitOptions() method, BoltCore.Configuration.Save() must be called just before building the UnitBase so that the Preferences Asset is serialized with FMOD nodes.