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

×
After updating the game with the latest patch, I receive an error message when launching the game via pad.exe:

"The procedure entry point _except_handler4_common could not be located in the dynamic link library msvcrt.dll"

This may be because I do not, in fact, own a gamepad, but when I delete pad.exe and try to launch the game directly, there is a persistent error message in the top left corner of the screen:

"ArgumentError: Error #3214"

Help, please?
No posts in this topic were marked as the solution yet. If you can help, add your reply
avatar
shawne: After updating the game with the latest patch, I receive an error message when launching the game via pad.exe:

"The procedure entry point _except_handler4_common could not be located in the dynamic link library msvcrt.dll"

This may be because I do not, in fact, own a gamepad, but when I delete pad.exe and try to launch the game directly, there is a persistent error message in the top left corner of the screen:

"ArgumentError: Error #3214"

Help, please?
Hi,

Please uninstall and reinstall the game. Don't use pad.exe to launch the game, please launch it via the Start menu shortcut that uses Evoland.exe. I think if you don't own a pad the game tries to look for pad-related libraries, can't find them, and then throws out an error. I think the game also uses pad.exe in its own way to check whether a pad is connected, as seen by the options menu where it states "Pad not found". Let me know if this helps :D
I'm also experiencing the same problem due to a dynamic link not found (msvcrt.dll) ... In my case I own a joypad ...

If I reinstall lose all game progress?
Post edited April 21, 2013 by rodrigoablima

Hi,

Please uninstall and reinstall the game. Don't use pad.exe to launch the game, please launch it via the Start menu shortcut that uses Evoland.exe. I think if you don't own a pad the game tries to look for pad-related libraries, can't find them, and then throws out an error. I think the game also uses pad.exe in its own way to check whether a pad is connected, as seen by the options menu where it states "Pad not found". Let me know if this helps :D
No, that didn't help at all - the error message kept coming up. The solution is to delete the d8input dll file - no msvcrt error after that, and in the absence of a gamepad there's no error message in the corner.

Hi,

Please uninstall and reinstall the game. Don't use pad.exe to launch the game, please launch it via the Start menu shortcut that uses Evoland.exe. I think if you don't own a pad the game tries to look for pad-related libraries, can't find them, and then throws out an error. I think the game also uses pad.exe in its own way to check whether a pad is connected, as seen by the options menu where it states "Pad not found". Let me know if this helps :D
avatar
shawne: No, that didn't help at all - the error message kept coming up. The solution is to delete the d8input dll file - no msvcrt error after that, and in the absence of a gamepad there's no error message in the corner.
I also have this problem with pad.exe. I followed your suggestion and the game worked perfectly for me with no error messages. It even detected my logitech cordless rumblepad and I'm now able to use it in the game.

Thank you for this solution.
avatar
shawne: No, that didn't help at all - the error message kept coming up. The solution is to delete the d8input dll file - no msvcrt error after that, and in the absence of a gamepad there's no error message in the corner.
avatar
jr135659: I also have this problem with pad.exe. I followed your suggestion and the game worked perfectly for me with no error messages. It even detected my logitech cordless rumblepad and I'm now able to use it in the game.

Thank you for this solution.
Yup. Deleting the d8input.dll file worked for me as well. No more error messages and game-pad support is now working.
The dinput8.dll's trick works fine for me. Thanks !

For info, my gamepad is a Logitech Dual Action (pretty old).
Post edited December 14, 2013 by mamieyannick
Renamed the dinput8.dll and the controller errors went away for my wireless xbox 360 controller. Thanks for the tip, shawne
Post edited May 11, 2014 by sangley