Xargon/ES-DE
1
0
Fork 0
mirror of https://github.com/RetroDECK/ES-DE.git synced 2024-11-25 07:35:38 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Documentation update

Browse source
This commit is contained in:
Leon Styhre 2023-11-09 01:03:37 +01:00
parent b2cb446e35
commit 062753de7c
2 changed files with 7 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
CHANGELOG.md
View file

@ -18,7 +18,6 @@ Some improvements were also made to the systems sorting functionality.
* The Orphaned data cleanup utility will now skip any system where a flatten.txt file is present * The Orphaned data cleanup utility will now skip any system where a flatten.txt file is present
* Changed a number of error messages in the Orphaned data cleanup utility from uppercase to lowercase * Changed a number of error messages in the Orphaned data cleanup utility from uppercase to lowercase
* The application release number is now tracked on startup instead of the application version * The application release number is now tracked on startup instead of the application version
* (Linux) Added fallback find rule entries for Wine and Proton in case they were relocated by AppImageLauncher
* (slate-es-de) Added console graphics for the adam system * (slate-es-de) Added console graphics for the adam system
* Changed the systems sorting platform from "Peripheral" to "Console" for the fds, megacd, megacdjp, n64dd, pcenginecd and satellaview systems * Changed the systems sorting platform from "Peripheral" to "Console" for the fds, megacd, megacdjp, n64dd, pcenginecd and satellaview systems
* Changed the systems sorting platform from "Peripheral" to "Console" for the sega32x, sega32xjp, sega32xna, segacd, sgb, sufami and tg-cd systems * Changed the systems sorting platform from "Peripheral" to "Console" for the sega32x, sega32xjp, sega32xna, segacd, sgb, sufami and tg-cd systems

18
USERGUIDE-DEV.md
View file

@ -867,7 +867,7 @@ The following Windows emulators are supported, and the setup for most of these i
| xbox360 | xenia | xenia/xenia.exe | | xbox360 | xenia | xenia/xenia.exe |
| xbox360 | xenia | xenia/xenia_canary.exe | | xbox360 | xenia | xenia/xenia_canary.exe |
**Fallback config for AppImageLauncher** **Setup for AppImageLauncher**
[AppImageLauncher](https://github.com/TheAssassin/AppImageLauncher) will by default move any AppImage you attempt to run to the root of the ~/Applications directory. This annoyingly also includes files in subdirectories in the ~/Applications tree, so the Wine and Proton AppImages would get relocated there too. [AppImageLauncher](https://github.com/TheAssassin/AppImageLauncher) will by default move any AppImage you attempt to run to the root of the ~/Applications directory. This annoyingly also includes files in subdirectories in the ~/Applications tree, so the Wine and Proton AppImages would get relocated there too.
@ -877,24 +877,20 @@ For instance:
``` ```
Would be moved to: Would be moved to:
``` ```
~/Applications/wine-stable_8.0.2-x86_64_007830d9c8edbf18441ad63ed592f371.AppImage ~/Applications/wine-stable_8.0.2-x86_64_7218a7d163a0ce403cac23ebcb3747a3.AppImage
``` ```
A hash will be applied to the filename as part of the move process. A hash will be applied to the filename as part of the move process.
To be able to launch these AppImages when using AppImageLauncher the following staticpath find rule is included for Wine: To work around this simply symlink the newly moved and renamed AppImage back into the Wine or Proton directory, like so:
``` ```
<entry>~/Applications/wine*.AppImage</entry> cd ~/Applications/Wine
ln -s ../wine-stable_8.0.2-x86_64_7218a7d163a0ce403cac23ebcb3747a3.AppImage .
``` ```
And the following rule is included for Proton: While it's possible to setup a custom find rule entry to look for the Wine and Proton AppImages directly in ~/Applications this is not a good idea as the filename similarities between these two files can lead to a mixup, you really want them separated into their own directories.
```
<entry>~/Applications/wine*roton*.AppImage</entry>
```
This way you'll be able to run Wine and Proton anyway. But note that this is not a reliable solution as there may be a mixup between the Wine and Proton AppImages on game launch due to their filename similarities. However, if you only intend to use one of them, then this will work fine as it can't get mixed up with the other AppImage. An alternative and recommended solution to avoid the symlinking would be to not use AppImageLauncher at all.
An alternative solution would of course be to not use AppImageLauncher.
## Running emulators in fullscreen mode ## Running emulators in fullscreen mode