| Both sides previous revision Previous revision Next revision | Previous revision |
| not_supported_emulators [2022/06/13 06:55] – added mention of system-explanations atari | not_supported_emulators [2023/02/28 05:01] (current) – [I want <X> emulator in Batocera. I know it is possible, and want to help, what can I do?] Fix channel name reference, and make it a link maximumentropy |
|---|
| * Even if WINE itself could be theoretically ported to other platforms, most Windows programs themselves are still x86 only/depend on x86-based libraries. The same applies to Proton. | * Even if WINE itself could be theoretically ported to other platforms, most Windows programs themselves are still x86 only/depend on x86-based libraries. The same applies to Proton. |
| * In the meantime however, you can use [[systems:moonlight|Moonlight]] to video stream your PC games to your SBC. | * In the meantime however, you can use [[systems:moonlight|Moonlight]] to video stream your PC games to your SBC. |
| | |
| | ==== Why can't I install Flatpaks on my ARM device? ==== |
| | |
| | * Most Flatpak packages are only provided for Linux on the x86/x86_64 platform. Even if Flatpak were supported on the ARM build of Batocera, not much could be installed (notably: Steam is x86 only). |
| |
| ==== Why isn't Dolphin (Wii/Gamecube) supported on my (old) SBC/handheld? ==== | ==== Why isn't Dolphin (Wii/Gamecube) supported on my (old) SBC/handheld? ==== |
| |
| * The Reicast/Flycast code is not ready for the aarch64 architecture yet. | * The Reicast/Flycast code is not ready for the aarch64 architecture yet. |
| | |
| | ==== Why isn't Redream supported on my RPi 3/RPi Zero 2/other ARM board? ==== |
| | |
| | * Redream is a closed-source emulator, we can only work with what binaries [[https://redream.io/download|they have provided]]. |
| | * On that note, Redream seems to perform worse on Raspberry Pi 4 than Flycast does. It may not even be working at playable speeds on weaker boards. |
| |
| ==== Why isn't Apple II supported on certain older Batocera versions? ==== | ==== Why isn't Apple II supported on certain older Batocera versions? ==== |
| |
| * If you're a developer (or just really handy with Python scripting, it's not too difficult to work out) you can try your hand at [[:batocera.linux_buildroot_modifications#how_to_add_an_emulator|implementing it yourself]]. You may need to reference [[:notable_files|certain notable files and/or folders]] for the live install if you don't want to go all the way through with [[:compile_batocera.linux|compiling Batocera from scratch]], however if Batocera does not already include the necessary dependencies/libraries that your emulator needs you may need to do just that. | * If you're a developer (or just really handy with Python scripting, it's not too difficult to work out) you can try your hand at [[:batocera.linux_buildroot_modifications#how_to_add_an_emulator|implementing it yourself]]. You may need to reference [[:notable_files|certain notable files and/or folders]] for the live install if you don't want to go all the way through with [[:compile_batocera.linux|compiling Batocera from scratch]], however if Batocera does not already include the necessary dependencies/libraries that your emulator needs you may need to do just that. |
| * If you're just a user but still want to help, you can request for the inclusion of a certain emulator in the #wish channel on the Discord. If the emulator is being blocked from being included in Batocera for other reasons, you can //politely encourage// the developer of the emulator to get in touch with Batocera to see what needs to be changed/implemented in the emulator itself to get it working in Batocera (most actively-maintained software have a certain procedure to follow for making feature requests like this, you should read up on their specific documentation first). Generally speaking, old/unmaintained or Windows-only emulators will be unlikely to be included in Batocera without extreme amounts of refactoring, testing and patching. Cemu has had exceptional circumstances to make it one of the more WINE-compatible emulators out there (read: it natively supports Vulkan, only needs a few easy-to-maintain Windows libraries, has a community-maintained patch to make it more WINE-friendly, etc.), most Windows-only software does not have this luxury. That being said, we've added multiple Windows-only emulators already, so it may just be a matter of time and patience. | * If you're just a user but still want to help, you can request for the inclusion of a certain emulator in the [[https://discord.com/channels/357518249883205632/758737725884596224|#suggestions]] channel on the Discord. If the emulator is being blocked from being included in Batocera for other reasons, you can //politely encourage// the developer of the emulator to get in touch with Batocera to see what needs to be changed/implemented in the emulator itself to get it working in Batocera (most actively-maintained software have a certain procedure to follow for making feature requests like this, you should read up on their specific documentation first). Generally speaking, old/unmaintained or Windows-only emulators will be unlikely to be included in Batocera without extreme amounts of refactoring, testing and patching. Cemu has had exceptional circumstances to make it one of the more WINE-compatible emulators out there (read: it natively supports Vulkan, only needs a few easy-to-maintain Windows libraries, has a community-maintained patch to make it more WINE-friendly, etc.), most Windows-only software does not have this luxury. That being said, we've added multiple Windows-only emulators already, so it may just be a matter of time and patience. |
| |