This commit is contained in:
etjanster 2025-02-04 07:28:27 +01:00
parent 4f175d4481
commit 2905d097e1
2 changed files with 36 additions and 40 deletions

View file

@ -97,22 +97,29 @@ Do not keep DLC and Update files in: `retrodeck/roms/wiiu/`
## Pretendo Account for online play ## Pretendo Account for online play
To create a Pretendo Network account use the following link: [Pretendo: Register Account](https://pretendo.network/account/register). To create a Pretendo Network account.
Then follow the following link: [Pretendo: Install WiiU](https://pretendo.network/docs/install/wiiu) to log in with your Pretendo Network account on a Wii U. 1. Use the provided link to register:
- Existing NNID are not usable on Pretendo Network, you must create a Pretendo account for Pretendo Network. [Pretendo: Register Account](https://pretendo.network/account/register).
Follow the [Cemu: Online Play Guide](https://cemu.cfw.guide/online-play.html) to generate and dump the required user files for your Pretendo Account. 2. Then, follow the instructions to log in with your Pretendo Network account on a Wii U.
[Pretendo: Install WiiU](https://pretendo.network/docs/install/wiiu)
- Note: Existing NNIDs are not usable on Pretendo Network, so you must create a Pretendo account.
3. Follow the guide to generate and dump the required user files for your Pretendo Account:
[Cemu: Online Play Guide](https://cemu.cfw.guide/online-play.html)
**RetroDECK specific file locations:** **RetroDECK specific file locations:**
- Wii U User Accounts `usr` and `sys` folders - Wii U User Accounts `usr` and `sys` folders
- Whatever `MLC Path` in `Options` -> `General settings` is configured to - Located in the `MLC Path` configured in `RetroDECK Configurator` -> `Open Cemu` -> `Options` -> `General settings` (default: `retrodeck/bios/cemu`)
- by default its `retrodeck/bios/cemu`
- `otp.bin` and `seeprom.bin` - `otp.bin` and `seeprom.bin`:
- `~/.var/app/org.retrodeck.retrodeck/data/Cemu` - Located at `~/.var/app/org.retrodeck.retrodeck/data/Cemu`.
## Known issues ## Known issues

View file

@ -1,6 +1,6 @@
# What devices and OS does RetroDECK currently support? # What devices and OS does RetroDECK currently support?
RetroDECK currently only works on x86_64 architecture. RetroDECK supports x86_64 architecture.
## Steam Deck ## Steam Deck
@ -8,25 +8,18 @@ RetroDECK was built for the Steam Deck in mind and started as a project towards
## Linux Desktop ## Linux Desktop
It works, but RetroDECK is still reliant on Steam Input for advanced hotkeys. RetroDECK works on Linux desktops but relies on Steam Input for advanced hotkeys. For the best experience, use a distribution with built-in Game Mode like SteamOS, Bazzite, or ChimeraOS and more.
For the best experience we recommend a distribution that has built in Game Mode like Valves SteamOS, Bazzite, ChimeraOS and so forth.
Game Mode fixes several Steam issues that are present in standard Linux Desktop such as the radials are rendered correctly on screen.
## Other x86_64 Linux Handhelds / Devices ## Other x86_64 Linux Handhelds / Devices
Our community is highly creative and likes putting RetroDECK on new devices. Our community is highly creative and likes putting RetroDECK on new devices.
Many devices are emulating a Playstation, Steam Deck or Xbox controller this it should work out of the box and be able to hook into that corresponding Steam Input Layout. RetroDECK can work on various devices emulating PlayStation, Steam Deck, or Xbox controllers in Steam Input. If a device has custom inputs, contact the RetroDECK Team to help us create a Steam Input profile.
If it does not show up as any known input, The RetroDECK Team might not have been able to create a input profile for a new device as it needs to be bought by the team to add it.
If you own a device that has custom inputs and want to create a Steam Input profile for it, please get it touch with the Team and so we can ship it in a later update.
### Installing Linux & RetroDECK on x86_64 Windows Handelds ### Installing Linux & RetroDECK on x86_64 Windows Handelds
We have user confirmation that RetroDECK does work on the other handhelds that was released with Windows. RetroDECK has been confirmed to work on handhelds released with Windows initially.
## FAQ Devices / OS ## FAQ Devices / OS
@ -34,35 +27,31 @@ We have user confirmation that RetroDECK does work on the other handhelds that w
No, RetroDECK doesn't support Windows currently. No, RetroDECK doesn't support Windows currently.
As an alternative you could try [RetroBat](https://www.retrobat.org/) that offers similar functionality in a Windows environment. You can try [RetroBat](https://www.retrobat.org/) for similar functionality on Windows.
How ever if you install a Linux distribution on your device instead you can try out RetroDECK.
ES-DE does support the Windows as does the emulators, but it is a vastly different landscape. Alternatively, you can install a Linux distribution on your device to use RetroDECK. Supporting Windows would be a major undertaking and would require more developers with Windows experience.
It would be a major undertaking but maybe one day in the future it could be possible.
We would also need more developers with Windows experience to help us with this effort.
### Will you support ARM devices like iOS, MacOS and Android? ### Will you support ARM devices like iOS, MacOS and Android?
No, RetroDECK doesn't support ARM devices currently. No, RetroDECK doesn't support ARM devices currently.
It would be a major undertaking but maybe one day in the future it could be possible. The underlying systems would need to be rewritten due to different emulators and licensing models,
especially on Android where some emulators are open source on x86_64 but closed source on ARM.
We would also need more developers with ARM experience to help us with this effort. Supporting ARM devices would be a major undertaking and would require more developers with ARM experience.
But it would need to be a unique experience as the emulators, other underlying systems would not be the same and would need to be rewritten from the ground up.
It is a vastly different landscape with other licensing models for several of the emulators/systems specially on Android where the X86_64 binary is FOSS while the Android version is closed source.
### Will you support RISC-V? ### Will you support RISC-V?
The idea of a widely accepted open-source architecture is exiting at least. It would be a major undertaking but one day in the far-off future it could be possible as the platform matures and more systems gets compatibility. The idea of supporting RISC-V is exciting, but it as everything else would be a major undertaking.
It might be possible in the far-off future as the platform matures and gains more compatibility.
But supporting RISC-V devices would be a major undertaking and would require more developers with RISC-V experience.
### Will you support other Linux distribution methods such as Snap or AppImage? ### Will you support other Linux distribution methods such as Snap or AppImage?
It's not in our roadmap yet as now the entire buildsystem is based on the flatpak-build that builds the software via the flatpak manifest. It's not in our roadmap yet. Currently, the entire build system is based on flatpak-build.
In the past we evaluated to migrate to **Buildstream** (or similar solutions) and build on to multiple output formats.
But the team is not large enough to migrate and maintain other distribution methods, so we prefer to focus our effort on Flatpak only. The team is not large enough to migrate and maintain other distribution methods.
If someone with knowledge and passion wishes to help us with migrating to a solution and help us maintain it, we are open for a discussion.
However, if someone with knowledge and passion wishes to help with migrating and maintaining it, we are open to discussion.