This version was fully checked on 3 differents hosts (with a check coverage close to 100%)
Here is the "official way" to do this : https://www.reddit.com/r/cemu/comments/f3w3j2/cemu_on_an_external_drive/
Better move your PC, no ?
If you want to script this procedure = BatchFw V1.0 (save settings per host)
And you'll also have to rebuild your entire shader cache each time you'll switch from one host to another...
With BatchFw, CEMU is installed on each host and so the shader cache is valid until the next drivers update (no need to rebuild the shader cache each time).
The basic concept of BatchFw is to gather all the game data in the game folder and use the -mlc option from the CEMU command line.
I continue to say that is the right way to do this (no big mlc01 folder that might contain saves, updates and DLC of uninstalled games)
The last versions focused on precisely on portability enhancement.
Of course with lower IO access on a USB device, pre and post treatments times are longer but no so much as soon as the system
has cached the files.
Here the new tutorial : https://1drv.ms/v/s!Apr2zdKB1g7fgkS7wOmXmanOFRRp?e=qhwmgU
You'll see how to make and handle a portable games'library on a external USB drive using BatchFw :
02:00 : install games directly (only put game, DLC and update folder in your games'folder)
07:45 : import saves/transferable cache/update/DLC and games stats from existing CEMU's installation
19:45 : use the same shader cache for CEMU 1.15.18, 1.17.0 and 1.17.1 (slow build only one time on the first run)
25:45 : use GFX packs created by batchFw on a game still not supported in the official repository
25:45 : install on another host (HOST2)
28:25 : automatic import of BatchFw parameters on new host
38:00 : see that shader cache, saves and game stats follow (Host1 ones are completed)
39:00 : how to remove all install traces on a host with one click
40:25 : switch back to a host (HOST1)
40:48 : what if the drive letter change when my USB device is mounted ?
41:40 : no need to rebuild the cache ! your games are ready to launch
41:55 : transferable, saves and games stats have been updated when playing on HOST2
44:40 : restore all data to "classic" CEMU install (including games stats)
46:00 : synchronize your transferable cache, saves and games stats with other BatchFw's install
47:10 : pre/post treatments times when installed on a basic HDD (5400rpm)
47:40 : disable progress bar on a local installation
48:45 : uninstall BatchFw
A FAQ and compatibles CEMU and GFX packs versions were added on gitHub page.
I recommend to stay in that range of versions supported (that i have checked) but you don't really risk much to try new versions.
All manipulations on xml files in BatchFw use the least restrictive XPath requests possible and must therefore work even
if the settings.xml file is reorganized.
GitHub page: https://github.com/Laf111/CEMU-Batch-Framework
latest version : https://github.com/Laf111/CEMU-Batch-Framework/releases/latest
Here is the "official way" to do this : https://www.reddit.com/r/cemu/comments/f3w3j2/cemu_on_an_external_drive/
Better move your PC, no ?
If you want to script this procedure = BatchFw V1.0 (save settings per host)
And you'll also have to rebuild your entire shader cache each time you'll switch from one host to another...
With BatchFw, CEMU is installed on each host and so the shader cache is valid until the next drivers update (no need to rebuild the shader cache each time).
The basic concept of BatchFw is to gather all the game data in the game folder and use the -mlc option from the CEMU command line.
I continue to say that is the right way to do this (no big mlc01 folder that might contain saves, updates and DLC of uninstalled games)
The last versions focused on precisely on portability enhancement.
Of course with lower IO access on a USB device, pre and post treatments times are longer but no so much as soon as the system
has cached the files.
Here the new tutorial : https://1drv.ms/v/s!Apr2zdKB1g7fgkS7wOmXmanOFRRp?e=qhwmgU
You'll see how to make and handle a portable games'library on a external USB drive using BatchFw :
02:00 : install games directly (only put game, DLC and update folder in your games'folder)
07:45 : import saves/transferable cache/update/DLC and games stats from existing CEMU's installation
19:45 : use the same shader cache for CEMU 1.15.18, 1.17.0 and 1.17.1 (slow build only one time on the first run)
25:45 : use GFX packs created by batchFw on a game still not supported in the official repository
25:45 : install on another host (HOST2)
28:25 : automatic import of BatchFw parameters on new host
38:00 : see that shader cache, saves and game stats follow (Host1 ones are completed)
39:00 : how to remove all install traces on a host with one click
40:25 : switch back to a host (HOST1)
40:48 : what if the drive letter change when my USB device is mounted ?
41:40 : no need to rebuild the cache ! your games are ready to launch
41:55 : transferable, saves and games stats have been updated when playing on HOST2
44:40 : restore all data to "classic" CEMU install (including games stats)
46:00 : synchronize your transferable cache, saves and games stats with other BatchFw's install
47:10 : pre/post treatments times when installed on a basic HDD (5400rpm)
47:40 : disable progress bar on a local installation
48:45 : uninstall BatchFw
A FAQ and compatibles CEMU and GFX packs versions were added on gitHub page.
I recommend to stay in that range of versions supported (that i have checked) but you don't really risk much to try new versions.
All manipulations on xml files in BatchFw use the least restrictive XPath requests possible and must therefore work even
if the settings.xml file is reorganized.
GitHub page: https://github.com/Laf111/CEMU-Batch-Framework
latest version : https://github.com/Laf111/CEMU-Batch-Framework/releases/latest
Last edited by Laf111,
