Dragon Age: Inquisition (1222690)

[pupper68k]

Compatibility Report

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

System Information

• GPU: R9 390
• Driver/LLVM version: Mesa 20.0.7
• Kernel version: 5.6.0-2-amd64
• Proton version: 5 Running up to date Debian

I confirm:

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

(Log is big, you can download it from my Nextcloud here) https://cloud.aidanis.online/s/nZ7MbemTJXq6wfP

Symptoms

I click on "Play" and the following occurs

• Origin opens momentarily and closes
• Origin opens momentarily again with the message "Origin cannot install games in this folder"
• Origin closes quickly
• Nothing else happens, however the steam client believes that the game process is still running
• Last few lines of log file linked repeat infinitely

Reproduction

• install game
• open game

[frostworx]

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

[kisak-valve]

Hello @pupper68k, friendly side note that Proton logs compress well. You can throw it in an archive and see if Github is happy with the file size.

[StrongholdVerx]

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?)

[astatide]

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

[astatide]

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

[fsyy]

controller doesn't work

#4186

[jjbarr]

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.

[kisak-valve]

Hello @jjbarr, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. The specific detail I'd like to confirm is which video driver the game is using.

[jjbarr]

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.

[kisak-valve]

Thanks, looking at your system information, we can see that you have three vulkan drivers installed for your system, and it's almost certainly not using the driver you expected. Unfortunately, skimming through the Proton log, I can't see which driver the game picked.

So, if you're willing, I'd like you to do some experimentation.

1. Go to /usr/share/vulkan/icd.d/ in a terminal.
2. Rename all six of the icds in the folder so that they end with .json.disabled instead of .json with something similar to sudo mv radeon_icd.x86_64.json radeon_icd.x86_64.json.disabled.
3. At this point Proton should not work because it can't find a usable vulkan driver. Rename one set at a time back to the original file names ending in .json Set 1: mesa/radv - radeon_icd.i686.json and radeon_icd.x86_64.json Set 2: AMDVLK - amd_icd32.json and amd_icd64.json Set 3: AMDGPU-PRO - amd_pro_icd32.json and amd_pro_icd64.json
4. Test the game's behavior.
5. Repeat from Step 2 and pick another driver set.

When you're done, you can rename all the icds so that they end with .json to be back to where you started. Blind guess based on the system information that the game ended up using AMDVLK when you expected it to be using a different vulkan driver.

[jjbarr]

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.

[hakzsam]

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

[jjbarr]

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.

[ptkato]

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.

[ptkato]

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

[ZereoX]

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.

[jjbarr]

@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.

[ZereoX]

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.

[kisak-valve]

Tracking note: Mesa and RADV labels dropped pending confirmation that a current driver release is still misrendering.

[jjbarr]

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.

[ZereoX]

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)

[intelligentgaming]

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.

[DanMan]

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.

[intelligentgaming]

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.

[Alex-Bujorianu]

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).

[romulasry]

Sound doesn't work for me on Proton Experimental as of today.

[kisak-valve]

Hello @romulasry, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, what's the most recent Proton version you know wasn't affected by the issue you're seeing?

[romulasry]

Seem to be working now after a restart.

[Alex-Bujorianu]

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

[sorin255]

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