2.20 Migration: errors during migration: clusters are lost when moving data to umount, incorrect reimport

[Amerio.Stephane]

Hello,

After migrating to 2.20, all our clusters have lost their content. The number of meshes is shown as 0 for every cluster.

Migration was done like this:

1. create a new 2.20 IG+VR project
2. import relevant asset store packages (ig aviation, airports, etc) (I guess this is not relevant for the bug, but who knows)
3. close editor
4. open 2.19 editor and export a package for each of our 2.19 umount (ex: 2.19/project/umount_hc exported to hx.upackage)
5. launch 2.20 editor and import the package (doing it this way allows us to filter out eventual duplicated guids). This starts the migration of hc to 2.20.
6. in editor create a new mount point for 2.20/project/umount_hc
7. in editor, move all content of hc to umount_hc
8. close editor
9. rename umount file umount_hc to its definitive name and location
10. relaunch editor
11. close and relaunch.

Surprisingly, subsequent relaunch creates a lot of issues: clusters are empty (but the clusters binary data is in the mount point, at the correct location). Also, a lot of FBX, GLB, OBJ are being reimported AFTER the migration (as if the migration wasn't done) and this creates a lot of empty mesh files, or texture files with the wrong extension (so the importer will incorrectly loads theme next time) or it simply duplicates the files that we had imported previously and moved to a texture/ folder.

[silent]

Hi Stephane,

I think that the root cause of this behavior is actually in the step 9:

Quote

rename umount file umount_hc to its definitive name and location

You need to change path directly in .node file so it would contain actual path to the mount after renaming mount:

This is known limitation of new binary clusters content stored in .node files, but it was not intended to work like that. We plan to fix this issue in the next release.

Thanks!