Right now Cemu creates a symlink in ~/retrodeck/bios/cemu/usr/save
to point to the ~/retrodeck/saves/wiiu/cemu directory
While this is fine for a single user/device setup, if the user attempts to do any cross-device syncing and the two devices do not have identically named users, the symlink will break and Cemu will fail to start up on the second (or later) device.
A workaround for this is to completely delete the symlink under ~/retrodeck/bios/cemu/usr/save and recreate it as a real directory. This will avoid invalid symlink paths, though does expose the saves to possibly being blown out with an emulator reset and leaves the saves in a non-standard path for the other emulators with the possibility of the user forgetting to back them up if they are moving devices.
Better handling of this symlink (possibly through the use of environment variables), or pointing Cemu directly to the ~/retrodeck/saves/wiiu/cemu path rather than through a symlink might solve this, but I'm expert on how to best handle this.
Right now Cemu creates a symlink in
~/retrodeck/bios/cemu/usr/save
to point to the~/retrodeck/saves/wiiu/cemu
directoryWhile this is fine for a single user/device setup, if the user attempts to do any cross-device syncing and the two devices do not have identically named users, the symlink will break and Cemu will fail to start up on the second (or later) device.
A workaround for this is to completely delete the symlink under
~/retrodeck/bios/cemu/usr/save
and recreate it as a real directory. This will avoid invalid symlink paths, though does expose the saves to possibly being blown out with an emulator reset and leaves the saves in a non-standard path for the other emulators with the possibility of the user forgetting to back them up if they are moving devices.Better handling of this symlink (possibly through the use of environment variables), or pointing Cemu directly to the
~/retrodeck/saves/wiiu/cemu
path rather than through a symlink might solve this, but I'm expert on how to best handle this.