search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.72k stars 1.07k forks source link

Dragon Age: Inquisition (1222690) #3950

Open pupper68k opened 4 years ago

pupper68k commented 4 years ago

Compatibility Report

System Information

I confirm:

(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

Reproduction

frostworx commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 3 years ago

controller doesn't work

4186

jjbarr commented 3 years ago

Compatibility Report

Dragon Age Inquisition (appid 1222690)

System Information

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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

jjbarr commented 3 years ago

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 commented 3 years ago

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

image

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

ptkato commented 3 years ago

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

ZereoX commented 3 years ago

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 commented 3 years ago

@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 commented 3 years ago

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 commented 3 years ago

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

jjbarr commented 3 years ago

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 commented 3 years ago

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
DAI_RX_5600XT

(@hakzsam cc for vis)

intelligentgaming commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 2 years ago

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

kisak-valve commented 2 years ago

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 commented 2 years ago

Seem to be working now after a restart.

Alex-Bujorianu commented 2 years ago

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 commented 2 years ago

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

kisak-valve commented 1 year ago

Dragon Age Inquisition (1222690)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6418. @maniman303 posted on 2022-12-29T17:46:02:

Compatibility Report

System Information

I confirm:

Symptoms

Controller doesn't work, and to be more specific - it's recognized by the game (if game doesn't recognize any controller it shows proper message on start), but it's not registering any input.

I've made small xinput wrapper dll for myself that logs calls to xinput and when the game on windows calls them all the time when it's running, on Linux it stops after a few seconds after launch.

Reproduction

Have controller connected to PC and enabled in Steam. Launch game. Go to options -> controls, choose controller instead of K+M. Go back to main settings page to approve changes. Now the game is in a "gamepad" mode, but it doesn't detect any gamepad input.

fbenedett commented 1 year ago

Compatibility Report

System Information

I confirm:

steam-1222690.zip

Symptoms

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

mikhaelcool7 commented 1 year ago

Controller input does not work

Ulfasti commented 1 year ago

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.

sorin255 commented 1 year ago

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

Noctis-Bennington commented 1 year ago

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.

sorin255 commented 10 months ago

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.

ptkato commented 5 months ago

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.

astromediaonly commented 5 months ago

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)

ptkato commented 5 months ago

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.