VerifiedShow Details
Unknown
Game doesn't launch properly with default installation options, or with Proton, even deleting the files in the save folder (like how other people recommend) doesn't fix the issue. But you know what did? Going to the Betas section in the Steam properties menu and selecting "linux32- 32-bit Linux (Legacy)". If you're having problems launching the game I recommend installing this version of the game.
I played the native version without any problems
Runs perfectly
Overall it just worked out of the box. The resolution was automatically set to 1280x800 (which others have commented on) and the controlled worked perfectly. I never had an issue with crashes, input controls or the UI. From a pure technical standpoint the game is flawless, it never dropped from 60FPS (it looks like it's locked to a max of 60 though)
Overall it's a great game for the deck, even though I really didn't enjoy the game itself.
On a 4K TV, the game runs perfectly fine, but some text does not scale with the UI scaling options and is too small to read.
Runs perfectly, and the game is excellent.
Every steam OS version I force fails to load
Crashes with a fatal exception on proton experimental, 9.x, 8.x, 7.x, and 6.x. Also fails to start up uisng native. I'm not seeing any tweak on protondb. They seem to be all for Deck.
I've completed this game using the native Linux port without problems
This game doesn't work with Proton Experimental (2024/07/31), 9.0-2 and 8.0-5 (I haven't tested other versions)
Modified/deleting Settings.sav
Changing the resolution to 1280x800 in the game properties menu, otherwise the game doesn't scale properly.
Steam Cloud saves preventing the Settings.sav from being deleted properly.
White screen upon boot up, game runs in the background as you can hear the menu sounds
Turning off Steam's cloud saves in the properties for this game, then deleting the Settings.sav file in the folder, which is located here
/home/deck/.local/share/DustAET/Save Files/Player1
will bypass the white screen when booting the game up.
Game runs perfectly fine afterwards. No further issues to note.
Deleting or Modifying Settings.sav
You will need to delete or empty the contents of the Settings.sav file (located at /home/deck/.local/share/DustAET/Save Files/Player1) to play the game, otherwise you'll be consistently met with a white screen
Works great, when you get past the lauching troubles
- Had a weird bug with game not launching, because it could not find loadTex.xnb from path: ../Dust An Elysian Tail/Content/gfx/ui/loadTex.xnb
Problem was with Content folder being lowercase.
Solved by renaming folder content to Content and game launched. - As others mentioned, had a bug with game launching into black screen. (because I played it on windows before)
Solved by (while game is running) deleting file: ../.local/share/DustAET/Save Files/Player1/Settings.sav
Then stopping and relauncing the game.
Notes: If you are running steam as flatpak like me, .local relates to flatpak's .local folder. If in doubt, choose open local files option in steam and walk backwards.
Tip: Turn on high quality character portraits in game settings
I tried a few things I found online (delete a certain file in desktop mode or while running the game) but none works. It's too bad it's a game I was really looking for playing on the Deck.
The Linux version initially would not boot in Gaming Mode. Launching it once in Desktop mode fixed the issue for me.
I was able to play at 5w TDP for 6-6.5 hours without any noticeable performance degradation.
Deleted Settings.sav
Been like this since I got my deck. Some have suggested deleting the settings file, but that did nothing. Seems totally unplayble, for the time being at least.
if you've played this game on windows you MUST delete the settings.sav file
If you have played this game on windows you MUST delete settings.sav For whatever reason this game syncs settings files which should not be synced according to Valve's dev documentation. You can follow this thread for more https://steamcommunity.com/app/236090/discussions/0/627456486245565380/
Played through whole story.
Works natively, no tinkering needed. Force native compability in case it's not chosen automatically
Too many issues while playing cause the game to be semi unplayable. It can really negatively affect the a great game
Stuttering in certain combat scenarios, conversations with NPCs can freeze for a couple of seconds
Sometimes the NPC dialogues will cause the game to freeze needing a restart
Hopefully the dev can check the linux port on the Steam Deck ASAP!
Slight issues with story moments and FPS dips could hamper the enjoyment. May need to be looked at by the developer
Sometimes the FPS seems to drop to the teens for a brief moment with a stutter, then it goes back to full 60fps
Issues when talking to NPCs and cutscenes. Game can freeze for a moment during these instances. Also had an issue were after the freeze is gone, it won't let me progress the rest of the conversation with the NPC. I have to go to the pause menu and skip the rest of the cutscene, though there have been moments where I couldn't even do that. I had to fully shut the game off.
I'm still early in my playthrough with the Steam Deck, but if these issues persist then it can hamper the game's enjoyment. Hoping for a fix!
Game will launch natively yet to a black screen
The game will launch natively (won't with any version of Proton), the music for the Microsoft Studios will play then the menu music, the menu will make it's noises as if you were choosing an option, YET there is only a black screen. I don't know if you can choose to play or enter any options since I can't see what I'm choosing. The Steam Overlay icons will appear like normal yet when fading away will leave odd trails/ghosting. I've tried a command I found in another report here as well (FNA_OPENGL_FORCE_ES3=1 %command%) yet it never changed anything in-game.
can not play on Linux native version. no se puede jugar en version nativa e Linux
showing a blur background with some snowflakes on Linux native, unable to load with proton(may need additional workaround). possible issues with MojoShader mostrandon un fondo borroso con nieve en la version nativa de Linux, incapas de cargar con proton(prodria requerir pasos adicionales). Quisas inconvenientes con MojoShaders
