Search Issue Tracker
Fixed
Fixed in 1.7.8
Votes
1
Found in [Package]
1.7.6
Issue ID
UVSB-2052
Regression
No
Visual Scripting can't read Bolt Saved Variables when project is migrated from Bolt to Visual Scripting
How to reproduce:
1. Open the attached project '1372762.zip'
2. Build and Run the application
3. In the app, press the 'Button' button
4. Open the same project in Unity 2021.2 or 2022.1
5. Install Visual Scripting package and migrate project when asked
6. Build and Run the application on an Android device
Expected results: The value '555' can be seen on the screen (the same screen that is seen after doing step 3)
Actual results: The value '1' can be seen on the screen instead of '555' (the same screen that is seen before doing step 3)
Reproducible with: 1.7.5 (2021.2.1f1), 1.8.0-pre.1 (2022.1.0a14)
Could not test with: 2019.4.32f1, 2020.3.22f1 (Visual Scripting package not available)
Notes:
- Does not reproduce in Editor when entering Play mode
- Reproducible on Android, iOS, and standalone builds
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
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
Resolution Note (fix version 1.7.8):
Add conversion to old Bolt save to new Visual Scripting.