protonscr

The Vanishing of Ethan Carter Redux

dxvkclosed amd radv
doitsujin/dxvk#732 · opened 2018-10-24 by LeJimster · updated 2018-11-11 · 9 comments · github
LLeJimster 2018-10-24 github

Game crashes when it reaches about 90% on initial loading bar. Seems like this title works fine on nvidia proprietary drivers. This is an Unreal Engine 4 game.

vanishingofethancarterredux_dxvk_crash

Software information

The Vanishing of Ethan Carter Redux

System information

  • GPU: RX Vega 56
  • Driver: Mesa 18.3.0-devel (git-ff281e6204) (with Transform Feedback patches)
  • Wine version: Proton 3.16-3
  • DXVK version: 0.90-12-ac0f8d6

Apitrace file(s)

EthanCarter-Win64-Shipping.trace

Log files

Ddoitsujin maintainer 2018-10-25 github

Does replaying the trace crash for you? It works fine on my end using latest mesa-git and LLVM 8.

Also, does it work with DXVK 0.90?

Eexolyte 2018-10-25 github

I didn't do any extensive testing of the game itself, but the crash at startup went away for me when using a dxvk.conf file in steamapps/common/The Vanishing of Ethan Carter Redux/EthanCarter/Binaries/Win64 with the option dxgi.customVendorId = 10DE

LLeJimster 2018-10-25 github

@doitsujin I created the original trace in Windows10 and I was struggling to get a functioning trace in wine. I've managed to get something now, although I don't know if it's useful. Same thing happens on all DXVK versions I've tested including 0.90 release and I'm using latest LLVM-svn.

wine trace

@exolyte yes that option works and the game launches now..

Ddoitsujin maintainer 2018-10-25 github

UE4 being annoying again. Since there is no indication that it crashes inside or because of my D3D code, I added a workaround to spoof an Nvidia card for this game.

Not an ideal solution, but the only one that comes to mind.

SSkiski 2018-11-11 github

I've got an nvidia card (GTX960) and I've got this problem with Proton 3.16-4 and not with 3.7-8.
In the latest proton changelog, it says:

For Direct3D games (both DXVK and wined3d), Nvidia cards are now reported as if they are actually AMD cards. This prevents games from trying to load the Windows-only nvapi library and crashing or giving very bad performance.

I think it breaks your patch and makes this game unplayable once again.

If I add the dxvk file with the correct Vendor Id and DeviceId, it works again.

LLeJimster 2018-11-11 github

@Skiski I don't think 3.16-4 has the latest dxvk, but I was wondering if this was going to be an issue.

SSkiski 2018-11-11 github

I followed the link in the proton thread about the game but didn't see it wasn't on proton github. Maybe it's not exactly a dxvk issue. But at least, I found a way to solve it. I'm not sure if it's something you can solve for everyone.

Maybe it would be interesting to have some fallback dxvk files that we can easily select (in the command line for launching the game) depending on the needs of the game.

Eexolyte 2018-11-11 github

Dxvk game-specific settings can override that proton behavior, so once 422cf71 hits proton, it should just work for everyone.

SSkiski 2018-11-11 github

I tried adding only dxgi.customVendorId = 10DE but it did not worked. I needed also the DeviceId for it to work. I don't know if it's because I've got an nvidia card. And I don't know if the piece of code you've shown is only used in case of an AMD card.

Proton versions

Upstream links