The Irritable Medic
Published
The game will not launch without this command.
Occasionally the music would loop and keep looping until the next audio change or the savegame was reloaded. This seemed to happen more frequently in later episodes. I believe I've seen this happen with other RPGMaker games in Windows, so I don't necessarily consider it a Linux/Proton issue. It was, however, very annoying.
Sometimes had to press a key to switch weapons or items a few times before it would respond. No frame of reference with Windows to tell if this was normal for the game or not.
Maxing LOD caused a little slowness, but switching on Advanced Grass had a massive, detrimental impact on framerate to the point that it was nearly unplayable.
Game would launch and close without a screen or an error unless the game was started with Proton 4.11-13.
Launches with a black screen, music, nothing else
Attempts to run game with Proton 4.11-11, 4.2-9 and 3.16-9 failed; was met with music, a completely black screen, and no menu interface.
This is more than what occurred with launching the native version, which just opened a browser window to nw:blank and a NW.JS text animation.
This fixed the all-black (and in 5.0-9, all-white) screen with no interface. Can now see and use full interface and actually play the game.
Windowed only. Using keyboard commands to engage fullscreen did not work, and there were no options for it in the game itself.
The controls locked up on completion of the Hungry Ghost puzzle if the ghosts were interacted with afterwards. The dog was unresponsive and only showed idle animations. Be sure to save before puzzle completion to avoid having to restart the game (only one save slot).
Also tried:
Native Linux version: Launches to NW.JS text animation, nothing else
Proton 5.0-9, no launch options: White screen, music, no interface
Proton 5.0-9, w/ PROTON_USE_WINED3D: Black screen, music, no interface
Proton 4.11-13 w/ PROTON_NO_D3D11: Full interface, music, only tested as far as main menu
Solution may not work for everyone; might need to wait for fixes. Temperamental, at least partially due to EAC. Otherwise, fine if it works.
Tried setting the newest DXVK via protonfixes --gui during earlier stages of the testing, but it didn't seem to help at the time. Can't discount it doing something to help, so listing it here.
Slightly during some sections of character creation, but no issues so far in the chapel at the start.
No problems once multiplayer was actually working, but there were initial problems with not being able to log in, finally resolved by enabling the Bleeding Edge beta version of Proton Experimental, and then restarting my system.
While testing other solutions found elsewhere:
Renaming eossdk-win64-shipping.dll and eossdk-win64-shipping.so to EOSSDK-Win64-Shipping.dll and EOSSDK-Win64-Shipping.so as found elsewhere to correct a spelling bug did not help me sign into multiplayer and, with some Proton versions, threw an "inappropriate activity detected" error on game launch instead of just saying it couldn't log in, so I didn't use it.
During install, the game stuck during DirectX installation. Killing game and Steams services and restarting Steam and hitting Play got rid of the installer message, but then it wouldn't launch the game. Tried the aforementioned Protontricks DXVK attempt, didn't help. Restarting Steam into Offline Mode didn't help. Verifying files didn't help (no listed file issues). Tried a symlink between start_protected_game.exe and eldenring.exe, but it didn't help so I unlinked it. I'd tried just launching the game regularly, using Proton-7.0rc3-GE-1, then Proton Experimental (without Bleeding Edge) and the last is what finally helped, but ONLY after a system reboot as well.
Running the Bleeding Edge beta allowed multiplayer to work with no errors.
On all attempts, the game didn't like to close cleanly. It will close the window, but still play audio in the background until you hit Stop.
Steam kept stalling on the DirectX install script on launch. Tried to launch the game directly, then with GE-Proton7-25, then with Proton Experimental and it still stalled at this point. Closed Steam and ended stalled Steam-related processes, removed the 1332010 folder from the Steam compatdata folder, then relaunched Steam and tried again with Proton Experimental and the game launched properly after a delay.
Once I was able to launch the game, it played perfectly up until where I stopped testing (the start of Dead City).
Installed fine, takes forever to launch, server join blocked by EAC
EVRIMA branch. Multiple runners tried, Proton-6.8-GE-1, Experimental, GE-Proton8-23, GE-Proton8-24, a few random ones in the 5, 6, and 7 series. Also tried RADV_DEBUG=nocompute %command% and removing compatibility folder 376210 as recommended here. It will launch, launch after a VERY long delay, or not launch at all. When it does launch, I can't join a server due to EAC issues. Just reinstalled it, but also tried to verify just in case; it didn't help.
