Dxvk: EVE Online issues

[sdack]

Issues with known fixes

• For those who are experiencing hangs with EVE Online in combination with the Nvidia driver please try disabling Allow Flipping in the Nvidia settings panel under the _OpenGL Settings_. See also here: https://github.com/doitsujin/dxvk/issues/341
• The game's VSync settings of _Interval Two_ to _Four_ are known to produce 60fps instead of the expected 30fps, 20fps and 15fps. This issue has been fixed with https://github.com/doitsujin/dxvk/commit/e615fc19a91891828919e0029d73cec77553636a .
• Video capture may produce a static image when the game is rendered under DXVK (possibly a Vulkan/Nvidia issue). For it to work does one need to enable a composition pipeline in the Nvidia driver settings (see _X Server Display Configuration -> Advanced_).
• Problems in combination with the Linux launcher can be worked around by using the game's standard Windows Launcher under WINE.

Known Graphical Issues without fixes

• Flickering of the 1st person HUD.
• Flickering of the speed meter and the outer ring around the game's HUD.
• Flickering of the background logo during character creation.
  https://www.dropbox.com/s/gecehtd0b0uz3no/vulkan.mkv
• Some background triangles don't render. https://github.com/doitsujin/dxvk/issues/402#issuecomment-394081891

Other Issues

• Game minimizes randomly. (Xfce4)
• Game becomes lowest window when in fullscreen mode. (Xfce4)
• Hanging clients after the Linux launcher exits. (KDE)
• High CPU usage of the Linux launcher. (KDE)

System Information

WINE 3.9, Nvidia 396.24.02 (GTX960), DXVK 0.53, Xfce4, Debian 10 "Buster"
WINE 3.9, Nvidia 396.24 (GTX1070), DXVK 0.53, KDE, Ubuntu 18.10 (dev branch), kernel 4.17rc7

d3d11.log
dxgi.log

@doitsujin I have no idea on how to create an apitrace at the moment. The .dll files provided by varis1 only produce crashes and the game itself is started by a launcher application, which cannot be worked around.

[varris1]

I am not Doitsujin, but you can use this for easy tracing:
https://www.dropbox.com/sh/o769ius47wpu3pw/AABYFKQFFNsCsosXhl7_HReDa?dl=0
just put the correct dlls into the game folder and apitrace will generate a .trace file.

If you fear for your account, you can create a throwaway one. Afaik nobody has been banned for using reshade yet, so I don't think apitrace will be a problem.

[sdack]

@varris1 Thanks, I'll do this, but I first have to wait for CCP to respond to my support request. This is a matter of courtesy.

I've also now seen the patch for the VSync issues and have tested it. Works perfectly. Thank you!

[3vi1]

@sdack: Which desktop are you using on your Debian setup? Is it Gnome/Wayland? I'm just curious because I'm using KDE/Xorg on the Ubuntu 18.10 dailies and I haven't see the minimizing or bottom-most problem you've seen with the game window.

I do see the other issues you've reported (hud flicker, etc.). I'm testing now with your suggestion to disable OpenGL flipping to see if it stops the random hangs.

[sdack]

@3vi1 Says up there in the description. Can you spot it?

[3vi1]

Ah, Xfce4. Must have skipped over it from "x burnout". :) That's weird, I would not have expected such odd behavior there.

My test enviroment: WINE 3.9, Nvidia 396.24 (GTX1070 Max-Q), DXVK 0.53, KDE Plasma, Ubuntu 18.10 Cosmic Cuttlefish (dev branch), kernel 4.17rc7

[sdack]

@3vi1 The game is playable with glitches and odd window behavior. This issues thread is here to collect all these. Other games have more pressing issues. Don't expect things to move fast and don't worry about it.

[3vi1]

Tested for several hours and found a couple of additional issues: The launcher is suddenly eating a lot of CPU, and closing the launcher causes any game clients you have running to hang.

I played two characters in 1280x1080 windows on my external monitor for 2+ hours with no issues, but I eventually noticed that the launcher had started consuming a lot of CPU at some point. So, I closed the launcher. Within 10 seconds, both client windows froze. This seems recreatable 100%

I killed the hung clients, restarted the launcher, launched both clients again and waited a few minutes. Everything was going fine, until I then I re-tested closing just the launcher window (which seems to consistently peg a CPU shortly after you start playing) again. Within a few seconds, both game client windows froze. It's as if the client windows are dependent on something allocated/initialized by the launcher.

I'll have to do some more tests to make sure this is solely due to dxvk, as I've not played EVE with Wine 3.9 before. But, this definitely wasn't a problem when using older versions of Wine and DX9 mode.

UPDATE: Tried _without_ DXVK this morning:

• Evelauncher definitely uses way less CPU without dxvk. I didn't see it start maxing a CPU like I did with dxvk.
• The clients do still hang if you close the launcher, when using dx11 mode with plain wine 3.9, so that one looks like it's _not_ on dxvk. The problem goes away if you switch to dx9 mode.
• They may have fixed something in yesterday's EVE expansion - chat window transparency now works for me in dx11 mode without dxvk, but the frame rate is wayyyyy lower than when using dxvk (~40 vs. 200+).

[sdack]

I've capture the problem in a video. This is what it should look like (DX11 over OpenGL):
https://www.dropbox.com/s/ab0deov02nhfui3/orig.mkv
This is what happens under DXVK:
https://www.dropbox.com/s/gecehtd0b0uz3no/vulkan.mkv

Here is a screenshot however of how the HUD in the center is getting damaged and starts to flicker:
https://www.dropbox.com/s/xhoi2sjuvdg6mxx/Screenshot_2018-05-30_13-31-41.png

I'll see if I can create another account and then run an API trace. CCP support only gave a "pick the bones out of this"-type of response and my question was likely just above their heads. Going to respect that, not doing it with my accounts, but will have to make one for it.

[sdack]

@3vi1 I've seen the "Abyss" update, but I have no issues with the launcher, not with the CPU or with any hanging clients. I'm using the standard Windows Launcher under WINE that comes with the game. Which launcher are you using?

[sdack]

@varris1: Thanks for the .dlls, but I only get a crashing game and no trace with them.

[3vi1]

@sdack: I'm using the native Linux launcher: https://binaries.eveonline.com/evelauncher-1104891.tar.gz

[sdack]

@3vi1 I thought so. Just remember it doesn't use WINE nor DXVK. Only the game client does. So any issues with the Linux launcher happen outside of WINE and DXVK. I've listed the issues nevertheless, but suggest to use the game's standard Windows Launcher under WINE.

On a different note, video capture now works. One needs to enable a composition pipeline in the Nvidia settings for ffmpeg to produce a proper video.

https://www.dropbox.com/s/gecehtd0b0uz3no/vulkan.mkv

[3vi1]

Additional bug: Some background triangles don't render. For instance, the image on the login screen when running in windowed mode consistently isn't drawing (or is drawing all-black) the bottom right triangle. .

I can see the same effect in-game, also consistently but only on one of my accounts, in the background of the neocom panel. The specific size of the panel/window may be a factor, as I see neither of these issues on other accounts running in different sized windows.

(Tested with master, as of yesterday [0.53+12commits])

[sdack]

@3vi1 I don't have this issue nor have I ever seen it before (I'm on the same patch level as you are). When you can see it with one account, but not the other then something else might be wrong.

Are you saying it was introduced recently? If so, can you bisect the commit that causes it?

Also, have you tried using 296.24.02 yet?

[3vi1]

Also, have you tried using 296.24.02 yet?

I've updated to 396.24.02, and I still see the issue. In fact, after resizing the windows a bit, I see it on both accounts. What's more, I see it on both triangles of the background (entire background is black) now. I don't see it on other accounts that I launch in fullscreen or large fixed-window sizes. I also don't see it if I launch the clients in DX9 mode.

Also, I don't find using the windows launcher to be a suitable workaround to the native launcher issues. I've been testing it since last weekend and the windows launcher a) has to be run WinXP mode due to Wine's perpetual IO completion ports issues and the way Qt5WebEngine behaves in Vista and later mode. b) it FREQUENTLY crashes or hangs - taking all open game clients with it (and logging nothing relevant to the console). And, like the native launcher, it has none of these problems if you launch the clients in DX9 mode.

[3vi1]

I noticed something about the missing triangle on the start screen today. That only seems to happen when I open the window on my 2560x1080 external screen. If I open the same client on my 1920x1080 laptop screen, both triangles render fine. Odd. I'm not sure why the screen/aspect would even matter for a client starting in windowed mode.

[chrisharper]

I can confirm the launcher resource usage(CPU+MEM) increase occurs when using the linux launcher and a game client is launched. I believe this is due to game client -> launcher communication with regards to logging .

If you check the launcher logs (~/.local/share/CCP/EVE/Launcher) you will note many of the following messages

D3D11DeviceContainer::QueryInterface: Unknown interface query

If however you set

DXVK_LOG_LEVEL=none

this turns off the logging and resolves the increasing resource usage.

[ForlornWongraven]

Can this set by default?

DXVK_LOG_LEVEL=none

[chrisharper]

Create a bash script that sets it and also runs the launcher (evelauncher/evelauncher.sh).

This will also allow you to set other config options in one location without making them global configs or getting removed on updates

[3vi1]

I can confirm chrisharper's log level solution fixes the biggest problems: 1) It seems to stop the game from crashing if using the Windows launcher under wine and leaving it open with multiple clients running. and 2) It stops the launcher from uploading tons of spam to CCP: I noticed it was uploading 20kb/s+ the entire time the game was running if I left the launcher open before, whereas after setting the log variable it seems to have dropped off to practically nothing.

With that in place, the only problems under DXVK are the very few minor graphical glitches pointed out earlier in this thread.

[ForlornWongraven]

I can confirm this working well even with 0.54 (as I am stuck with Mesa > 18.0.5).

[3vi1]

As of the 394.54.05 Nvidia drivers (and most probably since the .02 driver), all the items referenced in the OP's "Known Graphical Issues without fixes" section appear to be resolved! As long as you run the game with DXVK_LOG_LEVEL=none, the game appears to be working 100% here.