mirror of
https://github.com/RetroDECK/ES-DE.git
synced 2025-01-29 19:55:37 +00:00
Documentation update for the 3.1.1 release
This commit is contained in:
Leon Styhre
parent
93031ef08c
commit
a59b8016be
82
ANDROID.md
82
ANDROID.md
|
|
@ -55,17 +55,27 @@ Some emulators like RetroArch are still using an older storage access method and
|
|||
The following emulators are configured for FileProvider access:
|
||||
* 2600.emu
|
||||
* DroidArcadia
|
||||
* EKA2L1
|
||||
* FPseNG (still needs scoped storage to be setup in emulator)
|
||||
* FPse (still needs scoped storage to be setup in emulator)
|
||||
* GBA.emu
|
||||
* GBC.emu
|
||||
* Infinity
|
||||
* J2ME Loader
|
||||
* JL-Mod
|
||||
* Lynx.emu
|
||||
* MAME4droid 2024 (for most systems)
|
||||
* MAME4droid
|
||||
* MD.emu (genesis, mastersystem, megadrive, megadrivejp)
|
||||
* NES.emu
|
||||
* NGP.emu
|
||||
* Panda3DS
|
||||
* PCE.emu (pcengine, supergrafx and tg16 systems)
|
||||
* Ruffle
|
||||
* Skyline
|
||||
* Swan.emu
|
||||
* SWF Player
|
||||
* Virtual Virtual Boy
|
||||
|
||||
Some of these emulators require BIOS files, so they still need to be configured before they can be used with ES-DE.
|
||||
|
||||
|
|
@ -185,6 +195,14 @@ Also be aware that the version check that runs on app startup may not be able to
|
|||
|
||||
It's generally a very good idea to import your native Android apps into ES-DE prior to setting it as the home app, this way you can easily access things like the Settings app. Note however that even if you somehow lock yourself out of the system by setting ES-DE as the home app and not having any native apps added you can still always access the Settings app via the Android notification shade. On most devices you access this by swiping down from the top of the screen. After swiping down, just select the cogwheel icon to start the Settings app. From there you can change the home app to something else than ES-DE, should you need to.
|
||||
|
||||
## Running ES-DE in multi-window mode
|
||||
|
||||
On tablets and other devices that support it, ES-DE can be run in multi-window mode. This does come with some caveats though, most importantly that changing to or from multi-window mode or changing the size of the ES-DE window when running in multi-window mode will trigger a reload of the application. When this happens any menu that is open will get unceremoniously closed, so make sure to never do this when for instance the scraper or theme downloader is running as they will get instantly stopped.
|
||||
|
||||
Also be aware that running in multi-window mode obviously changes the ES-DE window size and therefore likely the window aspect ratio as well, so it may not look good with some themes that do not support the new aspect ratio.
|
||||
|
||||
Finally, multi-window mode doesn't work when ES-DE has been set as the home app as Android does not allow that.
|
||||
|
||||
## Known ES-DE problems
|
||||
|
||||
* Poor performance/low frame rate after startup on some devices, which seems to happen randomly and is usually resolved by itself within 10 to 30 seconds.
|
||||
|
|
@ -214,6 +232,12 @@ If you prefer to apply the NetherSX2 patch yourself (i.e. build the APK) then yo
|
|||
|
||||
https://github.com/Trixarian/NetherSX2-patch
|
||||
|
||||
### Cemu
|
||||
|
||||
This emulator can be downloaded from the following GitHub site. Note that this repository is not from the official Cemu project, we consider Cemu as experimental on Android for the time being.
|
||||
|
||||
https://github.com/SSimco/Cemu/releases
|
||||
|
||||
### Citra
|
||||
|
||||
The original Citra emulator project is no longer alive, but there is a fork that should work as a drop-in replacement. The Citra MMJ fork is also a viable alternative. Both of these emulators are available for download from their GitHub sites.
|
||||
|
|
@ -326,6 +350,14 @@ This emulator can be installed from the Play store.
|
|||
|
||||
https://play.google.com/store/apps/details?id=com.fms.ines.free
|
||||
|
||||
### Infinity
|
||||
|
||||
This PICO-8 game engine/emulator can be installed from the Play store.
|
||||
|
||||
https://play.google.com/store/apps/details?id=me.dt2dev.infinity
|
||||
|
||||
Note that this emulator has a strange behavior where it will return to the home app whenever you exit a game, so unless ES-DE is set as your home app you'll need to manually switch back to it after exiting Infinity.
|
||||
|
||||
### IrataJaguar
|
||||
|
||||
This Atari Jaguar emulator can be downloaded from their website. Just be aware that it's very old and has not been updated for modern Android releases, so it may be finicky on some devices or it may not work at all.
|
||||
|
|
@ -373,6 +405,12 @@ For some systems you will need to explictly set the _Start_ and _Select_ buttons
|
|||
|
||||
There are a few more things that you may need to configure for some systems, but that's beyond the scope of this document and should be covered by the MAME emulator documentation.
|
||||
|
||||
### Mandarine
|
||||
|
||||
This emulator which is forked from Citra can be downloaded from their GitHub site.
|
||||
|
||||
https://github.com/mandarine3ds/mandarine/releases
|
||||
|
||||
### MasterGear
|
||||
|
||||
This emulator can be installed from the Play store as a paid app.
|
||||
|
|
@ -502,6 +540,20 @@ Although this emulator supports both the Sinclar ZX Spectrum and MGT SAM Coupé
|
|||
https://play.google.com/store/apps/details?id=com.fms.speccy \
|
||||
https://play.google.com/store/apps/details?id=com.fms.speccy.deluxe
|
||||
|
||||
### SWF Player
|
||||
|
||||
This emulator which is essentially a GUI for Ruffle can be installed for free from the Play store. There's a paid Pro version as well.
|
||||
|
||||
https://play.google.com/store/apps/details?id=com.issess.flashplayer \
|
||||
https://play.google.com/store/apps/details?id=com.issess.flashplayerpro
|
||||
|
||||
### Virtual Virtual Boy
|
||||
|
||||
This emulator can be installed from the Play store or from their GitHub site.
|
||||
|
||||
https://play.google.com/store/apps/details?id=com.simongellis.vvb \
|
||||
https://github.com/SupernaviX/vvb/releases
|
||||
|
||||
### Visual Pinball
|
||||
|
||||
Although Visual Pinball is working fine on Android it's not possible to properly integrate it with a frontend, you'll instead need to install your tables inside the app and create dummy .vpinball files for your games in ROMs/vpinball and after launching a table from ES-DE you need to manually start it from inside the Visual Pinball GUI. There are more detailed setup instructions in the Visual Pinball section of the User guide.
|
||||
|
|
@ -541,14 +593,14 @@ This is clearly not a complete list of Android devices, but rather those we know
|
|||
| :----------- | :---------------------- | :-------------- | :-------- | :------------------ | :------------------------- |
|
||||
| Abxylute | One | 12 | Yes | None | |
|
||||
| Alldocube | iPlay50 mini Pro | 13 | Yes | None | |
|
||||
| Anbernic | RG353V | 11 | Yes | None | |
|
||||
| Anbernic | RG405M | 12 | Yes | None | Limited RAM capacity for this device makes it unsuitable for demanding themes and large game collections |
|
||||
| Anbernic | RG405V | 12 | Yes | None | Limited RAM capacity for this device makes it unsuitable for demanding themes and large game collections |
|
||||
| Anbernic | RG353V | 11,<br>GammaOS 12,<br>GammaOS 13 TV | Yes | None | Limited RAM capacity for this device makes it unsuitable for demanding themes and large game collections |
|
||||
| Anbernic | RG405M | 12,<br>GammaOS 12 | Yes | None | |
|
||||
| Anbernic | RG405V | 12,<br>GammaOS 12 | Yes | None | |
|
||||
| Anbernic | RG406H | 13 | Yes | None | |
|
||||
| Anbernic | RG406V | 13 | Yes | None | |
|
||||
| Anbernic | RG505 | 12 | Yes | None | Limited RAM capacity for this device makes it unsuitable for demanding themes and large game collections |
|
||||
| Anbernic | RG505 | 12,<br>GammaOS 12 | Yes | None | |
|
||||
| Anbernic | RG556 | 13 | Yes | None | |
|
||||
| Anbernic | RG ARC | 12 | Yes | None | LineageOS |
|
||||
| Anbernic | RG ARC | LineageOS 12,<br>GammaOS 12,<br>GammaOS 13 TV | Yes | None | Limited RAM capacity for this device makes it unsuitable for demanding themes and large game collections |
|
||||
| Anbernic | RG Cube | 13 | Yes | None | |
|
||||
| AYANEO | Pocket Air | 12 | Yes | None | |
|
||||
| AYANEO | Pocket DMG | 13 | Yes | None | |
|
||||
|
|
@ -559,6 +611,7 @@ This is clearly not a complete list of Android devices, but rather those we know
|
|||
| Ayn | Odin 2 (Base/Pro/Max) | 13 | Yes | Minor audio issues | |
|
||||
| Ayn | Odin 2 Mini | 13 | Yes | None | |
|
||||
| Ayn | Odin 2 Portal | 13 | Yes | None | |
|
||||
| GKD | Bubble | GammaOS 13 TV | Yes | None | Limited RAM capacity for this device makes it unsuitable for demanding themes and large game collections |
|
||||
| Google | Pixel 2 XL | 11 | Yes | None | |
|
||||
| Google | Pixel 3 XL | 12 | Yes | None | |
|
||||
| Google | Pixel 4a | 13 | Yes | None | |
|
||||
|
|
@ -569,7 +622,7 @@ This is clearly not a complete list of Android devices, but rather those we know
|
|||
| Google | Pixel 7 Pro | 13 | Yes | None | |
|
||||
| Google | Pixel 8 Pro | 14 | Yes | None | |
|
||||
| Google | Pixel Fold | 14 | Yes | None | |
|
||||
| Google | Pixel Tablet | 14 | Yes | None | |
|
||||
| Google | Pixel Tablet | 14, 15 | Yes | None | |
|
||||
| GPD | XD Plus | 11 | Yes | None | LineageOS |
|
||||
| Honor | 20 lite | 10 | Yes | None | |
|
||||
| Honor | Magic5 Pro | 13 | Yes | None | |
|
||||
|
|
@ -579,6 +632,7 @@ This is clearly not a complete list of Android devices, but rather those we know
|
|||
| Infinix | Zero 30 5G | 13 | Yes | None | |
|
||||
| Kinhank | G1 | 11 | No | Unable to install | Possibly 32-bit operating system? |
|
||||
| Kinhank | Super Console X5 Pro | 12 (TV) | No | None | Custom 64-bit Android TV OS |
|
||||
| KTPocket | KT-R1 | GammaOS 12 | Yes | None | |
|
||||
| Lenovo | Legion Y700 (2022) | 12 | Yes | None | |
|
||||
| Lenovo | Legion Y700 (2023) | 13 | Yes | None | |
|
||||
| Lenovo | Xiaoxin Pad Pro 2021 | 11 | Yes | None | |
|
||||
|
|
@ -604,6 +658,8 @@ This is clearly not a complete list of Android devices, but rather those we know
|
|||
| Oppo | A15 | 10 | Yes | None | |
|
||||
| Oppo | Find X5 Pro | 14 | Yes | None | |
|
||||
| Oppo | Reno5 | 12 | Yes | None | |
|
||||
| Orange Pi | Pi 5 | 12 (TV) | Yes | None | |
|
||||
| Powkiddy | RGB (RK3566) series | GammaOS 13 TV | Yes | None | Limited RAM capacity for this device makes it unsuitable for demanding themes and large game collections |
|
||||
| Raspberry | Pi 4/400 | 13, 14 | Yes | None | Low-power GPU so ES-DE may run a bit sluggish |
|
||||
| Raspberry | Pi 5 | 15 | Yes | None | Very poor GPU performance, runs at almost double speed in Raspberry Pi OS so likely a driver issue |
|
||||
| Razer | Edge | 13 | Yes | None | |
|
||||
|
|
@ -723,7 +779,7 @@ The **@** symbol indicates that the emulator is _deprecated_ and will be removed
|
|||
| fba | FinalBurn Alpha | FB Alpha 2012 | FB Alpha 2012 Neo Geo,<br>FB Alpha 2012 CPS-1,<br>FB Alpha 2012 CPS-2,<br>FB Alpha 2012 CPS-3 | Yes | |
|
||||
| fbneo | FinalBurn Neo | FinalBurn Neo | | Yes | |
|
||||
| fds | Nintendo Famicom Disk System | Mesen | Nestopia UE,<br>FCEUmm,<br>NES.emu **(Standalone)**,<br>iNES **(Standalone)**,<br>Nesoid **(Standalone)** | Yes | Single archive or ROM file |
|
||||
| flash | Adobe Flash | Ruffle **(Standalone)** | | No | Single .swf file |
|
||||
| flash | Adobe Flash | Ruffle **(Standalone)** | SWF Player **(Standalone)** | No | Single .swf file |
|
||||
| fm7 | Fujitsu FM-7 | MAME4droid 2024 [FM-7 Diskette] **(Standalone)** | MAME4droid 2024 [FM-7 Tape] **(Standalone)**,<br>MAME4droid 2024 [FM-7 Software list] **(Standalone)**,<br>MAME4droid 2024 [FM77AV Diskette] **(Standalone)**,<br>MAME4droid 2024 [FM77AV Tape] **(Standalone)**,<br>MAME4droid 2024 [FM77AV Software list] **(Standalone)** | Yes | For tape files you need to manually start the cassette player from the MAME menu after the "load" command, as well as entering the "run" command after loading is complete |
|
||||
| fmtowns | Fujitsu FM Towns | MAME4droid 2024 **(Standalone)** | | Yes | See the specific _Fujitsu FM Towns_ section in the user guide |
|
||||
| fpinball | Future Pinball | _Placeholder_ | | | |
|
||||
|
|
@ -768,13 +824,13 @@ The **@** symbol indicates that the emulator is _deprecated_ and will be removed
|
|||
| naomi | Sega NAOMI | Flycast | Flycast **(Standalone)** | Yes | Single archive file + .chd file in subdirectory if GD-ROM game |
|
||||
| naomi2 | Sega NAOMI 2 | Flycast | Flycast **(Standalone)** | Yes | Single archive file + .chd file in subdirectory if GD-ROM game |
|
||||
| naomigd | Sega NAOMI GD-ROM | Flycast | Flycast **(Standalone)** | Yes | Single archive file + .chd file in subdirectory if GD-ROM game |
|
||||
| n3ds | Nintendo 3DS | Citra | Citra **(Standalone)**,<br>Citra Canary **(Standalone)**,<br>Citra MMJ **(Standalone)**,<br>Lime3DS **(Standalone)**,<br>Panda3DS **(Standalone)** | No | Single ROM file |
|
||||
| n3ds | Nintendo 3DS | Citra | Citra **(Standalone)**,<br>Citra Canary **(Standalone)**,<br>Citra MMJ **(Standalone)**,<br>Mandarine **(Standalone)**,<br>Lime3DS **(Standalone)**,<br>Panda3DS **(Standalone)** | No | Single ROM file |
|
||||
| n64 | Nintendo 64 | Mupen64Plus-Next | M64Plus FZ **(Standalone)**,<br>Mupen64Plus AE **(Standalone)**,<br>ParaLLEl N64 | No | Single archive or ROM file |
|
||||
| n64dd | Nintendo 64DD | Mupen64Plus-Next | M64Plus FZ **(Standalone)**,<br>Mupen64Plus AE **(Standalone)**,<br>ParaLLEl N64 | Yes | |
|
||||
| nds | Nintendo DS | melonDS DS | melonDS,<br>melonDS **(Standalone)**,<br>melonDS Nightly **(Standalone)**,<br>DeSmuME,<br>DeSmuME 2015,<br>DraStic **(Standalone)**,<br>NooDS **(Standalone)** | No | Single archive or ROM file |
|
||||
| neogeo | SNK Neo Geo | FinalBurn Neo | Geolith,<br>NEO.emu **(Standalone)**,<br>MAME4droid 2024 **(Standalone)**,<br>MAME4droid **(Standalone)** | Yes | See the specific _Arcade and Neo Geo_ section in the user guide |
|
||||
| neogeocd | SNK Neo Geo CD | NeoCD | FinalBurn Neo,<br>MAME4droid 2024 **(Standalone)** | Yes | .chd (NeoCD and MAME4droid 2024 only) or .cue file |
|
||||
| neogeocdjp | SNK Neo Geo CD [Japan] | NeoCD | FinalBurn Neo,<br>MAME4droid 2024 **(Standalone)** | Yes | .chd (NeoCD and MAME4droid 2024 only) or .cue file |
|
||||
| neogeocd | SNK Neo Geo CD | NeoCD | MAME4droid 2024 **(Standalone)** | Yes | .chd (NeoCD and MAME4droid 2024 only) or .cue file |
|
||||
| neogeocdjp | SNK Neo Geo CD [Japan] | NeoCD | MAME4droid 2024 **(Standalone)** | Yes | .chd (NeoCD and MAME4droid 2024 only) or .cue file |
|
||||
| nes | Nintendo Entertainment System | Mesen | Nestopia UE,<br>FCEUmm,<br>QuickNES,<br>NES.emu **(Standalone)**,<br>iNES **(Standalone)**,<br>Nesoid **(Standalone)** | No | Single archive or ROM file |
|
||||
| ngage | Nokia N-Gage | EKA2L1 **(Standalone)** | | Yes | See the specific _Symbian and Nokia N-Gage_ section in the User guide |
|
||||
| ngp | SNK Neo Geo Pocket | Beetle NeoPop | RACE,<br>NGP.emu **(Standalone)** | No | Single archive or ROM file |
|
||||
|
|
@ -790,7 +846,7 @@ The **@** symbol indicates that the emulator is _deprecated_ and will be removed
|
|||
| pcengine | NEC PC Engine | Beetle PCE | Beetle PCE FAST,<br>Beetle SuperGrafx,<br>PCE.emu **(Standalone)** | No | Single archive or ROM file |
|
||||
| pcenginecd | NEC PC Engine CD | Beetle PCE | Beetle PCE FAST,<br>Beetle SuperGrafx,<br>PCE.emu **(Standalone)** | Yes | |
|
||||
| pcfx | NEC PC-FX | Beetle PC-FX | | Yes | |
|
||||
| pico8 | PICO-8 Fantasy Console | Fake-08 | Retro8 | No | See the specific _PICO-8_ section in the User guide |
|
||||
| pico8 | PICO-8 Fantasy Console | Fake-08 | Retro8,<br>Infinity **(Standalone)** | No | See the specific _PICO-8_ section in the User guide |
|
||||
| plus4 | Commodore Plus/4 | VICE xplus4 | | No | Single archive or image file for tape, cartridge or single-diskette games, .m3u playlist for multi-diskette games |
|
||||
| pokemini | Nintendo Pokémon Mini | PokeMini | | No | |
|
||||
| ports | Ports | ECWolf (Wolfenstein 3D) | NXEngine (Cave Story),<br>OpenLara (Tomb Raider),<br>Super Bros War | Yes for ECWolf | |
|
||||
|
|
@ -840,12 +896,12 @@ The **@** symbol indicates that the emulator is _deprecated_ and will be removed
|
|||
| vectrex | GCE Vectrex | vecx | MAME4droid 2024 **(Standalone)** | Yes for MAME4droid 2024 | Single archive or ROM file |
|
||||
| vic20 | Commodore VIC-20 | VICE xvic | | No | Single archive or tape, cartridge or diskette image file |
|
||||
| videopac | Philips Videopac G7000 | O2EM | MAME4droid 2024 **(Standalone)** | Yes | Single archive or ROM file |
|
||||
| virtualboy | Nintendo Virtual Boy | Beetle VB | | No | |
|
||||
| virtualboy | Nintendo Virtual Boy | Beetle VB | Virtual Virtual Boy **(Standalone)** | No | Single archive or ROM file |
|
||||
| vpinball | Visual Pinball | Visual Pinball **(Standalone)** | | No | See the specific _Visual Pinball_ section in the user guide |
|
||||
| vsmile | VTech V.Smile | MAME4droid 2024 **(Standalone)** | | Yes | Single archive or ROM file |
|
||||
| wasm4 | WASM-4 Fantasy Console | WASM-4 | | No | Single .wasm file |
|
||||
| wii | Nintendo Wii | Dolphin | Dolphin **(Standalone)**,<br>Dolphin MMJR **(Standalone)**,<br>Dolphin MMJR2 **(Standalone)** | No | |
|
||||
| wiiu | Nintendo Wii U | _Placeholder_ | | | |
|
||||
| wiiu | Nintendo Wii U | Cemu **(Standalone)** | | No | See the specific _Nintendo Wii U_ section in the user guide |
|
||||
| windows | Microsoft Windows | Winlator Cmod Glibc **(Standalone)** | Winlator Cmod PRoot **(Standalone)** | No | See the _Winlator_ section elsewhere in this document |
|
||||
| windows3x | Microsoft Windows 3.x | DOSBox-Pure | | No | |
|
||||
| windows9x | Microsoft Windows 9x | DOSBox-Pure | | No | |
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
# ES-DE Frontend - Changelog
|
||||
|
||||
## Version 3.1.1 / 3.1.1-39 (in development)
|
||||
## Version 3.1.1 / 3.1.1-39
|
||||
|
||||
**Release date:** TBD
|
||||
**Release date:** 2024-12-13
|
||||
|
||||
### Release overview
|
||||
|
||||
|
|
@ -10,7 +10,7 @@ This release adds support for four more languages, reduces the memory footprint
|
|||
|
||||
On Android the default audio driver has been changed from AAudio to OpenSL ES which should decrease audio latency on many devices. There is however a new menu entry in the Sound settings menu that makes it possible to easily revert to AAudio in case of issues with the OpenSL ES driver. Also for Android there is now experimental support for running ES-DE in multi-window mode on tablets and other devices that support this.
|
||||
|
||||
In addition to the above there are a number of bug fixes and other minor improvements.
|
||||
In addition to the above there are a number of bug fixes and other improvements.
|
||||
|
||||
### Detailed list of changes
|
||||
|
||||
|
|
|
|||
|
|
@ -1868,7 +1868,7 @@ Here's an example es_systems.xml file for Android:
|
|||
<path>%ROMPATH%/psx</path>
|
||||
<extension>.bin .BIN .cbn .CBN .ccd .CCD .chd .CHD .cue .CUE .ecm .ECM .exe .EXE .img .IMG .iso .ISO .m3u .M3U .mdf .MDF .mds .MDS .minipsf .MINIPSF .pbp .PBP .psexe .PSEXE .psf .PSF .toc .TOC .z .Z .znx .ZNX .7z .7Z .zip .ZIP</extension>
|
||||
<command label="Beetle PSX">%EMULATOR_RETROARCH% %EXTRA_CONFIGFILE%=/storage/emulated/0/Android/data/%ANDROIDPACKAGE%/files/retroarch.cfg %EXTRA_LIBRETRO%=mednafen_psx_libretro_android.so %EXTRA_ROM%=%ROM%</command>
|
||||
<command label="DuckStation (Standalone)">%EMULATOR_DUCKSTATION% %EXTRABOOL_resumeState%=false %EXTRA_bootPath%=%ROMSAF%</command>
|
||||
<command label="DuckStation (Standalone)">%EMULATOR_DUCKSTATION% %ACTIVITY_CLEAR_TASK% %ACTIVITY_CLEAR_TOP% %EXTRABOOL_resumeState%=false %EXTRA_bootPath%=%ROMSAF%</command>
|
||||
<platform>psx</platform>
|
||||
<theme>psx</theme>
|
||||
</system>
|
||||
|
|
|
|||
|
|
@ -1873,7 +1873,7 @@ Here's an example es_systems.xml file for Android:
|
|||
<path>%ROMPATH%/psx</path>
|
||||
<extension>.bin .BIN .cbn .CBN .ccd .CCD .chd .CHD .cue .CUE .ecm .ECM .exe .EXE .img .IMG .iso .ISO .m3u .M3U .mdf .MDF .mds .MDS .minipsf .MINIPSF .pbp .PBP .psexe .PSEXE .psf .PSF .toc .TOC .z .Z .znx .ZNX .7z .7Z .zip .ZIP</extension>
|
||||
<command label="Beetle PSX">%EMULATOR_RETROARCH% %EXTRA_CONFIGFILE%=/storage/emulated/0/Android/data/%ANDROIDPACKAGE%/files/retroarch.cfg %EXTRA_LIBRETRO%=mednafen_psx_libretro_android.so %EXTRA_ROM%=%ROM%</command>
|
||||
<command label="DuckStation (Standalone)">%EMULATOR_DUCKSTATION% %EXTRABOOL_resumeState%=false %EXTRA_bootPath%=%ROMSAF%</command>
|
||||
<command label="DuckStation (Standalone)">%EMULATOR_DUCKSTATION% %ACTIVITY_CLEAR_TASK% %ACTIVITY_CLEAR_TOP% %EXTRABOOL_resumeState%=false %EXTRA_bootPath%=%ROMSAF%</command>
|
||||
<platform>psx</platform>
|
||||
<theme>psx</theme>
|
||||
</system>
|
||||
|
|
|
|||
22
THEMES.md
22
THEMES.md
|
|
@ -755,16 +755,20 @@ The following languages are supported:
|
|||
| :------------ | :----------------------- | :----------------------- |
|
||||
| en_US | English (United States) | English (United States) |
|
||||
| en_GB | English (United Kingdom) | English (United Kingdom) |
|
||||
| ca_ES | Catalan | Català |
|
||||
| de_DE | German | Deutsch |
|
||||
| es_ES | Spanish (Spain) | Español (España) |
|
||||
| fr_FR | French | Français |
|
||||
| it_IT | Italian | Italiano |
|
||||
| nl_NL | Dutch | Nederlands |
|
||||
| pl_PL | Polish | Polski |
|
||||
| pt_BR | Portuguese (Brazil) | Português (Brasil) |
|
||||
| ro_RO | Romanian | Română |
|
||||
| ru_RU | Russian | Русский |
|
||||
| sv_SE | Swedish | Svenska |
|
||||
| ja_JP | Japanese | 日本語 |
|
||||
| zh_CN | Simplified Chinese | 简体中文 |
|
||||
| ja_JP | Japanese | 日本語 |
|
||||
| ko_KR | Korean | 한국어 |
|
||||
| zh_CN | Simplified Chinese | 简体中文 |
|
||||
|
||||
Note that the native name is what is shown inside the _UI Settings_ menu for the _Theme Language_ and _Application Language_ settings.
|
||||
|
||||
|
|
@ -1895,6 +1899,11 @@ Properties:
|
|||
- This property makes it possible to size the text relative to the overall item size. If using this and also defining a text background color using `textBackgroundColor` or `textSelectedBackgroundColor` then this color will still fill the entire item size.
|
||||
- Minimum value is `0.2` and maximum value is `1`
|
||||
- Default is `1`
|
||||
* `textBackgroundCornerRadius` - type: FLOAT
|
||||
- Setting this property higher than zero applies rounded corners to the text background, assuming it has a color set. The radius is a percentage of the screen width. Note that the maximum allowed value is quite arbitrary as the renderer will in practice limit the maximum roundness so it can never go beyond half the text background height.
|
||||
- Minimum value is `0` and maximum value is `0.5`
|
||||
- Default is `0` (corners are not rounded)
|
||||
- This property can only be used if `textBackgroundColor` has a value defined.
|
||||
* `textColor` - type: COLOR
|
||||
- Default is `000000FF`
|
||||
* `textBackgroundColor` - type: COLOR
|
||||
|
|
@ -2101,7 +2110,7 @@ Properties:
|
|||
- Minimum value is `0.2` and maximum value is `1`
|
||||
- Default is `1`
|
||||
* `backgroundCornerRadius` - type: FLOAT
|
||||
- Setting this property higher than zero applies rounded corners to the image defined by `backgroundImage`. The radius is a percentage of the screen width and not directly related to the image size. This makes it possible to apply identically sized corners regardless of image dimensions. The size is calculated internally with `itemScale` and `backgroundRelativeScale` set to `1`. Note that the maximum allowed value is quite arbitrary as the renderer will in practice limit the maximum roundness so it can never go beyond half the width or height. It means that setting this property sufficiently high will turn a perfectly square image into a perfectly round one.
|
||||
- Setting this property higher than zero applies rounded corners to the image defined by `backgroundImage`, or to the colored rectangle if `backgroundColor` has been defined without using a background image. The radius is a percentage of the screen width and not directly related to the background size. This makes it possible to apply identically sized corners regardless of image dimensions. The size is calculated internally with `itemScale` and `backgroundRelativeScale` set to `1`. Note that the maximum allowed value is quite arbitrary as the renderer will in practice limit the maximum roundness so it can never go beyond half the width or height. It means that setting this property sufficiently high will turn a perfectly square background into a perfectly round one.
|
||||
- Minimum value is `0` and maximum value is `0.5`
|
||||
- Default is `0` (corners are not rounded)
|
||||
* `backgroundColor` - type: COLOR
|
||||
|
|
@ -2124,7 +2133,7 @@ Properties:
|
|||
- Valid values are `bottom`, `middle` or `top`
|
||||
- Default is `top`
|
||||
* `selectorCornerRadius` - type: FLOAT
|
||||
- Setting this property higher than zero applies rounded corners to the image defined by `backgroundImage`. The radius is a percentage of the screen width and not directly related to the image size. This makes it possible to apply identically sized corners regardless of image dimensions. The size is calculated internally with `itemScale` and `selectorRelativeScale` set to `1`. Note that the maximum allowed value is quite arbitrary as the renderer will in practice limit the maximum roundness so it can never go beyond half the width or height. It means that setting this property sufficiently high will turn a perfectly square image into a perfectly round one.
|
||||
- Setting this property higher than zero applies rounded corners to the image defined by `selectorImage`, or to the colored rectangle if `selectorColor` has been defined without using a selector image. The radius is a percentage of the screen width and not directly related to the selector size. This makes it possible to apply identically sized corners regardless of image dimensions. The size is calculated internally with `itemScale` and `selectorRelativeScale` set to `1`. Note that the maximum allowed value is quite arbitrary as the renderer will in practice limit the maximum roundness so it can never go beyond half the width or height. It means that setting this property sufficiently high will turn a perfectly square selector into a perfectly round one.
|
||||
- Minimum value is `0` and maximum value is `0.5`
|
||||
- Default is `0` (corners are not rounded)
|
||||
* `selectorColor` - type: COLOR
|
||||
|
|
@ -2144,6 +2153,11 @@ Properties:
|
|||
- This property makes it possible to size the text relative to the overall item size.
|
||||
- Minimum value is `0.2` and maximum value is `1`
|
||||
- Default is `1`
|
||||
* `textBackgroundCornerRadius` - type: FLOAT
|
||||
- Setting this property higher than zero applies rounded corners to the text background, assuming it has a color set. The radius is a percentage of the screen width. Note that the maximum allowed value is quite arbitrary as the renderer will in practice limit the maximum roundness so it can never go beyond half the text background height.
|
||||
- Minimum value is `0` and maximum value is `0.5`
|
||||
- Default is `0` (corners are not rounded)
|
||||
- This property can only be used if `textBackgroundColor` has a value defined.
|
||||
* `textColor` - type: COLOR
|
||||
- Default is `000000FF`
|
||||
* `textBackgroundColor` - type: COLOR
|
||||
|
|
|
|||
|
|
@ -347,6 +347,8 @@ Instructions on how to customize the es_systems.xml file can be found in [INSTAL
|
|||
|
||||
In addition to the above it's also possible to customize the find rules via the `es_find_rules.xml` file. The logic is essentially identical to what is described for es_systems.xml, and details regarding this file can be found in [INSTALL-DEV.md](INSTALL-DEV.md#es_find_rulesxml) as well.
|
||||
|
||||
While the es_systems.xml and es_find_rules.xml files for Android in principle work identically to the desktop ports, there are still some important differences as far as the syntax is concerned. For this reason there's a specific section in the [INSTALL-DEV.md](INSTALL-DEV.md#es_find_rulesxml-and-es_systemsxml-on-android) document that covers the Android configuration.
|
||||
|
||||
## Migrating from EmulationStation
|
||||
|
||||
**IMPORTANT!!! IMPORTANT!!! IMPORTANT!!!**
|
||||
|
|
@ -3625,7 +3627,7 @@ The metadata for a game is updated by scraping or by manual editing it using the
|
|||
|
||||
**Check for application updates** _Not available for some builds_
|
||||
|
||||
By default a check for new ES-DE versions will be done on every application startup and a notification will be displayed if there is a new release available for download. Using this option the frequency of these checks can be set to _Always_, _Daily_, _Weekly_, _Monthly_ or _Never_. This setting is not available on some platforms and package formats such as the Linux AUR release and the semi-official FreeBSD and Raspberry Pi releases where pre-built packages are not provided.
|
||||
By default a check for new ES-DE versions will be done on every application startup and a notification will be displayed if there is a new release available for download. Using this option the frequency of these checks can be set to _Always_, _Daily_, _Weekly_, _Monthly_ or _Never_. This setting is not available on some platforms and package formats such as the Android app store releases, the Linux AUR release and the semi-official FreeBSD and Raspberry Pi releases where pre-built packages are not provided.
|
||||
|
||||
**Include prereleases in update checks** _Always enabled for prereleases_
|
||||
|
||||
|
|
|
|||
68
USERGUIDE.md
68
USERGUIDE.md
|
|
@ -345,6 +345,8 @@ Instructions on how to customize the es_systems.xml file can be found in [INSTAL
|
|||
|
||||
In addition to the above it's also possible to customize the find rules via the `es_find_rules.xml` file. The logic is essentially identical to what is described for es_systems.xml, and details regarding this file can be found in [INSTALL.md](INSTALL.md#es_find_rulesxml) as well.
|
||||
|
||||
While the es_systems.xml and es_find_rules.xml files for Android in principle work identically to the desktop ports, there are still some important differences as far as the syntax is concerned. For this reason there's a specific section in the [INSTALL.md](INSTALL.md#es_find_rulesxml-and-es_systemsxml-on-android) document that covers the Android configuration.
|
||||
|
||||
## Migrating from EmulationStation
|
||||
|
||||
**IMPORTANT!!! IMPORTANT!!! IMPORTANT!!!**
|
||||
|
|
@ -600,6 +602,8 @@ Themes are downloaded from their respective GitHub or GitLab sites using _Git_ (
|
|||
|
||||
If you have manually downloaded any of the themes from the [official themes list](https://gitlab.com/es-de/themes/themes-list) then these would need to be downloaded again as they will not contain the necessary information required by the theme downloader. A dialog will be presented to inform you about this and the theme directory will be renamed by adding the _DISABLED extension to its name. To conserve disk space it's a good idea to manually delete these _DISABLED directories outside of ES-DE. Alternatively you could just completely delete the theme from the user interface using the _Y_ button and start a fresh download.
|
||||
|
||||
On Android specifically all theme directories that were previously renamed with the _DISABLED suffix are automatically deleted every time the theme downloader is started. This is the case as Android prevents direct access to the theme directory due to it being located on application-internal storage, meaning it's not possible to manually delete these directories.
|
||||
|
||||
If you have customized a theme by for instance modifying any of its XML files, then this will be highlighted with an exclamation mark and the text _LOCAL CHANGES_ in the theme downloader interface. If you attempt to fetch updates for such a theme you will be asked a question of whether to overwrite your local changes, or whether to cancel. If you have however added additional files to the theme that are not included in the theme repository, then these will not interfere and you can go ahead and fetch theme updates without any risk of having your local files being deleted. But there is a special (although unlikely) situation, if you add files that are not part of the theme repository but that are later added by the theme developer as well, then your local copies of any such files will be ovewritten when fetching theme updates.
|
||||
|
||||
In worst case there could be a situation where a repository is corrupted and the theme downloader can't properly identify or handle the corruption. In this case you will have to rename or delete that directory. This could also apply to the actual themes list repository. The latter is named _themes-list_ so by just deleting this directory (i.e. `~/ES-DE/themes/themes-list`) you'll reset the theme downloader to its initial state.
|
||||
|
|
@ -700,8 +704,10 @@ The following emulators are supported in AppImage format when using the bundled
|
|||
| macintosh | SheepShaver | SheepShaver*.AppImage |
|
||||
| n3ds | Citra | citra-qt*.AppImage |
|
||||
| n3ds | Lime3DS | lime3ds.AppImage |
|
||||
| n3ds | Mandarine | mandarine-qt.AppImage |
|
||||
| n3ds | Panda3DS | Alber-*.AppImage |
|
||||
| n64/n64dd | Rosalie's Mupen GUI | RMG*.AppImage |
|
||||
| nds | melonDS | melonDS*.AppImage |
|
||||
| ngage/symbian | EKA2L1 | EKA2L1*.AppImage |
|
||||
| ps2 | PCSX2 | pcsx2*.AppImage |
|
||||
| ps2 | Play! | Play!*.AppImage |
|
||||
|
|
@ -807,6 +813,8 @@ The following manually downloaded emulators are supported when using the bundled
|
|||
| pico8 | PICO-8 | pico-8/pico8 |
|
||||
| psvita | Vita3K | Vita3K/Vita3K |
|
||||
| samcoupe | SimCoupé | simcoupe/simcoupe |
|
||||
| saturn/saturnjp | Kronos | kronos/kronos |
|
||||
| scummvm | DREAMM | dreamm/dreamm |
|
||||
| switch | Ryujinx | publish/Ryujinx |
|
||||
| switch | Ryujinx | publish/Ryujinx.Ava |
|
||||
| trs-80 | sdl2trs | sdl2trs/sdl2trs |
|
||||
|
|
@ -1473,9 +1481,11 @@ How to configure each emulator is far beyond the scope of this document, but the
|
|||
|
||||
For this platform there are two basic approaches for how the setup could be done; either to present each game as a single entry inside ES-DE, or to retain each game's directory structure. The first alternative is more user-friendly, tidy and requires less setup but basically restricts the emulator selection to the DOSBox-Pure RetroArch core. There is an alternative way to setup single entries to work with all DOSBox forks, but it has some drawbacks as discussed below.
|
||||
|
||||
If you want to emulate older DOS games and applications then there's also support for the VirtualXT RetroArch core, but this emulator can only run .img and .zip files and it probably won't be able to run most games from the 1990s. For these reasons this documentation only covers DOSBox.
|
||||
If you want to emulate older DOS games and applications then there's also support for the VirtualXT RetroArch core, but this emulator can only run .img and .zip files and it probably won't be able to run most games from the 1990s. For these reasons this documentation does not cover VirtualXT in more detail.
|
||||
|
||||
If you prefer to present the games as single entries you could compress each game directory into a ZIP file with either the .zip or .dosz file extension. On game launch a menu will be displayed by DOSBox-Pure, asking which file inside the archive you would like to execute. This makes it possible to select the actual game file, or for example a setup utility like SETUP.EXE or INSTALL.EXE. Attempting to launch such an archive file with any other DOSBox fork will fail, or not work as expected.
|
||||
Additionally, for a limited set of LucasArts games [DREAMM](https://aarongiles.com/dreamm) can be used. Note that DREAMM works a bit differently than both DOSBox and VirtualXT in that it just receives the game directory as an argument on game launch and will autodetect the game based on the content of this directory. This also means that DREAMM does not support launching of .zip files, i.e. the games need to be unpacked into separate directories. You can however use the _directories interpreted as a files_ functionality to present them as single entries in the gamelist view instead of as folders that you would have to go into to launch the games.
|
||||
|
||||
Moving on to the DOSBox setup, if you prefer to present the games as single entries you could compress each game directory into a ZIP file with either the .zip or .dosz file extension. On game launch a menu will be displayed by DOSBox-Pure, asking which file inside the archive you would like to execute. This makes it possible to select the actual game file, or for example a setup utility like SETUP.EXE or INSTALL.EXE. Attempting to launch such an archive file with any other DOSBox fork will fail, or not work as expected.
|
||||
|
||||
Here's an example of a .zip archive setup for use with DOSBox-Pure:
|
||||
```
|
||||
|
|
@ -2421,6 +2431,14 @@ A final alternative is to use _folder links_ to keep the directory structure int
|
|||
|
||||
If you're using the Flatpak release of ScummVM on Linux then you need to manually grant the application the necessary permissions using Flatseal or similar, otherwise you won't be able to launch any games.
|
||||
|
||||
**DREAMM**
|
||||
|
||||
For Linux, macOS and Windows there's an alternative to using ScummVM for a limited set of games, more specifically those from LucasArts. For these games [DREAMM](https://aarongiles.com/dreamm) can be used instead. It works a bit differently than ScummVM in that games will be autodetected based on the content of the game directory. So the way ES-DE launches these games is to pass the directory of the launched game file to DREAMM which will then autodetect which game it is. This means the ScummVM setup described above can be used without any extra configuration. Here's an example setup of two games, one using a game file inside a normal folder, and one using the _directories interpreted as a files_ approach:
|
||||
```
|
||||
~/ROMs/scummvm/dott/dott.scummvm
|
||||
~/ROMs/scummvm/monkey.scummvm/monkey.scummvm
|
||||
```
|
||||
|
||||
### Sony PlayStation 3
|
||||
|
||||
There are two ways to add PS3 games to ES-DE, by using shortcuts or by adding game directories directly to the ~/ROMs/ps3 folder and interpreting these as files. Shortcuts is generally the way to go as it's easier to setup and for HDD/pkg games it's the only way to make it work unless you manually create symlinks to the internal RPCS3 directory structure. So another benefit with shortcuts is consistency as both HDD/pkg games and disc-based games will be setup in the same manner. This also means that the same RPCS3 emulator entry can be used to launch every game. The drawback to using shortcuts is that they're not portable, if you change the location of RPCS3 or your games, you need to manually update the shortcuts as well.
|
||||
|
|
@ -2473,9 +2491,7 @@ When using this setup method you need to set the alternative emulator to _RPCS3
|
|||
There is also a video on the official ES-DE YouTube channel on how to setup Vita3K:\
|
||||
https://www.youtube.com/watch?v=4U8yAUJ9-Tk
|
||||
|
||||
On Android and Windows the Vita3K installation is straightforward, but on Linux you may need to place the emulator in a location recognized by ES-DE. See the [Using manually downloaded emulators on Linux](USERGUIDE.md#using-manually-downloaded-emulators-on-linux) section of this guide for more details. If using a Linux distribution that provides Vita3K via the repository (such as the AUR on Arch/Manjaro) then you can skip this step and install the emulator using your OS package manager.
|
||||
|
||||
Although a macOS release of Vita3K seems to be in the works this does not seem to be readily available for download so there is currently no macOS support for this system in ES-DE.
|
||||
On Android, macOS and Windows the Vita3K installation is straightforward, but on Linux you may need to place the emulator in a location recognized by ES-DE. See the [Using manually downloaded emulators on Linux](USERGUIDE.md#using-manually-downloaded-emulators-on-linux) section of this guide for more details. If using a Linux distribution that provides Vita3K via the repository (such as the AUR on Arch/Manjaro) then you can skip this step and install the emulator using your OS package manager.
|
||||
|
||||
After you've installed Vita3K, add your games via the GUI and make sure that they work correctly when launched from inside the emulator.
|
||||
|
||||
|
|
@ -2529,17 +2545,15 @@ As the Nokia N-Gage was running Symbian it may seem like the _ngage_ and _symbia
|
|||
|
||||
**Android**
|
||||
|
||||
For the symbian system it's possible to launch individual games directly from ES-DE, but for the ngage system this is unfortunately not possible. Instead the EKA2L1 user interface will open on game launch and you need to manually start your game from inside the emulator. For both the symbian and ngage systems all games need to be installed upfront in EKA2L1.
|
||||
For both the ngage and symbian systems it's possible to launch individual games directly from ES-DE, although they need to be installed upfront in EKA2L1.
|
||||
|
||||
For N-Gage games it's a good idea to just create empty dummy files with the .ngage file extensions inside the ROMs/ngage directory. These will then appear as indvidual games inside ES-DE and you can add metadata to them, scrape them etc.
|
||||
|
||||
For Symbian games you can export JSON launch files from EKA2L1 that can be run directly from ES-DE. Just open EKA2L1, long press the game icon and select _Create launch file_ from the popup list. Then just select the ROMs/symbian directory and the file will be saved there and game launching from ES-DE will work as expected.
|
||||
After installing the games in EKA2L1, long press the game icon and select _Create launch file_ from the popup list which will export a JSON file for the game. Then select the directory where the file should be saved, i.e. ROMs/ngage or ROMs/symbian. Following this, game launching from ES-DE will work as expected.
|
||||
|
||||
Here's an example setup:
|
||||
```
|
||||
/storage/emulated/0/ROMs/ngage/Asphalt 2.ngage
|
||||
/storage/emulated/0/ROMs/ngage/Bomberman.ngage
|
||||
/storage/emulated/0/ROMs/ngage/CallofDuty.ngage
|
||||
/storage/emulated/0/ROMs/ngage/Asphalt 2.json
|
||||
/storage/emulated/0/ROMs/ngage/Bomberman.json
|
||||
/storage/emulated/0/ROMs/ngage/CallofDuty.json
|
||||
/storage/emulated/0/ROMs/symbian/Animal Farm.json
|
||||
/storage/emulated/0/ROMs/symbian/AnotherWorld.json
|
||||
```
|
||||
|
|
@ -3256,7 +3270,7 @@ If the selected theme has multilingual support then you can select between its s
|
|||
|
||||
**Application language**
|
||||
|
||||
Sets the language for the application user interface. If this option is set to _automatic_ then the language will be auto-detected, which means ES-DE will attempt to use whatever language has been selected in the operating system language settings. If there are no translations available in ES-DE for this precise language then a fallback will be done to the closest match, such as _Svenska_ instead of _Svenska (Finland)_. If no close match is available then ES-DE will revert to the default language which is _English (United States)_. It's also possible to explicitly select a supported language, which will override whatever has been set by the operating system. Note that the onboarding configurator for the Android release is unaffected by this setting. Also note that language auto-detection does not work on the Steam Deck when running in game mode, so there it's necessary to select a language explicitly. If you accidentally select a language you didn't intend to, then you can access the application language setting via the second menu entry from the top after opening the main menu, and then after entering this sub-menu by pressing the down button eight times.
|
||||
Sets the language for the application user interface. If this option is set to _automatic_ then the language will be autodetected, which means ES-DE will attempt to use whatever language has been selected in the operating system language settings. If there are no translations available in ES-DE for this precise language then a fallback will be done to the closest match, such as _Svenska_ instead of _Svenska (Finland)_. If no close match is available then ES-DE will revert to the default language which is _English (United States)_. It's also possible to explicitly select a supported language, which will override whatever has been set by the operating system. Note that the onboarding configurator for the Android release is unaffected by this setting. Also note that language autodetection does not work on the Steam Deck when running in game mode, so there it's necessary to select a language explicitly. If you accidentally select a language you didn't intend to, then you can access the application language setting via the second menu entry from the top after opening the main menu, and then after entering this sub-menu by pressing the down button eight times.
|
||||
|
||||
**Quick system select**
|
||||
|
||||
|
|
@ -3458,6 +3472,10 @@ Whether to use a shader to render a slight horizontal blur which somewhat simula
|
|||
|
||||
Various sound settings.
|
||||
|
||||
**Audio driver (requires restart)** _(Android only)_
|
||||
|
||||
This setting makes it possible to select between the _OpenSL ES_ and _AAudio_ audio drivers. Note that this is a preference only, if OpenSL ES is not available on your device then ES-DE will automatically revert to using AAudio and log that a fallback took place to the es_log.txt file. It's generally recommended to keep the driver set to its default value OpenSL ES as that offers lower audio latency for most devices.
|
||||
|
||||
**System volume** _(Linux and Windows only)_
|
||||
|
||||
As the name implies, this sets the overall system volume and not the volume specifically for ES-DE. The volume change is applied when leaving the sound settings menu and not immediately when moving the slider.
|
||||
|
|
@ -3607,7 +3625,7 @@ The metadata for a game is updated by scraping or by manual editing it using the
|
|||
|
||||
**Check for application updates** _Not available for some builds_
|
||||
|
||||
By default a check for new ES-DE versions will be done on every application startup and a notification will be displayed if there is a new release available for download. Using this option the frequency of these checks can be set to _Always_, _Daily_, _Weekly_, _Monthly_ or _Never_. This setting is not available on some platforms and package formats such as the Linux AUR release and the semiofficial FreeBSD, Raspberry Pi and Haiku releases where pre-built packages are not provided.
|
||||
By default a check for new ES-DE versions will be done on every application startup and a notification will be displayed if there is a new release available for download. Using this option the frequency of these checks can be set to _Always_, _Daily_, _Weekly_, _Monthly_ or _Never_. This setting is not available on some platforms and package formats such as the Android app store releases, the Linux AUR release and the semi-official FreeBSD and Raspberry Pi releases where pre-built packages are not provided.
|
||||
|
||||
**Include prereleases in update checks** _Always enabled for prereleases_
|
||||
|
||||
|
|
@ -4109,7 +4127,7 @@ The **@** symbol indicates that the emulator is _deprecated_ and will be removed
|
|||
| atarist | Atari ST [also STE and Falcon] | Hatari | Hatari **(Standalone)** | Yes | Single archive or image file for single-diskette games, .m3u playlist for multi-diskette games |
|
||||
| atarixe | Atari XE | Atari800 | Atari800 **(Standalone)**,<br>Altirra **(Standalone)** [W] | Yes except for Altirra | |
|
||||
| atomiswave | Sammy Corporation Atomiswave | Flycast | Flycast **(Standalone)**,<br>Flycast Dojo **(Standalone)**,<br>Demul **(Standalone)** [W] | Depends | Single archive file |
|
||||
| bbcmicro | Acorn Computers BBC Micro | MAME **(Standalone)** | | Yes | Single archive or diskette image file |
|
||||
| bbcmicro | Acorn Computers BBC Micro | MAME **(Standalone)** | BeebEm **(Standalone)** [W] | Yes | Single archive (MAME only) or diskette image file |
|
||||
| c64 | Commodore 64 | VICE x64sc Accurate | VICE x64sc Accurate **(Standalone)**,<br>VICE x64 Fast,<br>VICE x64 SuperCPU,<br>VICE x128,<br>Frodo | No | Single archive or image file for tape, cartridge or single-diskette games, .m3u playlist for multi-diskette games |
|
||||
| cdimono1 | Philips CD-i | SAME CDi | CDi 2015 @,<br>MAME **(Standalone)** | Yes | Single .bin/.cue pair |
|
||||
| cdtv | Commodore CDTV | PUAE | PUAE 2021,<br>FS-UAE **(Standalone)**,<br>Amiberry **(Standalone)** [LM] | Yes | See the specific _Commodore Amiga and CDTV_ section elsewhere in this guide |
|
||||
|
|
@ -4126,7 +4144,7 @@ The **@** symbol indicates that the emulator is _deprecated_ and will be removed
|
|||
| daphne | Daphne Arcade LaserDisc Emulator | Hypseus [Daphne] **(Standalone)** | Hypseus [Singe] **(Standalone)**,<br>MAME - Current,<br>MAME **(Standalone)**,<br>DirkSimple | Depends | See the specific _LaserDisc Games_ section elsewhere in this guide |
|
||||
| desktop | Desktop Applications | _Suspend ES-DE_ | _Keep ES-DE running_,<br> _AppImage (Suspend ES-DE)_ [L],<br> _AppImage (Keep ES-DE running)_ [L] | No | See the specific _Ports and desktop applications_ section elsewhere in this guide |
|
||||
| doom | Doom | PrBoom | PrBoom+ **(Standalone)**,<br>Boom 3 [LW],<br>Boom 3 xp [LW],<br> _Shortcut or script_ | No | |
|
||||
| dos | DOS (PC) | DOSBox-Pure | DOSBox-Core,<br>DOSBox-SVN,<br>DOSBox-X **(Standalone)**,<br>DOSBox Staging **(Standalone)**,<br>VirtualXT | No | See the specific _DOS / PC_ section elsewhere in this guide |
|
||||
| dos | DOS (PC) | DOSBox-Pure | DOSBox-Core,<br>DOSBox-SVN,<br>DOSBox-X **(Standalone)**,<br>DOSBox Staging **(Standalone)**,<br>DREAMM **(Standalone)**,<br>VirtualXT | No | See the specific _DOS / PC_ section elsewhere in this guide |
|
||||
| dragon32 | Dragon Data Dragon 32 | MAME Dragon 32 [Tape] **(Standalone)** | MAME Dragon 32 [Cartridge] **(Standalone)**,<br>MAME Dragon 64 [Tape] **(Standalone)**,<br>MAME Dragon 64 [Cartridge] **(Standalone)**,<br>XRoar Dragon 32 **(Standalone)**,<br>XRoar Dragon 64 **(Standalone)** | Yes | See the specific _Dragon 32 and Tano Dragon_ section elsewhere in this guide |
|
||||
| dreamcast | Sega Dreamcast | Flycast | Flycast **(Standalone)**,<br>Flycast Dojo **(Standalone)**,<br>Redream **(Standalone)**,<br>Demul **(Standalone)** [W] | No | In separate folder interpreted as a file, with .m3u playlist if multi-disc game |
|
||||
| easyrpg | EasyRPG Game Engine | EasyRPG | EasyRPG Player **(Standalone)** | No | See the specific _EasyRPG Game Engine_ section elsewhere in this guide |
|
||||
|
|
@ -4179,7 +4197,7 @@ The **@** symbol indicates that the emulator is _deprecated_ and will be removed
|
|||
| msxturbor | MSX Turbo R | blueMSX | openMSX **(Standalone)**,<br>openMSX No Machine **(Standalone)** | Yes | |
|
||||
| mugen | M.U.G.E.N Game Engine | Ikemen GO **(Standalone)** | | No | See the specific _M.U.G.E.N Game Engine_ section elsewhere in this guide |
|
||||
| multivision | Othello Multivision | Gearsystem | Mesen **(Standalone)** [LW] | No | Single archive or ROM file |
|
||||
| n3ds | Nintendo 3DS | Citra [LW],<br>Citra **(Standalone)** [M] | Citra 2018 [LW],<br>Citra **(Standalone)** [LW],<br>Lime3DS **(Standalone)**,<br>Panda3DS **(Standalone)** | No | Single ROM file |
|
||||
| n3ds | Nintendo 3DS | Citra [LW],<br>Citra **(Standalone)** [M] | Citra 2018 [LW],<br>Citra **(Standalone)** [LW]<br>Mandarine **(Standalone)**,<br>Lime3DS **(Standalone)**,<br>Panda3DS **(Standalone)** | No | Single ROM file |
|
||||
| n64 | Nintendo 64 | Mupen64Plus-Next | Mupen64Plus **(Standalone)**,<br>ParaLLEl N64,<br>simple64 **(Standalone)** [LW],<br>Rosalie's Mupen GUI **(Standalone)** [LW],<br>Project64 **(Standalone)** [W],<br>ares **(Standalone)**,<br>sixtyforce **(Standalone)** [M] | No | Single archive or ROM file |
|
||||
| n64dd | Nintendo 64DD | ParaLLEl N64 [LW],<br>Mupen64Plus-Next [M] | Mupen64Plus-Next [LW],<br>ParaLLEl N64 [M],<br>Rosalie's Mupen GUI **(Standalone)** [LW],<br>ares **(Standalone)** | Yes | See the specific _Nintendo 64DD_ section elsewhere in this guide |
|
||||
| naomi | Sega NAOMI | Flycast | Flycast **(Standalone)**,<br>Flycast Dojo **(Standalone)**,<br>Demul **(Standalone)** [W] | Yes | Single archive file + .chd file in subdirectory if GD-ROM game |
|
||||
|
|
@ -4187,8 +4205,8 @@ The **@** symbol indicates that the emulator is _deprecated_ and will be removed
|
|||
| naomigd | Sega NAOMI GD-ROM | Flycast | Flycast **(Standalone)**,<br>Flycast Dojo **(Standalone)** | Yes | Single archive file + .chd file in subdirectory if GD-ROM game |
|
||||
| nds | Nintendo DS | melonDS DS | melonDS @,<br>melonDS **(Standalone)**,<br>DeSmuME,<br>DeSmuME 2015,<br>DeSmuME **(Standalone)** [L],<br>SkyEmu **(Standalone)**,<br>NooDS **(Standalone)** [LW] | No | Single archive or ROM file |
|
||||
| neogeo | SNK Neo Geo | FinalBurn Neo | FinalBurn Neo **(Standalone)** [LW],<br>Geolith,<br>MAME **(Standalone)** | Yes | See the specific _Arcade and Neo Geo_ section elsewhere in this guide |
|
||||
| neogeocd | SNK Neo Geo CD | NeoCD | FinalBurn Neo,<br>FinalBurn Neo **(Standalone)** [L],<br>MAME **(Standalone)** | Yes | .chd (NeoCD and MAME only) or .cue file |
|
||||
| neogeocdjp | SNK Neo Geo CD [Japan] | NeoCD | FinalBurn Neo,<br>FinalBurn Neo **(Standalone)** [L],<br>MAME **(Standalone)** | Yes | .chd (NeoCD and MAME only) or .cue file |
|
||||
| neogeocd | SNK Neo Geo CD | NeoCD | FinalBurn Neo,<br>FinalBurn Neo **(Standalone)** [LW],<br>MAME **(Standalone)** | Yes | .chd (NeoCD and MAME only) or .cue file |
|
||||
| neogeocdjp | SNK Neo Geo CD [Japan] | NeoCD | FinalBurn Neo,<br>FinalBurn Neo **(Standalone)** [LW],<br>MAME **(Standalone)** | Yes | .chd (NeoCD and MAME only) or .cue file |
|
||||
| nes | Nintendo Entertainment System | Mesen | Mesen **(Standalone)** [LW],<br>Nestopia UE,<br>Nestopia UE **(Standalone)** [L],<br>FCEUmm,<br>QuickNES,<br>puNES **(Standalone)** [LW],<br>Mednafen **(Standalone)**,<br>ares **(Standalone)**,<br>ares FDS **(Standalone)**,<br>jgenesis **(Standalone)** [LW],<br>3dSen **(Wine)** [L],<br>3dSen **(Proton)** [L],<br>3dSen **(Standalone)** [W] | No | Single archive or ROM file. For NES games in 3D see the specific _Nintendo NES and Famicom in 3D_ section elsewhere in this guide |
|
||||
| ngage | Nokia N-Gage | EKA2L1 [Mounted] **(Standalone)** | EKA2L1 [Installed] **(Standalone)**,<br>EKA2L1 [Mounted] **(Wine)** [L],<br>EKA2L1 [Installed] **(Wine)** [L] | Yes | See the specific _Symbian and Nokia N-Gage_ section elsewhere in this guide |
|
||||
| ngp | SNK Neo Geo Pocket | Beetle NeoPop | RACE,<br>Mednafen **(Standalone)**,<br>ares **(Standalone)** | No | Single archive or ROM file |
|
||||
|
|
@ -4197,7 +4215,7 @@ The **@** symbol indicates that the emulator is _deprecated_ and will be removed
|
|||
| openbor | OpenBOR Game Engine | OpenBOR **(Standalone)** [LW] | | No | See the specific _OpenBOR_ section elsewhere in this guide |
|
||||
| oric | Tangerine Computer Systems Oric | MAME **(Standalone)** | Oricutron **(Standalone)** | Yes | See the specific _Tangerine Computer Systems Oric_ section elsewhere in this guide |
|
||||
| palm | Palm OS | Mu | | | |
|
||||
| pc | IBM PC | DOSBox-Pure | DOSBox-Core,<br>DOSBox-SVN,<br>DOSBox-X **(Standalone)**,<br>DOSBox Staging **(Standalone)**,<br>VirtualXT | No | See the specific _DOS / PC_ section elsewhere in this guide |
|
||||
| pc | IBM PC | DOSBox-Pure | DOSBox-Core,<br>DOSBox-SVN,<br>DOSBox-X **(Standalone)**,<br>DOSBox Staging **(Standalone)**,<br>DREAMM **(Standalone)**,<br>VirtualXT | No | See the specific _DOS / PC_ section elsewhere in this guide |
|
||||
| pc88 | NEC PC-8800 Series | QUASI88 | QUASI88 **(Standalone)** | Yes | |
|
||||
| pc98 | NEC PC-9800 Series | Neko Project II Kai | Neko Project II | | |
|
||||
| pcarcade | PC Arcade Systems | Wine **(Standalone)** [L],<br> _Shortcut or script_ [MW] | Proton **(Standalone)** [L],<br> _AppImage_ [L],<br> _Shortcut or script_ [L] | No | |
|
||||
|
|
@ -4212,15 +4230,15 @@ The **@** symbol indicates that the emulator is _deprecated_ and will be removed
|
|||
| ps3 | Sony PlayStation 3 | RPCS3 Shortcut **(Standalone)** | RPCS3 Directory **(Standalone)** | Yes | See the specific _Sony PlayStation 3_ section elsewhere in this guide |
|
||||
| ps4 | Sony PlayStation 4 | _Placeholder_ | | | |
|
||||
| psp | Sony PlayStation Portable | PPSSPP | PPSSPP **(Standalone)** | No | Single disc image file |
|
||||
| psvita | Sony PlayStation Vita | Vita3K **(Standalone)** [LW] | | Yes | See the specific _Sony PlayStation Vita_ section elsewhere in this guide |
|
||||
| psvita | Sony PlayStation Vita | Vita3K **(Standalone)** | | Yes | See the specific _Sony PlayStation Vita_ section elsewhere in this guide |
|
||||
| psx | Sony PlayStation | Beetle PSX | Beetle PSX HW,<br>PCSX ReARMed,<br>SwanStation,<br>DuckStation **(Standalone)**,<br>Mednafen **(Standalone)** | Yes | .chd file for single-disc games, .m3u playlist for multi-disc games |
|
||||
| pv1000 | Casio PV-1000 | MAME - Current | MAME **(Standalone)** | No | Single archive or ROM file |
|
||||
| quake | Quake | TyrQuake | vitaQuake 2,<br>vitaQuake 2 [Rogue],<br>vitaQuake 2 [Xatrix],<br>vitaQuake 2 [Zaero],<br>vitaQuake 3 [LW],<br> _Shortcut or script_ | No | |
|
||||
| samcoupe | MGT SAM Coupé | SimCoupé **(Standalone)** | | No | Single archive or ROM file |
|
||||
| satellaview | Nintendo Satellaview | Snes9x - Current | Snes9x 2010,<br>Snes9x 2005 Plus,<br>Snes9x **(Standalone)**,<br>bsnes,<br>bsnes-hd,<br>bsnes-mercury Accuracy,<br>bsnes **(Standalone)** [LW],<br>Mesen-S,<br>Mesen **(Standalone)** [LW],<br>ares **(Standalone)** | | |
|
||||
| saturn | Sega Saturn | Beetle Saturn | Kronos [LW],<br>YabaSanshiro [LW],<br>Yabause,<br>Mednafen **(Standalone)**,<br>SSF **(Standalone)** [W] | Yes | .chd file for single-disc games, .m3u playlist for multi-disc games |
|
||||
| saturnjp | Sega Saturn [Japan] | Beetle Saturn | Kronos [LW],<br>YabaSanshiro [LW],<br>Yabause,<br>Mednafen **(Standalone)**,<br>SSF **(Standalone)** [W] | Yes | .chd file for single-disc games, .m3u playlist for multi-disc games |
|
||||
| scummvm | ScummVM Game Engine | ScummVM | ScummVM **(Standalone)** | No | See the specific _ScummVM_ section elsewhere in this guide |
|
||||
| saturn | Sega Saturn | Beetle Saturn | Kronos [LW],<br>Kronos **(Standalone)** [LW],<br>YabaSanshiro [LW],<br>Yaba Sanshiro 2 **(Standalone)** [W],<br>Yabause,<br>Mednafen **(Standalone)**,<br>SSF **(Standalone)** [W] | Yes | .chd file for single-disc games, .m3u playlist for multi-disc games |
|
||||
| saturnjp | Sega Saturn [Japan] | Beetle Saturn | Kronos [LW],<br>Kronos **(Standalone)** [LW],<br>YabaSanshiro [LW],<br>Yaba Sanshiro 2 **(Standalone)** [W],<br>Yabause,<br>Mednafen **(Standalone)**,<br>SSF **(Standalone)** [W] | Yes | .chd file for single-disc games, .m3u playlist for multi-disc games |
|
||||
| scummvm | ScummVM Game Engine | ScummVM | ScummVM **(Standalone)**,<br>DREAMM **(Standalone)** | No | See the specific _ScummVM_ section elsewhere in this guide |
|
||||
| scv | Epoch Super Cassette Vision | MAME - Current | MAME **(Standalone)** | Yes | Single archive or ROM file |
|
||||
| sega32x | Sega Mega Drive 32X | PicoDrive | ares **(Standalone)** | No | Single archive or ROM file |
|
||||
| sega32xjp | Sega Super 32X [Japan] | PicoDrive | ares **(Standalone)** | No | Single archive or ROM file |
|
||||
|
|
@ -4254,7 +4272,7 @@ The **@** symbol indicates that the emulator is _deprecated_ and will be removed
|
|||
| vectrex | GCE Vectrex | vecx | MAME - Current,<br>MAME **(Standalone)** | Yes for MAME | Single archive or ROM file |
|
||||
| vic20 | Commodore VIC-20 | VICE xvic | VICE xvic **(Standalone)** | No | Single archive or tape, cartridge or diskette image file |
|
||||
| videopac | Philips Videopac G7000 | O2EM | MAME - Current,<br>MAME **(Standalone)** | Yes | Single archive or ROM file |
|
||||
| virtualboy | Nintendo Virtual Boy | Beetle VB | Mednafen **(Standalone)** | No | |
|
||||
| virtualboy | Nintendo Virtual Boy | Beetle VB | Mednafen **(Standalone)** | No | Single archive or ROM file |
|
||||
| vpinball | Visual Pinball | Visual Pinball **(Standalone)** | | No | See the specific _Visual Pinball_ section elsewhere in this guide |
|
||||
| vsmile | VTech V.Smile | MAME - Current | MAME **(Standalone)** | Yes | Single archive or ROM file |
|
||||
| wasm4 | WASM-4 Fantasy Console | WASM-4 | | No | Single .wasm file |
|
||||
|
|
|
|||
Loading…
Reference in a new issue