This is the second time it has happened when an update causes all references to a Verse device to be lost, and when you have a multitude of connections set up it’s very time-consuming to have to rebuild your project connections from scratch.
If this doesn’t get addressed, every time something changes in Verse, all connections will again be lost in all verse devices.
Hi Wertandrew,
Is this the same thing as your post here? Critical - UEFN - No migration for Speaker device >> Audio Player Device, Project broke - #2 by Waurelius
If this is a DIFFERENT case can you tell from context what device failed to load? If you can post the client log we might be able to tell as well.
Audio speaker devices (from creative). They no longer exist and there was no migration to the new audio player device, so all those devices unloaded and we had a good amount of errors. Hard to get a log now since we have since replaced them, but it’s not the same issue as verse devices losing connections nor launching live edit causes 5k edits and takes 15 mins to load, all these are separate issues caused by the last update. Ray has the full project file if you want to see all the issues together (it was a fresh post-update build)
Yeah, ‘verse devices losing connections’ in cases where there wasn’t an obvious re-naming or removal of a given device is super concerning. If you come across a common workflow where you see this we would definitely be all ears.
The renaming/removal issue will… stop being an issue real soon because we’re going to stop doing that after public beta release.