It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hello guys, I've got a little problem here. The problem is: the crame crashes after connecting gamepad. Controller is working, 'cause I've checked it with Tomb Rider aned it worked well. Funny thing is, Divinity is running perfect, i can launch it, start the game etc. but it crashes after connecting the joystick. On the other hand when I plug in the pad before launching the game refuses to start. Windows just beeps and that's all. Yeah, I've emulated it with 360ce. Please, help buddies :(
avatar
ladywolfshead: Yeah, I've emulated it with 360ce.
Was it crashing before you tried that?

Try uninstalling or updating the controller's drivers, and/or disable force feedback in the drivers (if possible) or through x360ce.
I can confirm this. D:OS EE immediately crashes on startup any time I have a joystick connected. I've tried it with both a USB Xbox 360 control pad and a Mayflash Wii U Pro Controller adapter (which provides an Xinput input device just like the 360 pad). USB devices plugged in, D:OS crashes; after unplugging them, it launches just fine.

My drivers are up to date, I've tried verifying my installation, and I've done a complete uninstall and clean reinstall. Same problem every time.

System specs:
Windows 8.1 64-bit
Intel Core i7-4770K 3.50 GHz CPU
8 GB RAM
Gigabyte G1 Gaming GeForce GTX 1080 video card

I've also noticed that D:OS produces CrashDump files in its Shipping directory every time it crashes, so I can send one of those somewhere if you'd like.
avatar
minneyar: D:OS EE immediately crashes on startup any time I have a joystick connected. I've tried it with both a USB Xbox 360 control pad and a Mayflash Wii U Pro Controller adapter
Try uninstalling the drivers. The Xbox controller should certainly work; I'm not sure if it was a Mayfield adapter, but one person reported using a Wii U adapter fine in Xinput mode, but it caused a crash in Dinput mode, until they uninstalled the drivers (which were only needed for force feedback support).

If you check the Event Viewer, does that give an error code or 'Faulting Module' file name?
With controllers (and a USB hub) reported to cause this issue, the faulting module names have been ntdll.dll and EZFRD64.DLL.
- click Start (or WinKey-R or WinKey-W in Win 8), then type "event viewer" into the search box
- after starting the Event Viewer, expand 'Windows Logs' in the left column and select 'Application'
- in the center column, look for a recent error (maybe sort by Date and Time) for the game
- check the information under the 'General' tab below the list of events, starting with "Faulting application name..."
After rebooting, I see the behavior you describe, including the error in EZFRD64.DLL, so maybe something had gotten stuck and just needed a reboot...

In any case, I decided go to through and test it with every gamepad I have. The following all worked fine:
Xbox 360 wired USB game pad
2 PS4 Bluetooth game pads
PS2 game pad connected through a SmartJoy PLUS adapter (DirectInput)
Razer Onza game pad
Logitech Extreme 3D Pro joystick (DirectInput)

All of them work fine; only the Mayflash adapter in DirectInput mode causes a crash. That seems to imply that it's a problem with that driver, but it's odd that I haven't had issues with any other games.