dxvk: Warframe freezes with DXVK >0.90
EDIT:
solution:
either enable or disable vsync in game (esc->options->display) because “auto” breaks.
referencing https://gitlab.com/GloriousEggroll/warframe-linux/issues/70#note_122987817, it seems the versions including/supporting stream output reliably freeze Warframe (leaving behind an unresponsive window, the background music still playing and 3 threads at 150% cpu to be killed before restarting the game) on average every 5-15minutes.
downgrading to 0.81 has fixed the issue for some people (including me), so while not 100% sure stream output is the culprit it seems to be pointed to by that.
maybe we could get a d3d11.fakeStreamOutUnsupported setting to DISable stream output and/or more logging facilities related to it to debug this further?
EDIT: please excuse my lack of an apitrace, but it’s simply not possible to reliably run the game without dxvk due to a memory management issue in the microsoft dlls in combination with linux allowing larger memory chunks to be allocated than win does.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 48 (8 by maintainers)
i am not, i’m just saying it’s a different one
because you were
oh it’s “clear” now? who’s gaslighting again?
i have used dxvk 0.90, 0.96 and 1.0, on nvidia cards, as have others here, and none but you has the issue. and you yourself said it does not depend on vsync. and you yourself said >0.81, not >0.90, so it’s clearly a different issue than this one that freezes on >0.90 depending on vsync.
a) how do you know that, and b) how does that mean it’s dxvk’s fault, you just said it only happens on your nvidia setup.
oh ok, yes, good point, so you just confirmed it’s still a different issue because the one in this thread was warframe’s fault?
as i said a bazillion times already: it does not happen on my system, which is currently dxvk 1.0 on nvidia. so it cannot be dxvk>0.81 fucking up on nvidia.
the same logical reason that fails at literally every step of the way by ignoring you’re the only one having this problem that’s unrelated to this thread’s issue?
and more ad hominem bs, you sure it’s not your feelings you’re talking about here? i mean you’re the one crying about “gaslighting” just because i don’t have the same bug you experience…
yeah that’s reeeaaaaally victim like behaviour.
a) i’m not a man b) i’m not little c) i’m not intend on “not worrying anymore”, i’m intent on getting your problem fixed instead of trying to hide it in another resolved issue’s thread. because you hijacking this resolved one will only serve to obscure it from the devs instead of getting it fixed.
start reading, maybe? you are affected by something else, since this one is fixed, which is why i’m telling you it’s more effective to actually start a new issue for it. you’re just lowering your chances of getting your issue resolved by burying it in another one and then bitching about how people are “gaslighting” for trying to help you.
you just literally presented a textbook definition of actual gaslighting by saying that sentence.
You’re gaslighting because you’re deliberately avoiding the issue and trying to convince me that everything I said was wrong. Hell, you even gaslit me about answering how I gaslit you by misrepresenting the fact that by context, it’s clear I was referring to the post before my ad hominem, not your reply saying I made ad hominem attacks.
You wanna talk about logical fallacies, then stop making them yourself first.
As for the actual issue, stop making excuses. I told you, I already tested everything. This issue only affects DXVK versions >0.81, and only with nVidia cards. It doesn’t affect DXVK + AMD/Intel & it doesn’t affect Windows. And the fact that it doesn’t affect DXVK 0.81 tells me it’s not nVidia’s drivers or even Warframe either, but rather a specific piece of code within DXVK either geared explicitly for nVidia cards or otherwise missing an exception for nVidia cards that 0.81 had.
Logical reasoning led me to this, so all your excuses trying to blame me are exactly that: excuses meant to protect your own fragile feelings.
As for locking this thread down, I’d just suggest the proper solution: Editing the main post and/or title, as well as re-opening the issue to reflect the findings I’ve made. Only after that do we delete the comments dealing with your undue attacks on me and my retaliation against those attacks.
You can unsubscribe from this anytime you want, little man, since you seem intent on not worrying about it anymore. I don’t have that luxury since I’m still affected by it & need it fixed so that I don’t have to keep using hacky workarounds such as downgrading DXVK. You’re choosing to continue participating, and as a result, I’m forced to keep setting the record straight. Just unsubscribe, go away, and leave this to the people who actually know what they’re talking about because you clearly don’t.
I’ll address the last part first since it’s the easiest because I already explained it: The issue still exists. It’s just hidden behind a workaround. Put Warframe’s VSync setting on auto and it fucks up again. We all know this. For proper implementation, DXVK has to work on all settings. Therefore this is still a valid bug and needs to remain open.
As for the rest, I’ll start playing fair again when you do. Stop the gaslighting and I’ll stop the ad hominems. I told you my issue experiences the exact same symptoms as yours with the exact same set of requirements, and that I’ve already checked everything to make sure it was nothing on my end. A new issue would just be considered a duplicate of this one – especially since this one has to remain open anyway.
What kind of reply is that? “Do what you should’ve done”? I have been. And you know how I know you’re just being a dick here? You mention my proton installation being a possible cause, which shows you haven’t actually read my reply where I mentioned I ALREADY TESTED THAT WITH A FRESH PREFIX! So don’t you dare dismiss me and my evidence and try to tell me it’s something on my end, giving a dozen different reasons that, I repeat, I’VE ALREADY TESTED just so you can feel superior.
Everything I’ve seen indicated it’s the same issue, just that 1.0 is better with not locking up the CPU anymore. I’m still stuck with DXVK 0.81 because of this since that’s the latest version that’s unaffected by this issue because it’s the same. goddamn. issue.
Edit: Also, “just turn VSync on or off” is not a fix. It’s a workaround, at best. The underlying cause is still present and needs to be addressed, so even if you wanna assume my issue is different, this issue should still remain open.
@oswaldtechnic well they tried to default to d3d11, that’s why they needed the hotfix to actually do that because they screwed up that change and forced d3d10 on everyone 😛
and also, yes we’re aware of those changes, they’re unrelated to this issue though. only relevance is we’re glad dxvk works pretty much perfectly now because the wined3d10/11 alternative was hell.
also i feel this issue is
so given i’m the one who opened it and nobody else is doing it i guess i’m gonna close it now