New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This application has requested the Runtime to terminate it in an unusual way. #405
Comments
In dinput8.ini, under the line |
Sorry for the delay! Here's the dxvk.log Also, as a side note, a bug/problem I've noticed, setting the speed override hotkey to ' some reason makes the game refuse to launch. I was stuck figuring out why my game kept making refusing to load, and after a lot of repeat reboots and one by one redoing my settings, I narrowed it down to that. |
Ah, you're right. I never noticed that before, but it seems to be a problem with the ini reader we're using: It is trying to remove single and double quotes from strings, but that obviously breaks our hotkeys. Hmm.
Thanks, but it looks like there's nothing too helpful there... I improved our d3d9 fallback in this build: |
Here's some of my specs! And other details from where I got it from
And it is a laptop, yes, as well as downgraded from Windows 11 Home to Windows 10 Home. |
Seems the call to |
True, in any case, I'm not sure how to deal with the problem, since I keep my drivers up to date whenever possible, so I really have no clue what else I could do other than that to fix the problem. (That being said, I do note that I've just been keeping my Nvidia driver up to date, not the AMD ones, if that some reason makes any difference/explanation?) |
You've mentioned you're using a laptop, right? Is your Nvidia GPU set as the "Preferred graphics processor" in the nvidia control panel? The AMD stuff shouldn't matter here, I think. |
Validation
Describe your issue here (drag+drop ZIP to attach it)
Game Version - 1.1.0
I'm not really sure how to tackle this issue, and even though I think it might be on my end, in case it's important, I'm submitting this here in order to catch it. I just know it has direct relation to the Vulkan Renderer. Disabling it via the ini is what gets around the crash. Turning it back on results in it happening again.
I also have the crash via the CrashDump.
The text was updated successfully, but these errors were encountered: