I tested my own projects, several other games and even new blank projects, none of which works.1) download the sample game Crysalis from this site to check wether it might be a script that causes problems with input (Crysalis doesn't use any scripts, but especially if you're trying the gamepad with a game that has a mouse script or extended keyboard scripts applied, then there is a chance that they might conflict.
I didn't ask because the drivers might be defective, but because Microsoft introduced several different methods for input drivers in the last 20 years, and not all methods are compatible.The drivers work fine, you only need to download them if you use XP or lower and I have Windows 8. Also, the gamepad functions work perfectly in other games, rumble and all.
But it's basically 360 controller. I have used 360 controller before at my friend's place on RPGmaker games.I didn't ask because the drivers might be defective, but because Microsoft introduced several different methods for input drivers in the last 20 years, and not all methods are compatible.
If two drivers use the older methods (and as fas as I know RM does access the older API for getting input data), then they can block each other. That's one reason why you shouldn't use a not needed input driver - if that driver redirects the input data (like for example several older tablet drivers do), it can mix up RM's input detection.
Then it's something to do with your comp (so it could be the drivers like Andar said), since the controllers work on the RM games on your friend... try the workaround posted before this...But it's basically 360 controller. I have used 360 controller before at my friend's place on RPGmaker games.
You are the man. My controller suddently stopped working and setting it as my "Preferred device" did the trick. Thans a lot !I had the same problem when I first got RPG Maker VX Ace, where it didn't work with my controller (I have a Logitech Dual Action game controller).
But, after a bit of fiddling around on my own I figured out the fix was to set my game-controller as a "Preferred device".
I'm using Windows 7 (so I'm not sure if the following instructions would work if you had a different version of Windows, but I imagine it would be similar).
Open up your Game Controller properties via Windows.
One simple way you may do this, click on the Windows Start button, and in the "Search programs and files" field enter in the words "game controller" (without the quotes), and one of the things it finds should be "Setup USB Game Controllers", select to run that.
In the Setup Game Controller properties box, there should be an "Advanced" button, click on that. Before, my "Preferred Device" was blank (not selected), but from the Dropdown Menu, select your game-controller you want to set as the "Preferred Device" (whatever the game-controller you want to use that you have have connected to your computer). After that, click "OK" to accept the changes (you could also click on the "Properties" button to Test your game controller there as well).
Well, that's what "fixed" it for me, and hopefully it should fix it for you (or other people) who may have the same problem.
Cheers!![]()