Search Issue Tracker
Fixed
Fixed in 1.6.2
Votes
0
Found in [Package]
1.6.0-pre.3
Issue ID
UVSB-1432
Regression
Yes
Losing App and saved Variables after upgrading from Bolt to 1.6.0-pre.3
Reproducible on:
- Bolt 1.4.15 VS 1.6.0-pre.2, pre.3
- Editor version: 2021.1.2f1
- Platform: Windows 10
Steps to Repro:
- Create a project using Bolt Asset store
- Create new scene variable
- Create new app variable
- Create new saved variable
- From the package manager Import Visual Scripting 1.6.X
- Regenerate units, inspectors.
- On the Project window go to Ludiq->Bolt.Core->Generated
- Go to the Unity.VisualScripting.Generated-> VisualScripting.Core
Outcome Results:
- Observe that the Variables folder under Ludiq->Bolt.Core->Generated didn't get migrated to Unity.VisualScripting.Generated-> VisualScripting.Core when migrations were run. This will cause data loss if the user is transitioning from Bolt to VS and decided to delete Bolt folders Application and Saved variables will be lost
Expected Results:
- When the user runs migrations variables should be migrated as well so there is no data loss when transitioning.
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 (fix version 1.6.2):
Fixed application and saved variables not migrating from older versions