Browse Source
[docs] Obtanium, installing mods, external ES-DE config, section about CFW and settings (#3678)
[docs] Obtanium, installing mods, external ES-DE config, section about CFW and settings (#3678)
Signed-off-by: lizzie <lizzie@eden-emu.dev> Reviewed-on: https://git.eden-emu.dev/eden-emu/eden/pulls/3678 Reviewed-by: DraVee <chimera@dravee.dev> Reviewed-by: CamilleLaVey <camillelavey99@gmail.com> Co-authored-by: lizzie <lizzie@eden-emu.dev> Co-committed-by: lizzie <lizzie@eden-emu.dev>pull/3693/head
lizzie
3 days ago
committed by
crueter
crueter
No known key found for this signature in database
GPG Key ID: 425ACD2D4830EBC6
10 changed files with 473 additions and 120 deletions
-
8README.md
-
3docs/README.md
-
100docs/user/AddGamesToSRM.md
-
11docs/user/CFW.md
-
4docs/user/Graphics.md
-
206docs/user/Mods.md
-
19docs/user/README.md
-
54docs/user/Settings.md
-
129docs/user/SteamROM.md
-
59docs/user/ThirdParty.md
@ -1,100 +0,0 @@ |
|||
# Importing Games into Steam with Steam Rom Manager |
|||
|
|||
Use this when you want to import your games inside Eden into Steam to launch with artwork from Steam Game Mode without needing to launch Eden first. |
|||
|
|||
**Click [Here](https://evilperson1337.notion.site/Importing-Games-into-Steam-with-Steam-Rom-Manager-2b757c2edaf680d7a491c92b138f1fcc) for a version of this guide with images & visual elements.** |
|||
|
|||
--- |
|||
|
|||
### Pre-Requisites |
|||
|
|||
- Steam Deck Set up and Configured |
|||
- Eden set up and Configured |
|||
- Internet Access |
|||
|
|||
--- |
|||
|
|||
## Steps |
|||
|
|||
1. Press the **STEAM** button and then go to *Power → Switch to Desktop* to enter the Desktop mode. |
|||
|
|||
1. Install ***Steam ROM Manager***, there are 2 ways you can accomplish this, either manually or through [*EmuDeck*](https://www.emudeck.com/#downloads). |
|||
|
|||
--- |
|||
|
|||
### Manual Installation |
|||
|
|||
1. Open the *Discover Store* and search for *Steam ROM Manager.* |
|||
2. Select the **Install** button to install the program. |
|||
|
|||
--- |
|||
|
|||
### Installing Through *EmuDeck* |
|||
|
|||
<aside> |
|||
|
|||
***NOTE***: This assumes you have already set up EmuDeck, if not - just run through the guided installation and select *Steam ROM Manager* as one of the options. |
|||
|
|||
</aside> |
|||
|
|||
1. Open **EmuDeck**, then navigate to *Manage Emulators.* |
|||
2. Scroll down to the bottom of the page to the *Manage your Tools & Frontends* section. Click **Steam ROM Manager**. |
|||
|
|||
3. Click the **Install** button on the right hand side to install it. |
|||
|
|||
--- |
|||
|
|||
2. Open the Start Menu and Launch ***Steam ROM Manager*** |
|||
|
|||
1. The program will now launch and show you a window with parsers. |
|||
|
|||
<aside> |
|||
|
|||
***TIP***: Your layout may look different depending on how you installed *Steam ROM Manager*. You may need to go to **Settings → Theme** and change it to *Classic* to follow along. |
|||
|
|||
</aside> |
|||
|
|||
2. Switch off all Parsers by hitting the *Toggle Parsers* switch. |
|||
3. Scroll down the list on the left-hand side and look for a parser called *Nintendo Switch - Eden* and switch it on. This parser may not exist depending on how you installed *Steam ROM Manager* (EmuDeck creates it for you). Follow these steps to create it if it is missing. |
|||
|
|||
--- |
|||
### Creating the Eden Parser |
|||
|
|||
1. Select Create Parser and in the *Community Presets* option look for **Nintendo Switch - Yuzu**. |
|||
2. Change the **Parser title** from *Nintendo Switch - Yuzu* to *Nintendo Switch - Eden.* |
|||
3. Hit the **Browse** option under the *ROMs directory* section. Select the directory containing your Switch ROMs. |
|||
4. Under *Steam collections*, you can add a Steam category name. This just organizes the games under a common category in your Steam Library, this is optional but recommended. |
|||
5. Scroll down slightly to the **Executable Configuration → Executable**, select **Browse** and select the Eden AppImage. |
|||
6. Leave everything else the same and hit **Save** to save the parser. |
|||
--- |
|||
|
|||
4. Click the Eden parser to view the options on the right, select **Test** at the bottom of the screen to ensure that *Steam ROM Manager* detects your games correctly. |
|||
1. *Steam ROM Manager* will start to scan the specified ROMs directory and match them to games. Look over the results to ensure they are accurate. If you do not see any entries - check your parsers ROMs directory field. |
|||
1. When you are happy with the results, click the **Add Games** → **Parse** to start the actual Parsing. |
|||
1. The program will now identify the games and pull artwork from [*SteamGridDB*](https://www.steamgriddb.com/). |
|||
2. Review the game matches and ensure everything is there. |
|||
|
|||
--- |
|||
|
|||
### Correcting a Mismatch |
|||
|
|||
If the game is not identified correctly, you may need to tell *Steam ROM Manager* what the game is manually. |
|||
|
|||
1. Hover over the game card and click the magnifying glass icon. |
|||
2. Search for the game on the *Search SteamGridDB* section and scroll through the results, selecting the one you want. |
|||
3. Ensure the *Name* and *Game ID* update in the **Per-App Exceptions** and press **Save and close**. The game should now update. |
|||
|
|||
--- |
|||
|
|||
### Excluding Matches |
|||
|
|||
You may want to tell Steam ROM Manager to ignore some files (updates/DLC/etc.) that it finds in the directory. This is how you do so. |
|||
|
|||
1. Hit the **Exclude Games** button in the bottom right. |
|||
2. Deselect the game you want to exclude, the poster artwork should go dim and the **Number Excluded** number should increment up. Repeat with any other exclusions you want to add. |
|||
3. Hit **Save Excludes** when you are happy with your selections. |
|||
--- |
|||
3. When you are happy with the results, select **Save to Steam** to save the results. |
|||
1. The program will now start writing the entries into the Steam Library. You should get pop up notifications of the progress, but you can monitor the progress by selecting the **Log** on the left-hand side if needed. |
|||
2. Restart Steam to have the changes take effect. Check your library to ensure that your games are there, in a category if you defined one in the parser. |
|||
3. Try to launch a game and ensure everything is working. You are now good to go. |
|||
@ -0,0 +1,11 @@ |
|||
# User Handbook - Custom Firmware (CFW) |
|||
|
|||
At the moment of writing, we do not support CFW such as Atmosphere, due to: |
|||
|
|||
- Lacking the required LLE emulation capabilities to properly emulate the full firmware. |
|||
- Lack of implementation on some of the key internals. |
|||
- Nobody has bothered to do it (PRs always welcome!) |
|||
|
|||
We do however, maintain HLE compatibility with the former mentioned CFW, applications that require Atmosphere to run will run fine in the emulator without any adjustments. |
|||
|
|||
If they don't run - then that's a bug! |
|||
@ -0,0 +1,206 @@ |
|||
# User Handbook - Installing Mods |
|||
|
|||
## General Notes |
|||
|
|||
**Note:** When installing a mod, always read the mod's installation instructions. |
|||
|
|||
This is especially important if a mod uses a framework such as **ARCropolis**, **Skyline**, or **Atmosphere plugins**. In those cases, follow the framework's instructions instead of using Eden's normal mod folder. |
|||
|
|||
For example, **Super Smash Bros. Ultimate** uses such a framework. See the related section below for details. |
|||
|
|||
--- |
|||
|
|||
# Installing Mods for Most Games |
|||
|
|||
1. Right click a game in the game list. |
|||
2. Click **"Open Mod Data Location"**. |
|||
3. Extract the mod into that folder. |
|||
|
|||
Each mod should be placed inside **its own subfolder**. |
|||
|
|||
--- |
|||
|
|||
# Enabling or Disabling Mods |
|||
|
|||
1. Right click the game in the game list. |
|||
2. Click **Configure Game**. |
|||
3. In the **Add-Ons** tab, enable or disable mods, updates, and DLC by ticking or unticking their boxes. |
|||
|
|||
--- |
|||
|
|||
# Important Note About SD Card Paths |
|||
|
|||
Some mods are designed for real Nintendo Switch consoles and refer to the **SD card root**. |
|||
|
|||
The emulated SD card is located at: |
|||
|
|||
``` |
|||
%AppData%\eden\sdmc |
|||
``` |
|||
|
|||
Example: |
|||
|
|||
``` |
|||
Switch instruction: sd:/ultimate/mods |
|||
Eden equivalent: sdmc/ultimate/mods |
|||
``` |
|||
|
|||
--- |
|||
|
|||
# Framework-Based Mods (Super Smash Bros. Ultimate) |
|||
|
|||
Some games require external mod frameworks instead of the built-in mod loader. |
|||
|
|||
The most common example is **Super Smash Bros. Ultimate**. |
|||
|
|||
These mods are installed directly to the **emulated SD card**, not the normal Eden mod folder. |
|||
|
|||
--- |
|||
|
|||
# Installing the ARCropolis Modding Framework |
|||
|
|||
**Note:** Some mod packs bundle ARCropolis with their installer (for example, Smash Ult-S). |
|||
|
|||
--- |
|||
|
|||
## 1. Download ARCropolis |
|||
|
|||
Download the latest release: |
|||
|
|||
https://github.com/Raytwo/ARCropolis/releases/ |
|||
|
|||
--- |
|||
|
|||
## 2. Install ARCropolis |
|||
|
|||
Extract the **`atmosphere`** folder into: |
|||
|
|||
``` |
|||
%AppData%\eden\sdmc |
|||
``` |
|||
|
|||
This is the **emulated SD card directory**. |
|||
|
|||
Verify installation by checking that the following file exists: |
|||
|
|||
``` |
|||
sdmc\atmosphere\contents\01006A800016E000\romfs\skyline\plugins\libarcropolis.nro |
|||
``` |
|||
|
|||
--- |
|||
|
|||
## 3. Download Skyline |
|||
|
|||
Download the latest Skyline release: |
|||
|
|||
https://github.com/skyline-dev/skyline/releases |
|||
|
|||
Skyline used to be bundled with ARCropolis but is now distributed separately to avoid compatibility issues caused by outdated bundled versions. |
|||
|
|||
--- |
|||
|
|||
## 4. Install Skyline |
|||
|
|||
Extract the **`exefs`** folder into: |
|||
|
|||
``` |
|||
sdmc\atmosphere\contents\01006A800016E000 |
|||
``` |
|||
|
|||
The `exefs` folder should be **next to the `romfs` folder**. |
|||
|
|||
Verify installation by checking that the following file exists: |
|||
|
|||
``` |
|||
%AppData%\eden\sdmc\atmosphere\contents\01006A800016E000\exefs\subsdk9 |
|||
``` |
|||
|
|||
--- |
|||
|
|||
## 5. Launch the Game Once |
|||
|
|||
Start the game and make sure you see the **ARCropolis version text on the title screen**. |
|||
|
|||
This will also create the folders required for installing mods. |
|||
|
|||
--- |
|||
|
|||
## 6. Install Smash Ultimate Mods |
|||
|
|||
Install mods inside: |
|||
|
|||
``` |
|||
sdmc\ultimate\mods |
|||
``` |
|||
|
|||
Each mod must be placed inside **its own subfolder**. |
|||
|
|||
Example: |
|||
|
|||
``` |
|||
sdmc\ultimate\mods\ExampleMod |
|||
``` |
|||
|
|||
--- |
|||
|
|||
# Troubleshooting |
|||
|
|||
## ARCropolis text does not appear on startup |
|||
|
|||
Check the following: |
|||
|
|||
- `libarcropolis.nro` exists in: |
|||
|
|||
``` |
|||
sdmc\atmosphere\contents\01006A800016E000\romfs\skyline\plugins |
|||
``` |
|||
|
|||
- `subsdk9` exists in: |
|||
|
|||
``` |
|||
sdmc\atmosphere\contents\01006A800016E000\exefs |
|||
``` |
|||
|
|||
- Files were extracted to: |
|||
|
|||
``` |
|||
%AppData%\eden\sdmc |
|||
``` |
|||
|
|||
--- |
|||
|
|||
## Mods are not loading |
|||
|
|||
Make sure mods are installed inside: |
|||
|
|||
``` |
|||
sdmc\ultimate\mods |
|||
``` |
|||
|
|||
Each mod must have its **own subfolder**. |
|||
|
|||
Correct example: |
|||
|
|||
``` |
|||
sdmc\ultimate\mods\ExampleMod |
|||
``` |
|||
|
|||
Incorrect example: |
|||
|
|||
``` |
|||
sdmc\ultimate\mods\ExampleMod\ExampleMod |
|||
``` |
|||
|
|||
--- |
|||
|
|||
## Installing mods in the wrong folder |
|||
|
|||
ARCropolis mods **do not go in Eden's normal mod folder**. |
|||
|
|||
Do **not** install Smash mods here: |
|||
|
|||
``` |
|||
user\load\01006A800016E000 |
|||
``` |
|||
|
|||
That folder is only used for traditional **RomFS mods**, not ARCropolis. |
|||
@ -0,0 +1,54 @@ |
|||
# User Handbook - Settings |
|||
|
|||
As the emulator continues to grow, so does the number of settings that come and go. |
|||
|
|||
Most of the development adds new settings that enhance performance/compatibility, only to be removed later in newer versions due to newfound discoveries or because they were "a hacky workaround". |
|||
|
|||
As such, this guide will NOT mention those kind of settings, we'd rather mention settings which have a long shelf time (i.e won't get removed in future releases) and are likely to be unchanged. |
|||
|
|||
Some of the options are self explainatory, and they do exactly what they say they do (i.e "Pause when not in focus"); such options will be also skipped due to triviality. |
|||
|
|||
## Foreword |
|||
|
|||
Before touching the settings, please see the game boots with stock options. We try our best to ensure users can boot any game using the default settings. If they don't work, then you may try fiddling with options - but please, first use stock options. |
|||
|
|||
## General |
|||
|
|||
- `General/Force X11 as Graphics Backend`: Wayland on *NIX has prominent issues that are unlikely to be resolved; the kind that are "not our fault, it's Wayland issue", this "temporary" hack forces X11 as the backend, regardless of the desktop manager's default. |
|||
- `General/Enable Gamemode`: This only does anything when you have Feral Interactive's Gamemode library installed somewhere, if you do, this will help boost FPS by telling the OS to explicitly prioritize *this* application for "gaming" - only for *NIX systems. |
|||
- `Hotkeys`: Deceptively to remove a hotkey you must right click and a menu will appear to remove that specific hotkey. |
|||
- `UI/Language`: Changes language *of the interface* NOT the emulated program! |
|||
- `Debug/Enable Auto Stub`: May help to "fix" some games by just lying and saying that everything they do returns "success" instead of outright crashing for any function/service that is NOT implemented. |
|||
- `Debug/Show log in console`: Does as said, note that the program may need to be reopened (Windows) for changes to take effect. |
|||
- `Debug/Flush log output`: Classically, every write to the log is "buffered", that is, changes aren't written to the disk UNTIL the program has decided it is time to write, until then it keeps data in a buffer which resides on RAM. If the program crashes, the OS will automatically discard said buffer (any RAM associated with a dead process is automatically discarded/reused for some other purpose); this means critical data may not be logged to the disk on time, which may lead to missing log lines. Use this if you're wanting to remove that factor when debugging, sometimes a hard crash may "eat" some of the log lines IF this option isn't enabled. |
|||
- `Debug/Disable Macro HLE:` The emulator has HLE emulation of macro programs for Maxwell, this means that some details are purpousefully skipped; this option forces all macro programs to be ran without skipping anything. |
|||
|
|||
## System |
|||
|
|||
- `System/RNG Seed`: Set to 0 (and uncheck) to disable ASLR systemwide (this makes mods like CTGP to stop working); by default it enables ASLR to replicate console behaviour. |
|||
- `Network/Enable Airplane Mode`: Enable this if a game is crashing before loading AND the logs mention anything related to "web" or "internet" services. |
|||
|
|||
## CPU |
|||
|
|||
- `CPU/Virtual table bouncing`: Some games have the tendency to crash on loading due to an indirect bad jump (Pokemon ZA being the worst offender); this option lies to the game and tells it to just pretend it never executed a given function. This is fine for most casual users, but developers of switch applications **must** disable this. This temporary "hack" should hopefully be gone in 6-7 months from now on. |
|||
- `Fastmem`, aka. `CPU/Enable Host MMU`: Enables "fastmem"; a detailed description of fastmem can be found [here](../dynarmic/Design.md#fast-memory-fastmem). |
|||
- `CPU/Unsafe FMA`: Enables deliberate innacurate FMA behaviour which may affect how FMA returns any given operation - this may introduce tiny floating point errors which can cascade in sensitive code (i.e FFmpeg). |
|||
- `CPU/Faster FRSQRTE and FRECPE`: Introduces accuracy errors on square root and reciprocals in exchange for less checks - this introduces inaccuracies with some cases but it's mostly safe. |
|||
- `CPU/Faster ASIMD Instructions`: Skips rounding mode checks for ARM ASIMD instructions - this means some code dpeending on these rounding modes may misbehave. |
|||
- `CPU/Disable address space checks`: Before each memory access, the emulator checks the address is in range, if not it faults; this option makes it so the emulator skips the check entirely (which may be expensive for a myriad of reasons). However at the same time this allows the guest program to "break out" of the emulation context by writing to arbitrary addresses. |
|||
- `CPU/Ignore global monitor`: This relies on a quirk present on x86 to avoid the ARM global monitor emulation, this may increase performance in mutex-heavy contexts (i.e games waiting for next frames or such); but also can cause deadlocks and fun to debug issues. |
|||
|
|||
It is important to note the majority of precision-reducing instructions do not benefit cases where they are not used, which means the performance gains will vary per game. |
|||
|
|||
# Graphics |
|||
|
|||
See also [an extended breakdown of some options](./Graphics.md). |
|||
|
|||
- `Extras/Extended Dynamic State` and `Extras/Vertex Input Dynamic State`: These Vulkan extensions essentially allow you to reuse the same pipeline but just change the state between calls (so called "dynamic state"); the "extended" levels signifies how much state can be placed on this "dynamic" range, for example the amount of depth culling to use can be placed on the dynamic state, avoiding costly reloads and flushes. While this by itself is a fine option, SOME vendors (notably PowerVR and Mali) have problems with anything related to EDS3. EDS3 contains EDS2, and EDS2 contains EDS1. Essentially this means more extended data the driver has to keep track of, at the benefit of avoiding costly flushes. |
|||
- `Advanced/Use persistent cache`: This saves compiled shaders onto the disk, independent of any driver's own disk saved shaders (yes, some drivers, notably NVIDIA, save a secondary shader cache onto disk) - disable this only if you're debugging or working on the GPU backend. This option is meant to massively help to reduce shader stutters (after playing for one session that compiles them). |
|||
- `Advanced/Use Vulkan pipeline cache`: This is NOT the same as `Use persistent cache`; it's a separate flag that tells the Vulkan backend to create pipeline caches, which are a detail that can be used to massively improve performance and remove pipeline creation overhead. This is a Vulkan feature. |
|||
|
|||
## Controls |
|||
|
|||
Most of the controls should work out of the box. If not, please use a joystick calibrator to ensure it's not an issue with your own controller, for example: |
|||
- https://github.com/dkosmari/calibrate-joystick |
|||
Write
Preview
Loading…
Cancel
Save
Reference in new issue