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)
Comments (1)
-
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
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.