Couldn't get the app, let alone the game to run.
Played 180 hours a year ago using DAI-Proton for controller support. Been trying to play the game again the past weeks but no preset work, including GE and default Proton. Couldn't even launch the app after the update. I've cleared caches, uninstalled and installed the game, tweaked launch commands, but nothing worked.
MANGOHUD=1 gamemoderun %command%
dded "user.igoenabled=0" at the end in the "user_[id].ini" file to deactivate the origin overlay. Also deactivated the steam overlay via the game properties in steam itself.
When tabbing out, the game will be set to window mode and will overlay every other window. After tabbing in the game again fullscreen will be set again.
I had a few crahes while I played. Mostly in cutscenes.
There are numerous asset pop-ups, and the lighting sometimes takes a while to render.
Works great, although I heavily recommend modding it
I couldn't get Frosty Mod Manager to work under Wine or Protontricks, but this modified build of it: https://www.nexusmods.com/masseffectandromeda/mods/1190?tab=description works great in Bottles. I heavily recommend modding the game for some QOL features that it sorely needed (faster movement speed, no looting animations, faster war table missions etc). Out of the box it was a fine experience though.
In GE-Proton9-23, they included changes from the custom DAI Proton, which should solve the previous controller support issues.
Also the auto installation of the EA Launcher client can be tricky. Experiment launching it with older Proton versions to trigger its installation, but then revert it back to GE-Proton9-23 to play. ;)
cant switch to keybord and mice
EA app headaches aside, it plays perfectly using the current version of GE-Proton, including gamepad controls.
30 FPS limit in Deck settings
Some occasional mild judder during cutscenes. Mostly seems to occur in the early moments after entering a new area. But it's also consistent across playthroughs (i.e. not caused by shader compilation).
Doesn't exit cleanly; requires force-quit
Even though the game can usually be played offline after the first launch, on Steam Deck it is effectively online-only since there is no way to enable the auto sign-in option on the included EA app, which is required for offline play.
Gamepad controls appear to work perfectly now, without needing to install the custom DAI Proton mentioned in earler reports. Just enable it in the in-game control menu and you're good to go.
The game runs fine, also no problems with the embedded EA launcher
Controlle being detected but not responding in-game: this is no issue for me as I intended on using keyboard and mouse from the beginning.
I installed the game and played it for 50+ hours over multiple days / sessions and I have no issues to report. The embedded EA launcher made no problems, the game started every time, there were zero stability issues and the performance is as good as you expect for a ten year old game on modern hardware. So as long as you don't need / want to use a controller (which would require tinkering) but are comfortable with using mouse & keyboard, you can just do so without changing anything. Install, play, enjoy.
Installs and plays fine - with occasional controller recogognition problem
The audio was VERY soft. Couldn't find a way to solve this.
During cut scenes, there was a lot of flashing, as in going dark and then bright again. This was reduced if I lowered the graphics settings.
This seemed to be down to using the Steam input overlay. Disabling that allowed the controller to be recognised.
The use of the EA launcher truley adds nothing, and on occasion it would not start properly, and hence just hang there. Restarting and retrying usually got things going.
Also as a result of the EA launcher, Steam web sync for savefile is not available. Saves to the EA network 'may' work, but no way of knowing, so annoying.
EA Launcher immediately quits. Switch to Proton 7 allows to install, but the game shows small black box and then closes.
gamemoderun %command% -GameTime.MaxSimFps 60 -GameTime.ForceSimRate 60+
Does not work.
gamemoderun %command% -GameTime.MaxSimFps 60 -GameTime.ForceSimRate 60+
The game consistently froze every 2, 4, 6, 8, 12, or 14 minutes using Wayland. Tabbing out and back into the game made it run again, but I had to switch to X11 to solve this issue permanently.
The game sometimes fails to launch through EA Desktop. It always works on the second attempt, though.
Launched and ran without tinkering needed, picked up Origin save automatically, but no gamepad support without custom proton.
Needed custom Proton
DAI-Proton-1.0.4 seems to be working again. Installed and launched without issue, picked up cloud save from original playthrough on Origin, unable to detect controller even after enabling gamepad in settings (as expected from previous reports about how Xinput is handled.) Unpacked DAI-Proton-1.0.4 to needed folder, selected in compatibility options, relaunched and confirmed ability to use gamepad based config. Played for an hour or so on default settings at mostly 60fps in hub area.
WINEDLLOVERRIDES="winmm=n,b" %command%
Controller wasn't working. I installed the MOD Standalone Linux Controller Fix and Launched with WINEDLLOVERRIDES="winmm=n,b" %command%
I was able to link my EA account. It got my samed game from 2014 on DA2. It ran at 4k and let me increase the TEXT size. The controler worked great with the Mod and Launch Command.
For right now, DAI-Proton-1.0.4 does not work. I was able to install the EA launcher with GE-Proton-9-5 and then load the game. Expectedly, the gamepad did not work. Switching to the DAI bespoke version now crashes to Library every time. Suspect a change to the EA launcher causing the issue and awaiting update from cammoore1.
Standing by in hopes of a fix soon! :D
For native controller support, install DAI Proton and run the game with it: https://github.com/cammoore1/DAI-proton-ge-custom
TP Limit: 13 FPS Limit: 40 fps
Sometimes the EA launcher says it couldn't reach the servers and won't open the game. Rebooting the deck fixes this.
It's mandatory to install DAI Custom Proton in order to activate controller in settings.
Game can reach 60 fps even on high settings, but will have drops to the 40s in intense combat.
After installing DAI Proton from Github, the experience is a 10/10. Game runs great, looks nice and controller layout is very comfortable to use. If you want to install mods, just install DAI Mod Manager as a non-steam game, launch modmanager with proton experimental or GE and activate the mods following a tutorial, the process is the same as on windows.
TDP Limit to 13 and limit FPS to 40
Install DAI Proton to activate controller support
%command% -GameTime.MaxSimFps 60 -GameTime.ForceSimRate 60+
MSAAx4 resulted in thick vertical bars all over the screen in gameplay. There may be hair problems on highlighted characters.
EA Launcher fails to install on default Steam. I installed GE 6.21-GE-2 and used that to do the first run, which allowed the EA Launcher to install. I then left the WINEPREFIX intact and switched to the default launcher (9.0-201) and that was able to start the EA Launcher which then had a confirmation code from my EA Account, and let me proceed into the game.
Used DAI-Proton to get controller to work.
Needed proton-experimental in desktop mode to get past EA window for the first time. Custom proton needed for controller support.
fixed with custom proton version
- install
- force proton-experimental to get past the EA launcher for the first time. You may or may not need to do this one time in desktop mode
- install this custom version of proton-ge to get controller support working: https://github.com/cammoore1/DAI-proton-ge-custom. You need to use the tarball method detailed in README. Use the latest tarball in releases, at the time of writing 1.0.4 worked for me. Note that EA launher sometimes breaks with this proton version, in which case you need to start the game with proton-experimental before switching back to this version.
- close Steam from system tray in desktop mode and use ProtonUp-Qt to enable the custom version of proton-ge for this game. For me this was necessary, because steam did not detect it in the "Force compatibility" settings drop down menu even when I restarted steam.
- change the steam input settings to "Gamepad with mouse trackpads". Edit the layout and set right trackpad click to left mouse click. This is needed because controller support is disabled in the games settings by default.
- start the game, go to settings -> controls -> set controls from Mouse and keyboard to Gamepad.
Doesn't detect any gamepad, but there's a workaround
Use DAI-Proton for controller support. Installation is the same that any custom proton (like GE, since it's a fork). Get it there: https://github.com/cammoore1/DAI-proton-ge-custom/releases/tag/Proton-Workaround-v1.0.2
To enable controller on deck,you need “DAI-Proton-1.0.2”. Here is the link——https://www.youtube.com/watch?app=desktop&v=BSBft0qg6IY
To mod Inquisition on deck,please check this——https://www.reddit.com/r/SteamDeck/comments/196ue3a/how_to_mod_ea_games_frost_with_frosty_mod_manager/?share_id=_uxp4OXTP1v97n0eaLLgs&utm_content=2&utm_medium=ios_app&utm_name=ioscss&utm_source=share&utm_term=1
Hope I can help you.
10 watt TDP limit, Manual GPU Clock 900MHz
Tried to switch in game to controller and it broke the game. Use the community profile for controls. It's not the best, but it works enough to play.
Game runs at 50-60FPS, but cutscenes seem to cap at 30FPS. Did lower in game to low-medium for graphics choices.
I verifyied the game files, reinstalled the game, deleted the proton prefixes, and tried a variety of different proton versions. The game launch exists shortly after starting it in Steam. The EA App doesnt seem to be started neither.
%command% -GameTime.MaxSimFps 60 -GameTime.ForceSimRate 60+
EA App
Since this is an EA game, much of your ability to enjoy the game depends on whether or not the EA App decides to function during the current moon phase. I've had times when it worked just fine, but during my playthrough of Inquisition it gave me plenty of headaches. Half of the time I started the game the EA App didn't work and I'd have to restart. Halfway through my playthrough, the app started malfunctioning again, and I was forced to switch to Proton Experimental to fix the issues with the latest update.
Ultrawide Support
This is one of those games that works fine on Ultrawide screens, except it arbitrarily decides to pillarbox cutscenes and cinematic conversations. Flawless Widescreen has a fix for the game. SteamTinkerLaunch has an option to use Flawless Widescreen, but every time I used it the EA App refused to work. I tried several other options to launch FW alongside the game, but the EA App malfuntioned every tme I tried this. No idea what's going on there.
Cutscenes locked at 30fps
The biggest issue that has nothing to do with Linux is that this game (in 2014) came with cutscenes capped to 30fps. The fix is passing -GameTime.MaxSimFps 60 -GameTime.ForceSimRate 60+ as command line arguments. This caps them at 60fps. This was still a bit awkward since the rest of the game ran at 100fps (my monitors refresh rate), but it's better than nothing and it seems that keeping the game at 60 anyway is better for stability. Unfortunately, the results are mixed, as some cutscenes are smooth, but others stutter heavily and don't manage to reach 60fps at all. This is not a Linux issue.
FPS limit: 50 ; 50hz TDP Limit: play around 8 - 10 Watts GPU Clock Frequency: 900
EA app is problematic at times. But it works. Just keep on trying. Game launches eventually.
It flickers at times. maybe its just my earbuds. cant notice it much during speaker mode.
FPS drops a fragment on High Settings but still playable. Go lower if you prefer stable fps.
VERY IMPORTANT: Please refer to my Reddit Post here for Custom DAI Proton Compatibility:
If you want to play on steam gamepad instead of KB&M Layout. Refer to the link above. It fixes the gamepad issue of DAI on steam deck. Your Welcome and Enjoy!
Just slight lag.
I found a workaround to get native controller support working. Here is a link to a custom version of Glorious Eggroll proton wine: https://github.com/cammoore1/proton-wine/releases/tag/Workaround-v1.0.1 . I do not have the game through Steam so I can't comment exactly how to set it up through there. Hopefully someone can provide instructions if they are able to get it working with the directory structure for the Steam version of the game.
However, for Lutris, you can extract the files from DAI-proton-wine-x86_64.zip to either /home/.local/share/lutris/runners/wine or /home/.var/app/net.lutris.Lutris/data/lutris/runners/wine. After that, you can go to the EA App or Origin or the game itself if already added on Lutris (don't start them yet) and click the arrow next to play -> then click "Configure -> click "Runner Options" -> set Wine Version to DAI-proton-wine-x86_64. After that, you can open the game and a controller should work. Tested and working with both a DS4 controller on an Acer Aspire with Arch Linux and a Steam Deck and it runs smoothly without a custom controller configuration through Steam.
If DAI-proton-wine-x86_64 doesn't show up in Lutris, make sure you extracted the files in the correct directory as well as potentially closing and reopening Lutris as it may have to discover the files.
Created a per-game profile with Frame Limit: 50fps TDP Limit: 8 Watts Manual GPU Clock: 900
Run the first time in desktop mode to get around the EA launch installers.
GAME_DATA_DIR='Z:\mnt\games\SteamLibrary\steamapps\common\Dragon Age Inquisition\ModData\Default' %command%
Cutscenes seem choppy
The game runs fine for me, except for choppy/stuttering cutscenes as some others have mentioned. It's unfortunate but not unplayable. I wanted to add some notes for those interested in playing with mods, though.
The preferred mod manager for this game (and other games on EA's Frostbite engine) is Frosty Mod Manager: https://www.frostytoolsuite.com/downloads.html. You can add this to Steam as a non-Steam game and run it that way. I had to use Proton Experimental to get it working; the default Proton version didn't work for me. I also added launch options to tell it to run out of DAI's prefix (replace /mnt/games/SteamLibrary with the path to your Steam library, which is probably $HOME/.local/share/Steam if you haven't set up a different one):
STEAM_COMPAT_DATA_PATH=/mnt/games/SteamLibrary/steamapps/compatdata/1222690/ %command%
Finally, you may need to download this patch which fixes some Linux-specific issues with Frosty: https://www.nexusmods.com/masseffectandromeda/mods/1190/. At the time of writing, this patch is specifically for Frosty 1.0.6.2, which is the latest version. Future readers should check the description and verify that the version it requires is the version you downloaded. You don't need any of the DLLs or other stuff the description mentions; those are specific to Mass Effect: Andromeda.
Once that's all set up, you can launch Frosty and install mods as normal. You then need to click the Launch button in Frosty, which will install all the mods to the ModData folder in DAI's folder and attempt to launch the game. However, for me, it didn't successfully launch the game, it just opened the EA app. Once that happens, close the EA app and kill all EA-related processes. Then, we can add an environment variable to the game's launch options to tell it to load data from the ModData folder. Again, remember to replace mnt\games\SteamLibrary with the path to your Steam library. Also note the single quotes, which I used because this is a Windows path with backslashes. If you want to use an environment variable like $HOME, you'll need to change those to double-quotes and double up your backslashes.
GAME_DATA_DIR='Z:\mnt\games\SteamLibrary\steamapps\common\Dragon Age Inquisition\ModData\Default' %command%
By following all of these steps, I was able to get the game working with mods. There are other apps out there like FrostyFix and DatapathFix which are supposed to enable Frosty to launch the game correctly, but those didn't work for me.
(Mostly) Working great OOTB
No crashes or performance issues here! However, the EA app will give you a hard time every now and then trying to load the game, and is generally slow and annoying to deal with. Had an issue where the game would not launch, but luckily @BigBadBeef 's advice of nuking the "/steamapps/compatdata/1222690" folder (but keep a copy of your saves and whatnot) got it working again. The issue only happened twice and I personally haven't experienced it again for about a week as of now.
gamemoderun %command%
Sometimes games is out of sync during cutscenes
Animations stuttering, especially during cutscenes.
I added gamemoderun %command% but i don't see any advantages using this. Game is working fine with occasionally frame drops during gameplay and especially during cutscenes. I need to try run game without KDE.
Fully playable on Arc A770
The game is fully playable although sometimes EA launcher is causing problems
If the game doesn't launch anymore or if the EA app starts acting out, this is what you must do to get it going again.
gamemoderun %command%
Some sort of update was pushed out by steam, which means my previous advice won't work anymore. First you need to switch to proton 7.0.6. Then find your steam folder and go to "/steamapps/compatdata/1222690/pfx/drive_c/users/steamuser/Documents/BioWare/Dragon Age Inquisition/". Copy your save folder somewhere else, then go back to "/steamapps/compatdata/1222690" and delete everything inside that folder. Run the game once, this will force it to reinstall all dependancies. After the game has launched close it. Then you go to the "Dragon Age Inquisition" folder again, and delete the save folder and replace with the backup you made before.
I'm afraid its the only way, and you will have to do this once or twice a week, but it does work. On a good note, performance has improved slightly, and your cutscenes won't stutter as badly if you turn off vsync.
Runs faster than on windows, except for the typical Bioware cutscene issues. The EA app is acting out, while its annoying, it can be fixed!
gamemoderun %command%
Alt-Tabbing the game causes all kinds of jankiness. On principle it doesn't work at all unless you have something else open in the background while you play.
Custenes will suffer from occasional terrible performance drops. It is completely random. The same cutscene may be okay the first time, but stutter horribly the second time or vice versa. The cutscene fps fix, meant for windows, cause the game to crash on startup so no luck there.
The game runs faster than on windows, but like all Bioware games on Linux, the cutscene stutter may cause your eyeballs to bleed on occasion.
The EA app is a cancerous abomination that has no business existing even on windows computers. It fails to launch the game properly, and once it does, only a full system restart fixes the problem. If you're a power user, you can back up your save files, and detele the compadata for DAI, forcing steam to reinstall the EA app. That will give you a few days peace to play before it starts up all over again.
Work perfectly
nothing to report, the game work well and I can play for hours without any problems.
see reddit link
8W CPU, 900Mhz GPU, Running stable at 60fps
audio breaks very rarely but only for a few seconds
some minor texture flickering
I own this game on Origin. First downloaded the EA App and installed on Desktop mode but it only worked for a few hours. I then followed a reddit guide for installing origin and setting up the game as shortcuts in steam. Everything working fine now.
I have tried a lot of different controller settings. These worked best for me:
- Right trackpad mouse, left trackpad radial menü with numbers 1-0 (skills, dialog choices )
- Right stick as mouse (but with touch = right mouseclick -> easy camera control)
- Left stick as wqse (works as wasd should)
- ABXY Buttons with important actions (e.g. Jump, Use, Scan environment, etc) and some other actions bound to double press (potion, switch target)
- Grip Buttons as 1-4 for skills mainly
Guide on Reddit: https://www.reddit.com/r/SteamDeck/comments/tx6srv/guide_installing_origin_on_the_steam_deck_the/
EA app fails to log in normally but there's a workaround. Go to desktop mode, open the EA website in the browser, log in there, after you switch back to game mode you should be able to start the game and play it.
The game doesn't recognize the steam deck controller but there's a community mapping for simulating keyboard + mouse, takes a bit of getting used to but works very well after some practice.
Running at 40Hz.
Log in to EA website in desktop mode, then you will automatically log in when game starts through steam
Steam deck controller not detected but there's a workaround mapping
