Unified DXVK/VKD3D lag timebomb in most games if compiled from git #4436
Comments
|
We have found out that, when this triggers, it only happens when moving the mouse, I'll be posting a video soon. |
|
DXVK does not interact with mouse input in any way, I strongly doubt it's even remotely possible that this is our bug. Also haven't seen anything like this on my machine even in extended play sessions. As for Unreal Engine titles, I ran Hellblade and Days Gone for ~an hour not too long ago to test some unrelated changes. |
I understand that they don't interact with mouse input, but when I run a game that natively uses Vulkan (ie. Quake 2 Remastered, Saints Row) they're not affected by this problem. Switching to any of your releases paired with a vkd3d release completely fixes this mouse problem. I'm not any more expert than you, but the only thing dxvk and vkd3d have in common is dxgi. I don't know if I'm being helpful but I can post a video on YouTube or logs. |
|
Well what I'm saying is that this functionally doesn't make any sense and I can't reproduce it. First step would probably be to provide detailed info about your build environment, including compiler version, MinGW version if applicable, and the exact command lines you're using to build the whole thing. Another question would be what kind of environment you're running on as well, any sort of input issue points more towards wine/compositor issues than us. |
I'm using fully updated Arch Linux, MinGW 13.1.0-1. I tried with X11, X11 + gamescope, Wayland and Wayland + gamescope. Same problem happens after roughly 25 to 40 minutes of gameplay. There's an intermittent heavy stutter that runs at its own pace, but only when playing with keyboard and mouse apparently, and it gets worse if you move your mouse once the "timebomb" triggers. I'm using your package-release.sh script to build dxvk, using vkd3d's package-release.sh script to build vkd3d as well. Nothing goes wrong while compiling. Switching to "old" versions of vkd3d + dxvk completely gets rid of the issue. Running a game that natively uses Vulkan or OpenGL never triggers this problem (under the same proton prefix and under the same circumstances of course). I'm going to upload a video of the problem on YouTube (recorded by a friend of mine) in order to showcase the problem. |
|
Video uploaded, manually switch to 1080p if it starts at 360p. This is a footage after roughly 30 minutes of playtime. The lag "timebomb" shows up at 0:44 timestamp: |
|
Does this also happen with the builds that ship with Proton Bleeding Edge or downloaded from GitHub CI or only with self compiled? Also are you able to bisect which commit it started with? |
This is precisely what the release builds are from. MinGW stuff hasn't been updated in a year or so, so the past couple of stable releases were compiled using exactly this in release mode.
Does "old versions" include self-compiled builds of stable releases? I'm not running anything special here, just plain old KDE Wayland with (generally) no Steam overlay and (generally) no Gamescope, and RADV on a 6900XT. If this is an issue that supposedly affects any (UE4) game on any setup then what exactly is it that makes my system the special snowflake that this doesn't happen on? Sorry for the rather annoyed tone but we have a release planned soon, so if this issue actually does affect a majority of users then I need a reliable way to reproduce it in order to actually do somehting about it. |
Yes, to also answer @Blisto91 the "old versions" included my own self-compiled. I have self-compiled versions of both dxvk and vkd3d saved, but I don't know where to start, honestly, maybe we can guess something:
|
|
For the sake of having a complete background, I'm actually going to test this whole thing without using ecores on intel and by using only one ccx on amd. It's probably unrelated and nonsensical but it doesn't harm me to test, my boyfriend is also testing with me. We've been trying to troubleshoot this for days to no avail. |
|
could you send a log with also could u try windowed mode |
Yes, I'll attempt both things after testing the ecores/ccx thingy. Edit: I'm sorry because these tests take a very long time, it's 25 to 40 minutes per-test. Yet, reproducibility should be easy (not timewise of course) as long as you're playing with a mouse and a keyboard on newly compiled dxvk + vkd3d. |
funny story, I can't reproduce it either |
I'm building it while my boyfriend is testing without ecores. |
Is it actually git cloned and compiled or just picked from releases? If nobody can reproduce this here, it could actually be related to a change that affects ecores (to-be-confirmed since my boyfriend is still testing, he's playing since 31 minutes without the problem triggering as of now). |
Does not seem to be the problem. Will try no-occlusion straight away @doitsujin |
Timebomb triggered at 33 minutes with this fork. Some walls and corners were invisible. My boyfriend will test this again with debug logging, I'm going to sleep soon. Make a list of more things that I should try and I'll do it right after waking up (I don't have work so I'm free the whole day). |
|
Well, that rules out the only DXGI change since 2.4.1, so.... |
Could it be a shared change between DXVK and VKD3D? Because we don't experience that problem with neither Proton GE and Experimental, yet we used to not have that problem at all and I always compiled the latest git releases for both of us. I strictly believe that, at some point in time, something changed, and it affected both dxvk and vkd3d, and specifically "mouse handling" (probably not the right term) somehow. It's weird that anything that runs on native API (Vulkan / OpenGL) does not suffer from this issue on any Proton prefix, yet the moment we try using git compiled dxvk + vkd3d this starts triggering. It's interesting that games that run, for example, on Insomniac Engine and its forks, don't even suffer from this issue, while other games (notably Unreal Engine) have this timebomb as long as they use DXVK or VKD3D and as long as you play them with a mouse and keyboard. My boyfriend will provide debug logging until the problem starts happening, and if you can 100% conclude that this is certainly not a DXVK + VKD3D issue, I'll have to look somewhere else. Most worrying scenario would be this problem affecting the majority of people but they have no idea. We really need more people testing this. |
|
Been playing Hogwarts Legacy for around 110 mins now but haven't been able to reproduce. |
That's not exactly the steps, I meant manually compiling dxvk and vkd3d straight away and putting them in a compatibility tool. |
|
I asked above if the issue shows with the builds included in Proton Bleeding Edge or from the CI. Edit: Could you share the ones you have compiled? |
This will take a long time to test, I was mainly testing git compiled dxvk and vkd3d. Bleeding Edge breaks too much stuff, I'd rather live with the lag timebomb. |
|
I would like to try the ones you have compiled yourself to test with. Just package them up and attach here |
|
|
I've got to sleep now, I'll keep myself updated when I wake up. File attached in the previous message. |
|
Played Hogwarts Legacy for 90 minutes more, this time with the Bleeding Edge DLLs replaced with vkd3d-proton, dxvk and dxvk-nvapi from your archive. Still nothing sadly |
|
since you can build your own dxvk and know that the issue has been happening for 2 months, could you bisect it? |
My boyfriend actually tried experimental bleeding edge overnight (without my DLLs) and the timebomb triggers there as well. Are you sure you were actually playing with a keyboard and a mouse? The problem only seems to happen when using m+k. Regular Proton Experimental is completely fine and unaffected by the way. And again: native Vulkan/OpenGL games running under any of these compatibility tools do not expose the problem, so it's definitely a dxvk+vkd3d thing.
See my message above where I list my older compiled dxvk+vkd3d combos, I don't know where to start. If you have an idea, maybe a date, I can start from there and test. |
Steam Input was already turned off because that game is an aim trainer, so I turned it off to not add useless layers on top of the game. |
I probably won't do it until tomorrow because I'm strained by all these days of troubleshooting and I just don't want to deal with more log grabbing and stuff. You can feel free to post an issue, or wait until I do it, it's the same to me. |
|
I'm closing this specific issue because it's caused by Steam's I will probably open an issue at https://github.com/ValveSoftware/steam-for-linux/issues tomorrow, but you can feel free to do so as well. |
|
Actually, I just played overwatch 2 and did run into the same issue. |
Were you able to fix it with the If you need mangohud: If you also need gamemode for some reason: (you still need gamemoderun for gamemode to actually trigger) |
|
Haven't tried yet, but I'll probably play again today, have already setup LD_PRELOAD="" in the launch parameters. Thanks for being persistent in trying to solve this issue, as it's definitely a rough one. |
For me, it definitely started around the same time Valve implemented the "Record your game" thingy on Steam. And yeah I would say I'm quite persistent with things when it's not my fault, probably due to the way my work environment is (where colleagues accuse each others of having broken some code all the time), kinda reflects to other things I do. |
|
Ran into the same issue about 3 days ago as well - Thanks for the |
|
When you say your overlay is completely disabled, how do you mean? Have you taken any steps for that other than using the UI option in the Steam client to disable the overlay? |
Completely disabled through Steam's UI. |
|
Thank you for this thread @SheMelody. I thought I was going bonkers for the last few weeks looking for whatever it may have been. As I experienced this on a number of different games but not all games. I appreciate the effort you went through on this. |
|
Can confirm I have also been experiencing the same issue, but only since upgrading to Fedora 41. Couldn't find anything online and was thinking I was going crazy. Thanks for making the thread. |
|
Having the same issue, stuttering occurred in Saitsfactory. Thought it was gamescope but turning gamescope off didn't resolve it. Happened in DX12 and Vulkan mode. Disabled steam overlay. Switched from Proton Experimental to GE-Proton-9-16 It initially seems to have been resolved by adding Went stuttering in Satisfactory every 30-40m on mouse input that required a reboot of the game, to playing for almost an hour and half last session after adding the command without issue (wasn't able to test further). |
|
Thank you so much guys this issue was driving me crazy! |
|
Setting LD_PRELOAD="" seems to introduce input lag for me in Borderlands 2 |
|
Alan Wake 2 too had been showing some weird mouse lags recently (past month) on both Nobara 40 and Mint 22. It happens only if at least 15 minutes has passed. It simply will not happen sooner. I noticed this issue here, and tried to run the game on Lutris to see if lags go away and it was definitely fixed. I did not use LD_PRELOAD workaround for neither Steam nor Lutris. I never compiled anything though... playing with default Proton 9/Experimental versions on both Steam and Lutris. I shall now try other games on Steam to see if they too have this mouse lag bug after 30 mins (tried Remnant 2 yesterday but I always rage quit it before 10 mins passed, despite trying hard not to. Now going to try Empire of the Ants and possibly Hellblade 2). |
|
Ah! And god of war Ragnarok also has this problem!! |
|
I had this issue with Guild Wars 2. I want to also add what temporary fixed the time bomb was using the release version of DXVK. However this was my experience 2 weeks ago, currently experiencing mouse lag immediately in GW2. The fix for the 40 min lag time bomb was to use a release version of DXVK, however the immediate cursor lag I'm experiencing now is unrelated to DXVK. The current lag I am experiencing is worse with outside Value tree's of Proton. I've tested Experimental and GE Proton versions which have a 5-10 fps drop moving the cursor, however Proton or Wine compiled without value tree's shows a bigger fps drop moving the cursor. Again want to state this was only for Guild Wars 2, and not other games. |
|
I had relief knowing this issue was made clear when noticed in CS2 massive lag spikes after playing 30 min , warframe too when doing nothing but not in Space Engineers (maybe because crashes before experiencing this lag). |
Did you mean Counter Strike 2 or Cities Skylines 2? I seem to have a similar issue that after around 40-60 minutes of gameplay suddenly the game starts stuttering. Not sure if its this but Im gonna try LD_PRELOAD="" as well. EDIT: Actually seems to have helped... no more stutters. AMD Radeon 7900 XTX OS: |
|
Having same issue with Star Trek Online |
|
Also happens in Path of Exile 2 with its Vulkan renderer, which would mean this is unrelated to dxvk? |
|
I am seeing this also on Manjaro KDE running Fallout76 using GE-Proton9-20. The game runs perfectly smooth for about exactly 30 minutes or so then the jitter line in mangohud just goes crazy and the only fix is to restart the game. Currently using this launch parameter:
I will try some of the above fixes and report back. |
|
I can report that after over an hour it has not returned. The only thing added to the run command was LD_PRELOAD="" for a total command of: Mangohud works and so does gamemoderun without anything additional. |
|
This was occurring to me in Path of Exile 2 with both DX12 and Vulkan. |
and others
There's a literal "lag timebomb" when pulling the latest git versions of DXVK and VKD3D and compiling them. These lag timebombs are unified, meaning that they happen in both DXVK git and VKD3D git, and they trigger after roughly ~25 to ~40 minutes of gameplay and generally only trigger if the user is providing input to the game. This problem exists since roughly 2 months and I felt like it would be good to report it here. Since the problem is unified (happens on both DXVK and VKD3D) I actually didn't know where to report it.
Affected games mostly use Unreal Engine. Insomniac Engine games, for example, didn't seem to be affected.
Using a "Release" version of DXVK + a "Release" version of VKD3D seems to solve the problem.
More specifically, the game is smooth before the "timebomb" triggers, then consistent and repeated heavy stutters begin to happen. If needed, I can record a video.
EDIT: We have found out that, when this triggers, it only happens when moving the mouse.
Software information
Any game that uses DXVK or VKD3D pulled from git and compiled, this problem is unified and common in both DXVK and VKD3D
System information
Apitrace file(s)
Log files
The text was updated successfully, but these errors were encountered: