Monster Hunter Wilds

Monster Hunter Wilds

View Stats:
Bum Mar 15 @ 1:49pm
Anyone crashing and using a dual sense edge controller
It seem there is an issue with SteamAPI and wilds doesn't support controllers natively.......

The only fix that seems to work is using DS4Window to emulate Xbox360 controller then use HidHide to hide DualSense Edge from the system. To check if it's hidden open the controller config in steam. If DSE doesn't appear you're good.

That's the only thing that worked for me. After swapping direct storage, updating chipset cpu, update gpu, removing turbo from bios, etc .... nothing worked but emulating another controller.
< >
Showing 1-15 of 22 comments
VNRG Mar 15 @ 2:22pm 
I have turned off bluetooth and use wired connection for my PS5 controller, no crashes at all as well, guess there are multiple options to fix this problem
Nauct Mar 15 @ 2:23pm 
I use the Edge, but I completely removed Windows Gamebar. It caused issues in other games before, so I always manually remove it
Bum Mar 15 @ 2:44pm 
Originally posted by VNRG:
I have turned off bluetooth and use wired connection for my PS5 controller, no crashes at all as well, guess there are multiple options to fix this problem

Dual sense Edge is not the same as dual sense.
VNRG Mar 15 @ 3:08pm 
Originally posted by Bum:
Originally posted by VNRG:
I have turned off bluetooth and use wired connection for my PS5 controller, no crashes at all as well, guess there are multiple options to fix this problem

Dual sense Edge is not the same as dual sense.
ah I see, but still both controllers including ps4 are causing crashes/BSOD with the clock_watchdog_timeout, sucks that we need multiple different solutions for them
Can you tell me how you did that? I have both hidhide and Ds4 but while in big picture mode it still shows my ps5 controller inputs so its reading it as both an xbox controller and such.
Bum Mar 15 @ 5:16pm 
Originally posted by Le_Skully:
Can you tell me how you did that? I have both hidhide and Ds4 but while in big picture mode it still shows my ps5 controller inputs so its reading it as both an xbox controller and such.

Open HidHide configration and add DS4Windows as tool. Everything in that list is on a white list. Then open ds4Windows and emulate xbox 360. Once you see there are 2 controllers, in HidHide check dualsense and click enable hiding. Then disconnect your dual sense and reconnect it. You should now have only xbox 360 in steam if you did everything correctly.
Metalped Mar 15 @ 7:45pm 
Yeah I switched from the sense edge to the Nintendo switch controller and the game runs fine now.
FreakyFred Mar 15 @ 11:16pm 
I only crashed once in entire time playing the game and I been using one wired majority of the time. Not using anything other than steam and the Capcom official profile layout
Last edited by FreakyFred; Mar 15 @ 11:18pm
Bum Mar 15 @ 11:19pm 
Originally posted by FreakyFred:
I only crashed once in entire time playing the game and I been using one wired majority of the time.

Shouldn't be possible. The issue comes from SteamApi. You are probably not talking about Dual Sense EDGE or are just saying bs for no reason.
i got the bsod because of my 12th gen cpu and ds4.. fix was to turn off e cores in bios. I've heard some say the xbox controller emulator helped them. Odd problem.
I'm experiencing the same problem with the DualSense Edge :( both the game and Steam crash whenever it's connected. Has anyone managed to find a solution?
I don't use dual sense edge nor ever heard of it so can't help you there but I use ps4 controller and it works fine without even needing ds4windows.
Originally posted by MonkeyDog:
I'm experiencing the same problem with the DualSense Edge :( both the game and Steam crash whenever it's connected. Has anyone managed to find a solution?

Only thing that's worked for me so far has been using hid hide to hide the controller and ds4windows to emulate an xbox controller. I've heard disabling ecores for your cpu (if you have a 12th gen intel) works but I haven't tried it personally. Sounds like the steam input api for dual sense edge isn't working correctly and causing the "CLOCK_WATCHDOG_TIMEOUT" bsod.
Originally posted by Corporal Chromosome:
Originally posted by MonkeyDog:
I'm experiencing the same problem with the DualSense Edge :( both the game and Steam crash whenever it's connected. Has anyone managed to find a solution?

Only thing that's worked for me so far has been using hid hide to hide the controller and ds4windows to emulate an xbox controller. I've heard disabling ecores for your cpu (if you have a 12th gen intel) works but I haven't tried it personally. Sounds like the steam input api for dual sense edge isn't working correctly and causing the "CLOCK_WATCHDOG_TIMEOUT" bsod.

I'll give it a try then. I tried it with DSX on Steam though but still having the same issue. My regular Dualsense works just fine. But the Edge one was problematic.
Originally posted by MonkeyDog:
Originally posted by Corporal Chromosome:

Only thing that's worked for me so far has been using hid hide to hide the controller and ds4windows to emulate an xbox controller. I've heard disabling ecores for your cpu (if you have a 12th gen intel) works but I haven't tried it personally. Sounds like the steam input api for dual sense edge isn't working correctly and causing the "CLOCK_WATCHDOG_TIMEOUT" bsod.

I'll give it a try then. I tried it with DSX on Steam though but still having the same issue. My regular Dualsense works just fine. But the Edge one was problematic.
Hidhide is the important part, if steam can detect your dual sense edge before you launch the game you're going to end up crashing eventually. Steam controller API broke for the edge and until it gets fixed you either have to make sure it's not picked up by steam or just use a different controller
< >
Showing 1-15 of 22 comments
Per page: 1530 50

Date Posted: Mar 15 @ 1:49pm
Posts: 22