Cannot Migrate Verse Devices Between Projects

General Issues and Bug Reporting
,
1

Summary

Verse devices cannot be migrated between projects.

Verse device assets cannot be migrated.

Verse device actors in a level asset are migrated, but they will fail to validate in the destination project because the verse device assets are not migrated.

Additionally, even if the verse assets are manually migrated to the project, any editable properties that reference other actors will fail to validate. In the text definition of the actor, the editable references refer to the source project name.

Finally, any assets referenced by the verse code via asset reflection will also not be migrated. In this case, this will prevent the verse from building successfully, since the assets it depends on are not migrated.

Please select what you are reporting on:

Verse

What Type of Bug are you experiencing?

UI/Tools

Steps to Reproduce

  1. Create a project with verse devices that have editable properties to devices
  2. Place a verse device in the level
  3. Connect all editable properties in the device
  4. Migrate the level asset to a new project
  5. Go to destination project
  6. Open migrated level
  7. Attempt to build verse code
  8. Attempt to launch session
  9. Observe several validation errors

Expected Result

The migrated level validates, and operates the same as the source level

Observed Result

Several validation errors when launching a migrated level with verse devices.

Platform(s)

PC / UEFN

2

FORT-946761 has been created and its status is ‘Unconfirmed’. This is now in a queue to be reproduced and confirmed.

3

it is worth noting that converting a source project into a template, and creating a new project using that template, will preserve verse devices. but this only works once for a destination, and must be done from the beginning