protonscr

[d3d9] E.Y.E: Divine Cybermancy graphical artifact when aiming

dxvkclosed
doitsujin/dxvk#1392 · opened 2020-02-01 by TacoDeBoss · updated 2020-02-04 · 5 comments · github
TTacoDeBoss 2020-02-01 github

20200131171054_1

Software information

E.Y.E: Divine Cybermancy (appid 91700), issue occurs on all settings.

System information

  • GPU: Radeon RX 5700XT
  • Driver: mesa-git, latest as of writing
  • Wine version: Proton 4.11-12
  • DXVK version: 1.5.3

Apitrace file(s)

This game appears to be untraceable from my efforts, resulting in a 124 byte trace and instant game crash on launch. If anyone has some suggestions, please do let me know.

Log files

This issue also used to occur on my GTX 1070 with the Nvidia proprietary driver, and the bug has been present since D9VK has existed. It is not present on wined3d.

Ddoitsujin maintainer 2020-02-01 github

This game appears to be untraceable from my efforts, resulting in a 124 byte trace and instant game crash on launch.

That's not particularly helpful and means that we won't be able to do anything until someone manages to get this to work. Are you trying to launch it via apitrace.exe or did you copy the d3d9.dll from apitrace? Were you using wined3d or dxvk when running apitrace?

TTacoDeBoss 2020-02-01 github

That's not particularly helpful and means that we won't be able to do anything until someone manages to get this to work. Are you trying to launch it via apitrace.exe or did you copy the d3d9.dll from apitrace? Were you using wined3d or dxvk when running apitrace?

I copied the d3d9.dll file to the game directory and used wined3d to run the game. I tried with no success to generate a trace on Windows, because (on Windows) the game ignores any d3d9.dll in the game directory, be it apitrace or DXVK's.

DDustyCrumpet 2020-02-01 github

d3d9.dll needs to be placed in the steamapps/common/EYE/bin folder.
I can reproduce this issue with DXVK 1.5.3 on both Linux and Windows 10.

Windows trace

Ddoitsujin maintainer 2020-02-01 github

@DustyCrumpet thanks; annoyingly I cannot reproduce the problem since the trace renders fine. What's your GPU?

Edit: Looks like there's a broken memory barrier somewhere that needs investigation, but that shouldn't be causing these rendering issues.

DDustyCrumpet 2020-02-01 github

I'm using an AMD Vega 56. Replaying the Windows trace looks correct here too, so here's a trace recorded with DXVK, hopefully it's useful.

DXVK trace

Proton versions

DLLs