How exactly is this a DXVK bug? Does this not happen with wined3d?
I'd argue that if this regressed with wine 4.20, it's either a wine bug or wine triggers some XWayland issue. DXVK does not interact with X11 or Wayland directly, only with the win32 windowing APIs; There's literally nothing to "account for".
Also, please post the DXVK logs as requested in the issue template.
Because it does not happen when I uninstall DXVK.
The log files are empty and I don't know why.
The log files are empty and I don't know why.
Unless you the environment variable DXVK_LOG_LEVEL is set to something other than ìnfo, the only reason why it would be empty is because the game hasn't even initialized DXGI yet, which would mean that not a single line of DXVK code has been executed at that point.
In any case, there's not much I can do here without logs or an apitrace, and since DXVK does not interact with Xlib, I don't think it's possible to properly fix this inside DXVK in the first place. Weird that it runs with wined3d though.
Note that Xwayland is known to cause all sorts of problems with wine and dxvk, including poor performance, non-functional Vsync and some weird issues in wine that popped up recently, I can only recommend not to use it.
You might want to check out the following wine patch which works around
a regression on XWayland introduced in wine 4.20: https://source.winehq.org/patches/data/174570
I have absolutely no idea what changed, but now the game actually succeeds to launch. However, mouse input does not work at all; No clicks or hover events are registered. Keyboard input works just fine.
Log files are still empty.
Mouse and keyboard input has nothing to do with DXVK.
It is quite confusing since uninstalling DXVK solves all issues.
Also why is Input Issues listed under Common Issues in the wiki?
DXVK does not interact directly with input APIs at all.
The "common issues" entry is extremely old and IDXGISwapChain has been reimplemented since to mostly match wined3d's behaviour, I don't really see why there would be any differences that would affect input handling.
I've updated to WINE 5.0-rc1 and DXVK 1.5, and now it's back to not launching at all and throwing an X error. I tried with WINE 5.0-rc1 only before I installed DXVK 1.5 after uninstalling 1.4.6, and it works perfectly other than the performance hit.
Also there's something that I forgot to mention in the first report: WINE stops working completely after the failed attempt of launching EVE Online, even when used to run software that is not fullscreen and does not even have any 3D graphics. Even winecfg fails to run. That is until the session is restarted.
WINE stops working completely after the failed attempt of launching EVE Online, even when used to run software that is not fullscreen and does not even have any 3D graphics. Even
winecfgfails to run. That is until the session is restarted.
I think you can just kill the xwayland process. I don't have the same problem as you but the Wayland experience is pretty bad overall.
One thing I was wondering is, would a native Linux build allow to run natively on Wayland with the appropriate WSI? Is this even how this works?
I mentioned before that when it succeds to launch, mouse input does not work at all.
Now I have discovered that mouse input actually works, however, the actual cursor is stuck at the top left corner, even though the visible cursor moves. When I move the game between GNOME workspaces, the actual cursor is freed for a fraction of a second. I was able to log in that way, then discover this when I tried to click anywhere and it always clicked a button in the top left corner.
seems like this was fixed at some point either in wine or in dxvk. it is working now.
DXVK_LOG_LEVELx1 2019-12DXVK_HUD=fps,gpuloadx1 2019-12WINEESYNC=1x1 2019-12
When launching EVE Online under Wayland, it fails to make a fullscreen window and throws an X Error.
Here's the full terminal log:
The most important part of this is the last part of the X Error, since everything else also shows up under X11 and the game still launches and works perfectly.
The game used to work fine under Wayland with WINE 4.19 and DVXK 1.4.4, but since WINE 4.20
this has been happening. I assume they changed something in WINE that was not accounted for in DXVK.
Software information
EVE Online, 64-bit, DX11
System information