Open duke1102 opened 6 years ago
Hey there. Yeah, that looks like a bug. The exception IS thrown when initializiing any joypads at boot. I'll look into it as soon as I can.
Hey @Asnivor - thanks for the quick reply!
I just build the source myself and could identify the problem. I had a software called PC Remote from Monect installed, which allowed me to control my PC via an Android phone and use it as a mouse/keyboard/gamepad. The software created it's own device driver "Monect Hid Device" which ultimately caused the exception to happen.
After I uninstalled the software and device from the device manager... voila, MedLaunch launched without problems.
Exception gets thrown on line 129 in the GamePad.cs, where it checks if the ContInfoFromLog.Count() > 0. This "Monect Hid Device" did fool the if-check and caused to go boom. Might want to use a try-catch block here too, even if this issue is rather rare.
Keep up the good work! I hope I helped!
Awesome stuff, thanks. Thats a great help.
I guess I never assumed there would be a gamepad device that would be detected in slimdx, but not in mednafen. Duh. I will certainly get this fixed up when I next have the chance.
Thanks again!
Hey!
So I encountered a critical issue with MedLaunch today, when I wanted to test it out. The issue happened with the current production release v0.5.25.3 and v0.5.25.4-DEVBUILD-133. I also tried to use Mednafen v1.21.3 and v1.21.1 (64bit) - same issue.
I'm using Windows 10 Pro 64bit.
According from the exception log I assume it has something to do with the Gamepad initializing. I'm using a wired XBOX 360 Gamepad connected via USB. After unplugging it, the same crash happens.
Even after trying a fresh copy of MedLaunch and Mednafen again with the gamepad unplugged, it threw the same exception. So not sure if it is caused by my controller.
Here's the exception.log file it created: Exceptions.log
If you need any further details about my system specifications and such, let me know!