protonscr

ME:Andromeda doesnt start with new Dxgi

dxvkclosed can't reproduce
doitsujin/dxvk#1140 · opened 2019-07-21 by t14462 · updated 2019-12-08 · 8 comments · github
Tt14462 2019-07-21 github

Software information

Mass Effect Andromeda launching only with wine's Dxgi

System information

  • GPU: RX560
  • Driver: Mesa RADV/ACO from AUR
  • Wine version: wine-4.12.1.r18.g5d7a86d0 ( TkG Staging Esync )
  • DXVK version: 1.3.1

Log files

MassEffectAndromeda_d3d11.log
MassEffectAndromeda_dxgi.log
mealog.txt

Ddoitsujin maintainer 2019-07-21 github

Does it work if you disable nvapi in winecfg?

The game has always worked fine for me in the past even with DXVK's DXGI.

Tt14462 2019-07-21 github

nvapi64 disabled - nothing changes.

Ddoitsujin maintainer 2019-07-21 github

Just managed to test it again and the game works fine for me (ignoring input issues, but dxvk has nothing to do with those).

Tt14462 2019-07-22 github

It is on AMD RX, on Mesa ACO from AUR?

Hmm... Maybe it is Wine-TkG problem :-/
Or patch in TkG-dxvk-tools fails somewhere

Ggnusuari0 2019-08-31 github

Hi, I can reproduce this. DXVK 1.3.2.
DXVK's DXGI doesn't start. I have to use Wine's DXGI.
Wine staging 4.14 from Wine's repos https://wiki.winehq.org/Ubuntu.
MassEffectAndromeda_dxgi.log
MassEffectAndromeda_d3d11.log
mea-console-output.txt

dxvk.conf.txt

Captura de pantalla de 2019-08-31 01-59-37

Edit: Just a comment. With Proton 4.2, provided by Steam, the game works. But if I change in Lutris to Wine 4.14 staging, the previous error shows up. Both using DLL override dxgi=native.

Ggreencopper 2019-11-18 github

I can confirm this. Running on Arch Linux 5.3.11-arch1-1 with wine-4.20 (Staging), Nvidia 440.31 and DXVK 1.4.4. I haven't played the game since I had the strange lightning issue, so today I wanted to see if anything had changed since the upgrades both to Nvidia and DXVK.

Screenshot_2019-11-18_17-49-05

MassEffectAndromeda_d3d11.log
MassEffectAndromeda_dxgi.log

When I run it with dxgi=native, then it works.

Ddoitsujin maintainer 2019-11-19 github

@greencopper can you test this commit: 9e69a610cb1fe5c7bbeef304627dadc9566f2160

I'm still unable to reproduce the problem, but integer overflows might be the issue here.

Ggreencopper 2019-12-07 github

I'm sorry for my very late reply. I have just upgraded to 1.4.6 this evening and the problem is gone! Thank you very much for your amazing work!

Proton versions