Skip to content
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

Closed
2 tasks done
InsideCat02 opened this issue Dec 27, 2022 · 8 comments
Closed
2 tasks done
Labels
bug Something isn't working

Comments

@InsideCat02
Copy link

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.

image

I also have the crash via the CrashDump.

@InsideCat02 InsideCat02 added the bug Something isn't working label Dec 27, 2022
@nipkownix
Copy link
Owner

In dinput8.ini, under the line UseVulkanRenderer = true, please add a new line with DXVK_LOG_LEVEL = debug. This will create a dxvk.log in the re4_tweaks folder the next time you run the game. Hopefully there will be some helpful information there.

@InsideCat02
Copy link
Author

InsideCat02 commented Dec 28, 2022

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.

@nipkownix
Copy link
Owner

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:
https://github.com/ThirteenAG/IniReader/blob/85c2845b9dda0fa1f36612f8476d432dab1730d7/IniReader.h#L216

It is trying to remove single and double quotes from strings, but that obviously breaks our hotkeys. Hmm.

Sorry for the delay! Here's the dxvk.log

Thanks, but it looks like there's nothing too helpful there...
What are your specs? Are you using AMD or Nvidia? Is it a laptop?

I improved our d3d9 fallback in this build:
https://github.com/nipkownix/re4_tweaks/suites/10070218481/artifacts/490377396
If you try running with the vulkan renderer again, and it fails, the reason for the failure should now hopefully be in dinput8.log. Could you give it a try?

@InsideCat02
Copy link
Author

InsideCat02 commented Dec 28, 2022

Here's some of my specs!

image

And other details from where I got it from

AMD Ryzen 7 5800H 3.2GHz Processor
NVIDIA GeForce RTX 3050 4GB GDDR6
16GB DDR4-3200 RAM
512GB Solid State Drive
Microsoft Windows 11 Home
10/100/1000 Network
2x2 802.11ax Wireless
Bluetooth 5.0
15.6" FHD IPS LED-backlit Anti-Glare 120Hz Display

And it is a laptop, yes, as well as downgraded from Windows 11 Home to Windows 10 Home.

As for the new dinput8.log, here you go!

@nipkownix
Copy link
Owner

[18:23:21] [t 43420] hook_Direct3DCreate9 -> DXVK error: DxvkInstance::enumAdapters: Failed to enumerate adapters
[18:23:21] [t 43420] hook_Direct3DCreate9 -> Falling back to D3D9

Seems the call to vkEnumeratePhysicalDevices fails, so this is a problem with your setup. Your GPU should support Vulkan just fine, so I can only imagine there's some issue with your drivers.
At least the improved fallback does let the game use d3d9 if Vulkan fails in this way now.

@InsideCat02
Copy link
Author

At least the improved fallback does let the game use d3d9 if Vulkan fails in this way now.

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?)

@nipkownix
Copy link
Owner

nipkownix commented Jan 1, 2023

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.

@InsideCat02
Copy link
Author

InsideCat02 commented Jan 1, 2023

Is your Nvidia GPU set as the "Preferred graphics processor" in the nvidia control panel?

I've sometimes flopped back and forth between just auto-selecting and setting it to be the preferred GPU, and usually with auto-select, it'll automatically go with the Nvidia GPU for RE4, so yeah, it probably shouldn't matter, it was just an idea (that in hindsight reminded me to update AMD stuff just in case. I WAS pretty outdated regardless.)

image

EDIT: Just after posting this by the way, I tried running with Vulkan again, and this is after updating my AMD stuff, and apparently that actually fixed my issue??? Because the frame rate counter is also coming up and everything. It may have updated a lot of things, including Vulkan drivers, maybe.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants