Emulators
Emulator configuration is slightly more involved. You have to specify the path to each emulator executable you want to use. All the Playnite supported emulators should work if they have a Linux version and use the same command line arguments as their Windows counterparts.
Example configuration
- Ares emulator is installed as a native package and is available in the system PATH, so all you need to specify is its name.
-
Nestopia and RetroArch are installed as flatpak packages, so you need to specify the entire script including
the
flatpak runcommand. - DuckStation and RPCS3 are installed as AppImages, so you need to specify the absolute path to the AppImage file.
- You can also specify the environmental variables for specific emulators, like you can see in the RPCS3 emulator configuration.
As for the regular Playnite emulator configuration, little has changed. You specify each emulator in the Configure Emulators menu as usual.
Since in Linux you don't really install apps to their specific directories, you don't need to specify the Installation Folder, but the emulator import functionality doesn't work.
Example - built-in emulator
In this example, we have ares emulator configured as a built-in emulator. We have also added Famicom and Super Famicom as built-in profiles. This should be everything you need to do to get this emulator working.
Example - custom emulator
In this example, we add Kate, a Linux text editor, as a example custom emulator. Of course, you can use any application you want.
The most important settings is Executable. Here, you need to specify the Linux path with a wine-bridge:// prefix to your target application. Since we launch Kate using the kate command in the terminal, we need to enter wine-bridge://kate.
The rest of the settings you fill out the same way as on Windows. It's worth noting that {ImagePath} variable will be converted to Linux path when executing the command even though in the game configuration we specify a Windows path.
Working Directory and Tracking Mode are ignored.
The above configuration will make so that the game ROM file running in this "emulator" will be opened in Kate.
Scanning for ROMs should work mostly out of the box. The only exceptions are emulators that use Powershell scripts for ROM import, so: RPCS3, ShadPS4 and ScummVM.
It's worth noting that the Scan folder needs to contain the Windows path for the folder you want to scan.
Example configuration
Again, it's the same as on Windows. When specifying the ROM path, you use the Windows path. If running through a Linux emulator, it will be automatically converted to the Linux path.
Example
See Issues for details.