Lales.Charles Posted January 18, 2023 Share Posted January 18, 2023 Hi, We just migrated our external data (mount points) to 2.16.1. Following documentation (and our usual procedure), we proceeded manually with command usc_x64.exe upgrade.usc ... https://developer.unigine.com/en/docs/latest/upgrade/migration_content/?rlang=cpp#manual_upgrade No msg error, but migration done to 2.16.0.2 only. Then opening editor with this data (mount points), migration has been completed to 2.16.1.0. Is it normal? Can you check manual migration scripts or config files are fine? Regards, Charles Link to comment
vvvaseckiy Posted January 19, 2023 Share Posted January 19, 2023 Hello Lales.Charles, I've doubled checked that manual migration for 2.16.1 works without issues on our side, so the problem might be in some specific content or some other conditions. Could you please specify for what version of project migration was ran, e.g. 2.15.1? Also migration log would've been very helpful. Usually migration for some version could be skipped if migration script detects version higher that migration version at least in one file. It's not marked as error, but usually such files don't appear in project unless they've been imported in some beta releases Unlike migration script, migration in editor doesn't stop when it finds higher version, it just proceeds to the next file Link to comment
Lales.Charles Posted January 19, 2023 Author Share Posted January 19, 2023 Hi, Well, manual migration has been done on multiple external folders (8 mount points), and same for all (except the resources delivered directly from your asset store). It was a mix 2.15.0.1 and 2.15.1.0. Just redone it on some data related to your demo data. Logs mention migration to 2.16.0.0, 2.16.0.1, 2.16.0.2, 2.16.1.0 Scanning files, still many 2.15.0.1 and 2.15.1.0 are still there.. Attached log helps? Do you need the data? Regards, Charles migration-2-16.txt Link to comment
vvvaseckiy Posted January 19, 2023 Share Posted January 19, 2023 From migration log it seems that everything went fine. Migration only affect specific assets that require migration, while some other contents of data/ managed by editor contains engine version but not affected by migration(e.g. data/runtimes/**/*.meta), they're updated on editor startup or by runtimes_generator. Also some files ignored both by migration script and editor, e.g. *.umount files or files like ig_config.xml and they can contain older versions even after migration and launch of editor. So searching for older version inside files can sometimes give positive results, it shouldn't affect engine functionality 1 Link to comment
Recommended Posts