hi pupper68k (nice nick, amiga fan? :))
in case you haven't seen it yet, here is the generic origin crash issue:
https://github.com/ValveSoftware/Proton/issues/3937

I started DA:I with Proton 5.0-9, Origin installed and the game started up the first time and it was working though with constant stutters which become apparent after playing a bit.

I tried removed the prefix that was created and started the game again (prompting the creation of another prefix) and Origin installed and started up again but I think it got confused since it tells me that it doesn't recognize the game and that I should enter a key to activate. (maybe it's confused since I have the game on Origin and Steam separately?)

Mine is crashing upon trying to start a new game, and randomly if I load up an old game. Not sure what's going on.

System Information

GPU: Radeon VII
Driver/LLVM version: Mesa 20.1.1
Kernel version: 5.6.10-arch1-1-fsync
Proton version: 5.09
Running up to date Arch Linux

Attached is the Proton log, although I'm not experienced enough at reading them to be able to figure out what's going on.
DAIProton.log

I managed to 'fix' whatever error I had, which is possibly related to NUMA nodes. I'm running on a TR 2970WX; booting with fewer cores enabled managed to get beyond that point. I'm also able to boot from within a 42 core linux VM (kvm/qemu) using the same install; on said vm, I don't give the VM any NUMA topology to sort through. Oddly this also fixed issues with another game (Hellblade) but that's for another thread.

I could try and emulate the NUMA topology and see if I have the instant crash again. I had originally suspected that it was related to the number of game threads, although if it was just that I'd assume 42 would be as bad as 48. Something NUMA related seems possible.

QEMU/KVM
Distro: Arch Linux
CPU: TR 2970WX
GPU: Radeon VII
Driver/LLVM: Mesa 20.1.4-3
Kernel: 5.7.12
Proton: 5.09

controller doesn't work

#4186

Compatibility Report

Dragon Age Inquisition (appid 1222690)

System Information

• GPU: AMD Radeon RX5600XT
• CPU Ryzen 5 2600X
• Driver: Mesa RADV (both ACO and LLVM tested) 20.3.4 (Origin appears to refuse to load with VK_ICD_FILENAMES set, or at the very least will crash under AMDVLK)
• OS: Arch Linux, kernel 5.11.5
• Complete System Information: specs.txt

Symptoms

Game initially loads correctly. On first run, everything will appear correctly. However, on subsequent runs, when attempting to continue the game, the ground becomes invisible and violent and seemingly random texture flickering across the display will render the game essentially unplayable. Note that game logic appears to continue to function correctly: this issue is entirely graphical. The glitches can be observed in the attached screenshot:

Reinstalling the game or erasing and rebuilding the prefix seemingly have no effect most of the time. Sometimes a reinstall has briefly fixed the issue, seemingly at random.

Hey kisak. I've updated my report to include a link to the system information gist, and am attaching
steam-1222690.log to this post.

Thank you for the quick response.

Hi Kisak.

I can confirm (from quite a bit of experience) that my system does load the RADV/ACO ICD by default if the driver is not otherwise specified. However, I'm never one to shy away from experimentation.

Earlier, I stated that Origin would crash if I used the VK_ICD_FILENAMES mechanism to specify an ICD. This was due to an embarassing oversight on my part: I assumed that merely specifying the ICD for the game's arch would be sufficient. However, while DA:I is a 64-bit game, Origin also invokes DXVK--and Origin is a 32-bit application. After specifying the 32-bit ICD as well, I was able to sucessfully use VK_ICD_FILENAMES to manually select a Vulkan driver to be loaded without renaming the JSON files for each ICD (which is nice, because I don't have to do that every time I launch DA:I now). I attempted to load the radeon ICD to be sure that I had tried RADV/ACO. This lead to the same results as prior: the graphical glitches continued to manifest. However, loading the AMDVLK driver allowed the game to run correctly, and I was able to continue playing after loading from my save.

Thank you for your assistance.

@jjbarr I think I fixed a similar issue with https://gitlab.freedesktop.org/mesa/mesa/-/commit/68197e8c67b6976f2ad5b98a79d4bc64201c5205. Can you confirm?

Hmm... I'm not actually running mesa-git right now, so it might take me a while to do a fresh compilation and test that. FWIW, it certainly seems like a likely candidate.

Every time I try to start the game, Origin boots up and greets me with this:

Note that if I go over to check my library on Origin, DA:I is listed there, with the Steam logo.

It seems that Proton Experimental sort things out just fine, and the game activates and launches.

Hi @kisak-valve,

Would it be possible to tag with retest? I was unable to reproduce the issue reported above (https://github.com/ValveSoftware/Proton/issues/3950#issuecomment-798804192) on a RX 5700 XT (Mesa 20.3.4 and Mesa-Git [e2cdbb25]). In all instances, terrain and geometry was rendering correctly at launch and on susequent save file loads.

@jjbarr Would you be able to provide additional details such as the graphical options set and also if the issues is specific to an area? I reached right pass the prologue, but could not reproduce the issue.

Thanks.

@ZereoX
Resolution Scale: 100
Mesh Quality: Medium
Tessellation Quality: Low
Texture Quality: Fade Touched
Shadow Quality: Medium
Terrain Quality: Medium
Vegetation Quality: Medium
Water Quality: Medium
Post Process Quality: Medium
Ambient Occlusion: SSAO
Effects Quality: Medium
Post-Process AA: Medium
MSAA: Off
Shader Quality: Medium

I've run the game in both fullscreen and windowed, and at 60, 120, and 144Hz.

I am using a 5600 and allegedly the issue was supposed to have been fixed in Git, so maybe that's why. I do not know.

Hi @jjbarr,

Thanks for the information. I was mainly wanting to confirm the issue was resolved by the commit above, but considering I cannot reproduce the issue on Mesa 20.3.4, I'm reticent on calling it fixed.

The commit mentioned above should now be included in the latest stable Mesa 21.0 release. When you do have a chance, confirmation would be much appreciated.

Thank you.

I can no longer confirm for the 5600XT, sadly, because my GPU just bit the dust.

Either from overheating or poor manufacture, I can't say.

Hey @kisak-valve ,

Given the user has now identified that their GPU was / is failing, I'm most confident in saying that the vertex explosion reported above is most likely due to a hardware failure rather than a Mesa / RADV bug, especially given the report of it occurring randomly

I also had the chance to verify the game on an RX 5600 XT myself and can confirmed that the game renders perfectly fine on Mesa stable and master (previously had also confirmed only on a RX 5700 XT). Unless other users have also reported this, or other reports of similar issues with the game, we can most probably remove the AMD RADV / Mesa labels.

Thanks.

RX 5600 XT w/ Mesa-Git git-3c8ac6a129

(@hakzsam cc for vis)

The game takes a while (approximately 30 seconds to launch) assuming that EA Origin does not crash or fails to launch the game.

This was observed several times using Proton 6.3-5.

And the game tends to crash on close.

Ubuntu 21.04
AMD Ryzen 5 3600
nVidia GTX 1080 - Driver 470.57.02

The main issue is Origin itself, the game runs really well, (almost 50 hours recorded on my channel) and only a couple of crashes).

Using Proton-GE 6.15-GE-1 fixes it somewhat.

Maybe we need a separate thread for EA Origin and all it's shenanigans.

Game itself seems to work fine.

Can't get any gamepad to work though. Doesn't register any inputs once you switch from KBM to gamepad in the game options. I've tried a generic one and XB1, both connected via USB. Read about similar reports on /r/wine_gaming.

The game runs fine, it's getting to that point, as for the controller issue, I had to use DS4Windows to get it to recognise my PS4 controller in Windows, so it could just be a limitation of the game itself, and not Proton.

As SWJFO, Rocket League, and all the Dark Souls games all recognise the PS4 controller out of the box.

If I had a XB1 controller, I would test this game on Windows.

The game does not shutdown correctly and sometimes leaves my desktop in a corrupted state, forcing me to kill the process. Apparently, this issue is very common according to ProtonDB reports: https://www.protondb.com/app/1222690

Could you please investigate what might be causing this issue? I do not observe this behaviour with DA:O or DA2 (which also uses Origin).

I can no longer play the game at all. I have tried Proton 6.3-8 and 5.0-10 without success. Multiple recent reports confirm this: https://www.protondb.com/app/1222690

Suddenly having trouble launching the game. My guess is it has something to do with switching to EA Play over origin?

The past week and a half I've been able to launch it, with the EA Play window coming up as just a solid colour box and no other assets. I could at least login blind. But now it seems to not be coming up at all, which aborts the launch entirely.

I've tried this with several different versions and forks and I'm getting the same issue. I've attached my logs specifically from 7.0-4 because that's the version it was most recently working under.

steam-1222690.log

Compatibility Report

• Name of the game with compatibility issues: Dragon Age Inquisition
• Steam AppID of the game: 1222690

System Information

• GPU: NVIDIA GeForce RTX 3050 Laptop GPU
• Driver/LLVM version: nvidia 510.108.03
• Kernel version: 5.19.0-41-generic
• Link to full system information report as Gist:
• Proton version: Proton experimental

I confirm:

• [ ] that I haven't found an existing compatibility report for this game.
• [ ] that I have checked whether there are updates for my system available.

steam-1222690.zip

Symptoms

The game does not start. I briefly see the QA image and then everything stop.

Controller input does not work

Controller option does not work with Steam deck; Only keyboard and mouse work with deck. This would be awesome with deck, if native controller support would work.

If anyone is interested/able to troubleshoot the controller issue further here's a link to the wine bugzilla for DA:I.

Kinda sounds like it's getting somewhere

https://bugs.winehq.org/show_bug.cgi?id=47070

I can confirm Dragon Age Inquisition detects the controller (because the game tell you that if you don't have connected a controller, controls goes to mouse/kb, however, it doesn't), but it's like it's not. Tried with Steam Deck and a DS4 connected to it. Tried in a PC (Ubuntu 23.10) with DS4 connected too. I had the same result. Controller detected, but NOT working.

As @sorin255 says, seems that thread goes to somewhere. Let's do a follow-up with this.

The thread on Wine's Bugzilla seems to have narrowed down the problem enough to come up with a workaround for the controller issue.

Here's the link shared.

https://github.com/cammoore1/proton-wine/releases/tag/Workaround

It's a unique build of proton that should only be used with DA:I (as the creator states).

They go a little bit more in depth with what they think is the issue and that it might simply be caused by wine limitations.

I reinstalled the game today and tried launching it, the EA App installs itself and then proceeds to "preparing game", however the game never opens. Opening the EA App and clicking play shows it as "launching", but then nothing happens. I tried using several different Proton versions and limiting the CPU threads, to no avail. I played this game before in the same hardware, so it must be a software problem.

I had hard time with EA App too, sometimes it took ages, sometimes it failed on save sync - I would overall blame save synchronization implementation if I did had to guess (especially as there is almost zero user feedback about what its currently doing and how long it will do it). I have also a suspicion some background stuff like save sync or EA App updates can close the original instance of the launched EA App which steam can continue from on windows in normal circumstances as new is launched afterwards after few secs/mins but it breaks in that proton virtual environment as it automatically closes or something and it will not continue when the relaunch normally happen (because the whole virtual system is no longer runing?) which can also cascade in another issues like more complications with save syncing and so ... atleast those are my educated guesses from behavior I did noticed frequently ... its pain tu use EA App on steamdeck :/ (to be fair on Windows soemtimes too but its like 2/3 more stable)

Yes, it seems that the problem was not that the game doesn't launch, but that it takes a really long time for it to open, at least in the first run, which gives the impression that it doesn't launch, beforehand I just did not wait long enough.

Looks like yet another EA App update broke the game.

EAApp crashes with current Experimental (2025-12-09) while booting the game (issue not present with Proton 10.0-3/4 (RC) and 9.0-4)

Logs: steam-1222690.tar.gz

Specs:

• OS: Arch
• Kernel: 6.12.61
• GPU: RX 6700 XT (Mesa 25.2.7)
• CPU: Ryzen 7 5700G (8c/16t)
• DE: Plasma 6.5.3 (wayland)

Controller still not working with Proton 9.0 and 10.0 unfortunately (tested with a DS4 and X360)

The game crashes on Proton-Experimental, Proton-GE 27 and 28 (I know it's not from Valve, but contrary to Experimental, it actually has versioning).

On Proton 10.0.3 the game launches, but controller is not detected.

Proton-GE 25 is the only version with working game and controller.

Tested on Steam Deck.

Steam Deck experiencing same or similar issue with Proton Experimental to what was reported a month ago. See attached Proton log.

steam-1222690__20260209-1.tar.gz

System info from the log preface:

Proton: 1769531387 experimental-10.0-20260127
SteamGameId: 1222690
Command: ['link2ea://launchgame/1222690?platform=steam&theme=dai']
Options: {'forcelgadd'}
depot: 3.0.20251216.191774
pressure-vessel: 0.20251210.0 scout
scripts: 0.20251210.0
sniper: 3.0.20251216.191774 sniper 3.0.20251216.191774
Kernel: Linux 6.11.11-valve27-1-neptune-611-g60ef8556a811 #1 SMP PREEMPT_DYNAMIC Thu, 08 Jan 2026 10:09:09 +0000 x86_64

EA Desktop application seems to run initially, getting past initial EA credentials prompt. And it even gets as far as loading the EA Desktop library briefly before crashing. However, DAI never completes and Steam to the library showing green "> Play" button after a few seconds following the EA Desktop library disappearing.

I have attempted similar with:

• Proton Hotfix (no luck)
• DAI Proton 1.0.4 (no luck)
• GE Proton 29 (no luck)
• GE Proton 10-29 (no luck)
• GE Proton 10-25 (no luck)

So far, Proton Experimental has been the only Proton version to successfully progress through the EA Desktop application prompts (except for crashing at the end)

I have been able to replicate the EA Desktop login process by removing /home/deck/.steam/steam/steamapps/compatdata/1222690/ and completing its credential input using Proton Experimental. However, still no luck after clearing the compatdata/1222690 entry.

Happy to provide more info or tests.

Steam installed an update to the game recently, and now I can’t get it to run on the previously working versions either. So, yeah … got worse instead of better.

Can't get it to run either, tried both experimental and latest GE

Hello,

There was a global update of all EA games yesterday (23 Feb 2026), and now none of them start anymore (except Dragon Age Inquisition after much manual tinkering).
Launching with PROTON_LOG=1 reveals that the error is err:steam:run_process Failed to execute L"link2ea://launchgame/1172390?platform=steam&theme=jfo
This affects at least Mass Effect Legendary Edition/Andromeda/1/2/3, Dragon Age Inquisition, Star Wars Jedi Fallen Order/Survivor/Battlefront.
Deleting the corresponding compatdata/<app_id> directories doesn't fix the issue. Verifying the game files only enable the install script to run. Sometimes the EA App installer shows and download something, then the buttons just return to 'Play' after a while, or the EA App installer just flashes and then the game doesn't start. After that, launching the game again just does nothing until and the aforementioned error is shown in the proton log.

I tried to uninstall EA App through protontricks → Run uninstaller → EA App → Modify/Remove (this fails and just remove the app entry in the list), then 'install' → select EAuninstall.exe from the Program Files/Electronic Arts/EA Desktop/13.649.[numbers] → Repair (This just uninstall all version of EA App), and then verify the game files to trigger the install script, run game. It worked for Dragon Age Inquisition that installed the EA App anew and was functionnal, but not for the other games. They just don't seem to be able to install the new EA App.

Regards.

Hello,

It seems that my issue lies within the 13.649.[numbers] update to EA App, as it affects Windows and Mac users alike with multiple symptoms (failure to install, invalid entry point, black screen/not responding) as can be seen in the recent influx of bug reports on the EA technical forums.

https://forums.ea.com/discussions/ea-app-technical-issues-en/new-ea-app-launcher-installation-may-be-corrupt-started-2-19-2026/13213260

Regards.

Forgot to attach logs, mb

steam-1222690.log