Dragon Age Origins Problems

[Reverse Module]

Hello, I'm on Manjaro LXQT and I just installed Dragon Age origins which is rated Platinum on ProtonDB. The game won't even start with any other Proton than Proton 4.11-13 and even then I have massive stuttering and no audio at all. am I doing something wrong? Here's my system info:

 System:
  Host: qushy-systemproductname Kernel: 5.6.7-1-MANJARO x86_64 bits: 64 
  compiler: gcc v: 9.3.0 Desktop: LXQt 0.14.1 Distro: Manjaro Linux 
Machine:
  Type: Desktop Mobo: ASUSTeK model: TUF GAMING X570-PLUS (WI-FI) 
  v: Rev X.0x serial: <filter> UEFI: American Megatrends v: 1005 
  date: 08/01/2019 
CPU:
  Topology: 12-Core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 
  L2 cache: 6144 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 192091 
  Speed: 3998 MHz min/max: 2200/4000 MHz Core speeds (MHz): 1: 3997 2: 4003 
  3: 3989 4: 3986 5: 3998 6: 4001 7: 3995 8: 4000 9: 4000 10: 3999 11: 4000 
  12: 3993 13: 4000 14: 3997 15: 4008 16: 3993 17: 4005 18: 3999 19: 3996 
  20: 3999 21: 3993 22: 3999 23: 3990 24: 3994 
Graphics:
  Device-1: AMD Baffin [Radeon RX 460/560D / Pro 
  450/455/460/555/555X/560/560X] 
  vendor: Sapphire Limited driver: amdgpu v: kernel bus ID: 08:00.0 
  Display: x11 server: X.org 1.20.8 driver: amdgpu,ati unloaded: modesetting 
  resolution: <xdpyinfo missing> 
  OpenGL: renderer: Radeon RX 560 Series (POLARIS11 DRM 3.36.0 
  5.6.7-1-MANJARO LLVM 10.0.0) 
  v: 4.6 Mesa 20.0.5 direct render: Yes 
Audio:
  Device-1: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] 
  vendor: Sapphire Limited driver: snd_hda_intel v: kernel bus ID: 08:00.1 
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus ID: 0a:00.4 
  Device-3: Logitech Webcam C170 type: USB driver: snd-usb-audio,uvcvideo 
  bus ID: 5-2:3 
  Sound Server: ALSA v: k5.6.7-1-MANJARO 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0 
  IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 1.24 TiB used: 44.90 GiB (3.5%) 
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB 
  size: 931.51 GiB 
  ID-2: /dev/sda vendor: SanDisk model: SDSSDA240G size: 223.57 GiB 
  ID-3: /dev/sdb vendor: Toshiba model: TL100 size: 111.79 GiB 
Partition:
  ID-1: / size: 907.53 GiB used: 44.61 GiB (4.9%) fs: ext4 
  dev: /dev/nvme0n1p3 
  ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap 
  dev: /dev/nvme0n1p4 
Sensors:
  System Temperatures: cpu: 44.9 C mobo: N/A gpu: amdgpu temp: 46 C 
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 953 
Info:
  Processes: 397 Uptime: 29m Memory: 31.33 GiB used: 1.98 GiB (6.3%) 
  Init: systemd Compilers: gcc: 9.3.0 Shell: zsh v: 5.8 inxi: 3.0.37  

[Aoi Blue]

Could you give your system info as displayed by the steam help menu?

I'm not sure, but Dragon Age Origins may require 32bit mode support.
I need to see if you have the prerequesites 32bit mode support setup.

Finally, you should probably set the game to run under Steam Runtime. (In the game preferences under force running under a specific compatability tool.) This not only addresses issues with games that are incompatible with Majaro/Arch Steam Native Runtime, it also fixes issues with many missing extended libraries. It's a major win for everyone, and made life easier.

Future developers will be able to specify this option directly in their games, but I doubt the feature will be backported unless it fixes a major bug that affects Ubuntu, Debian, Red Hat, and/or Fedora users, as those are the usual "Officially supported" distros that hold the majority of the market share. It's not a matter of if I agree with it. It's a matter of how it is.

[thetargos]

It does. Origins runs really well on my systems. Alas, my suspicions would be about driver compatibility with that particular version of both mesa and Proton. The game is DX9 so fairly good compatibility with OpenGL backend. I have little experience with Mesa and Proton, though, as I mainly run nVidia until my next upgrade (hopefully soon).

Having said that, you may have to fiddle with the WINED3D variable to alternate between D9VK and the wine OpenGL backend for D3D9, or maybe even ESYNC (given the sheer number of threads of your CPU).

Either way hope you get it sorted out, the game does run rather smooth on modest (by today's standards) system @high settings and high res (though assets can be a bit blurred).

[Reverse Module]

Yeah I actually installed Manjaro XFCE cause LXQT couldn't scale thing on my HiDPI screen without much strife so I'm gonna redownload and try again. :D

[Marlock]

display 1 has no identifiable screen resolution, so maybe proton isn't fond of guessing and fails?

you mentioned setting it up for HiDPI so I'm guessing it's 4k or ultrawide or something more than classic 1920x1080p FullHD... this paired with an AMD RX560 may be a big cause of sluggishness since that's a cheap and power-conscious GPU but not a strong one (mine is an AMD RX580 and AFAIK it is considered just a mid-range performance by today's standards)... is it working well for other proton games?

also a Ryzen 3xxx means a couple inicial hiccups with linux support that AFAIK are already resolved with default boot parameters on kernel 5.6.x but may be better to doublecheck that

and finally, you should make sure vulkan support is properly installed... try installing and running vulkaninfo in 64-bits and in 32-bits to doublecheck that... (not sure about package names on Manjaro and if it's supposed to come preinstalled)

aside from that, running the game over wined3d instead of dxvk dx9 support is a good test


no NTFS partition in the way at least :)

[ripper81]

Is the mesa vulkan driver (RADV) installed ?

[Reverse Module]

OK, just tested it in XFCE, works like a charm no problems at all even in 4K (altho that was a bit too much for my GPU). I am playing 1080p and everything just worked without me having to do anything. :D

[thetargos]

With multiple monitors you have to set the default display, either in xorg.conf or through RandR, if using a WM instead of a DM. Most DMs nowadays integrate well RandR to configure the screen and multiple screens. It may boil down to that with LXQT not setting everything up through RandR.