Linux and the launcher

[DomiStyle]

The launcher refused to start for me on Fedora by default but setting the launch arguments to DOTNET_BUNDLE_EXTRACT_BASE_DIR=.cache %command% did the trick.

On Steam Deck I'm stuck in an update loop, i.e. every time the launcher starts it wants to install the game files. Didn't look into what's going on there yet but it seems like some people got it working.

There's also an issue with the launcher not accepting mouse input right after the install for some reason. Stopping the launcher in Steam and starting it again is enough to resolve it.

No other issues so far.

[Je12emy]

Bump, I am also interesting on playing in Linux.

[eldewrito2]

The launcher refused to start for me on Fedora by default but setting the launch arguments to DOTNET_BUNDLE_EXTRACT_BASE_DIR=.cache %command% did the trick.

We'll try and find a workaround for that issue.

On Steam Deck I'm stuck in an update loop, i.e. every time the launcher starts it wants to install the game files. Didn't look into what's going on there yet but it seems like some people got it working.

Ensure that you are running the launcher.exe from the folder that you installed to. Depending on where it is ran from (the presence of the manifest.json file) it will either act as an Installer or the Game Launcher / Updater. This is because ElDewrito is mostly portable - It can be installed to multiple folders.

There's also an issue with the launcher not accepting mouse input right after the install for some reason. Stopping the launcher in Steam and starting it again is enough to resolve it.

I'm not entirely sure what would cause that but it will be looked into, and I'll get back to you if it turns out to be a bug with the launcher itself.

Let us know if you run into any other Linux or Steam Deck issues. We'll be happy to take a look and improve support.

Check back with our guide also as it is being updated constantly.

[DomiStyle]

Thanks for the feedback!

Ensure that you are running the launcher.exe from the folder that you installed to. Depending on where it is ran from (the presence of the manifest.json file) it will either act as an Installer or the Game Launcher / Updater. This is because ElDewrito is mostly portable - It can be installed to multiple folders.

That makes sense, might I suggest making the default path the same path as where the launcher.exe is run from? Alternatively, maybe allow the manifest.json to point to another folder and add one if the launcher.exe is located somewhere else?

Seems like something that could happen to Windows users as well when they try to launch the launcher.exe in their download folder.

If you add the game on Steam on the Steam Deck, it will always start the original launcher.exe so if you install to the default path you get the loop. I installed it the same way I did on my desktop just now (into the folder where the launcher.exe is located) and things work fine.

I'm not entirely sure what would cause that but it will be looked into, and I'll get back to you if it turns out to be a bug with the launcher itself.

Might be related to the launcher opening/closing multiple times after a new install. It's reproducible on Steam Deck on desktop mode as well, but not in gaming mode.

The launcher also seems to have issues drawing when in this state, so if you put another window in front and remove it again the launcher will still mirror the window that was in front of it.

Let us know if you run into any other Linux or Steam Deck issues. We'll be happy to take a look and improve support.

One more thing I noticed is that Steam Input gets broken by the launcher in desktop mode for some reason. I can't use the trackpad/triggers/software keyboard when the launcher is focused, only the touchscreen works.

Game runs really well on the Steam Deck otherwise.