Migrating verse devices always fails to load it, and loses the references

General Issues and Bug Reporting
, , ,
1

Every time I try to migrate a Level to create a copy or anything related to the migration process with custom creative verse devices the new version has all the references to the project gone or this message appears:

image

  • There is no Verse compilation errors
  • I re-opened the project a few times
  • The class was not renamed
  • It was migrated, not moved / deleted (I suppose migration counts as moving, but this process should change the other project references with the new ones in an ideal situation)
  • The verse code has not suffered any modification since the migration

Replacing the device means literally 6-8 hours lost in the migration process, and referencing work which is tedious and difficult, tedious, hard to replicate perfectly and time consuming.

Anyone know a workflow that dose not lose the verse class references or any way to do that.

THE PROBLEM APPEARED IN MIGRATION PROCESS, I HAVE NOT TESTED IN COPY PASTING THE LEVEL IN THE SAME PROJECT BUT I THINK IT WILL GENERATE THE SAME PROBLEM

2

We’re encountering the same problem and haven’t yet found a workaround.

If you open the uasset files in a hex editor you can see that the paths for verse objects aren’t rewritten correctly and will contain the old project name.

We have a large and complex map we’d like to reuse for different game modes and not being able to migrate it over means a huge amount of rework for any interactive content in the map.

3

I’ve faced the same issue a few times. Fixing this would save myself and others many hours!

4

Same issue. I wonder if Epic ever migrated Verse Devices…