I've heard that, with the XBCD+360 Patch drivers, the 360 wired pad rumble feature could work for Project 64 with N-Rage's input plugin. Well, I've got the Microsoft Xbox 360 wired gamepad and have those XBCD drivers installed and the profile loaded that seperates the left and right triggers to their own axis. I'm able to assign the N64 buttons onto the 360 gamepad, but when I go to the part where you configure mempak or rumblepak the drop-down box under select force feedback device doesn't show anything but "none". I happen to have N-Rage input plugin version 2.00a. Am I not doing something right or does the 360 pad's rumble feature not work yet with Project 64?
Xbox 360 Controller rumble help
- Thread starter mattg568
- Start date
squall_leonhart
The Great Gunblade Wielder
you used the full installer for that 360 patch didn't you
theres a bug in that, so you need to install the XBCD driver and the 360 patch seperately.
btw, check the plugins section of this forum for the new nrage plugin
theres a bug in that, so you need to install the XBCD driver and the 360 patch seperately.
btw, check the plugins section of this forum for the new nrage plugin
squall_leonhart
The Great Gunblade Wielder
yes 
squall_leonhart
The Great Gunblade Wielder
yes very wierd :|
it doesn't really matter, as long as it works
it doesn't really matter, as long as it works
squall_leonhart
The Great Gunblade Wielder
- Thread Starter
- #9
I uninstalled the XBCD drivers and reinstalled XBCD1.07 and then this new 360 exe file. Upon updating the microsoft driver to the XBCD Xbox360 drivers the controller refused to be detected. There was a yellow circle with a black character in the center next to the XBox 360 controller. So now I've unstalled the drivers again and reinstalled the XBCD and the 360 patch bat file to actually get the controller to be detected.
squall_leonhart
The Great Gunblade Wielder
you have to restart between installs
its a problem with the way the driver disengages i think, it happens to me when i install the full install, then go back to just the xbcd drivers (i only an xbox stype but the new drivers have a few fixes)...
easiest way
plug in control
open device manager, and remove the control form there
unplug control
uninstall the xbcd drivers
RESTART
install the xbcd 1.07, then install the 360 patch installer
plugin in the control
pray it works, it should though. does for me.
its a problem with the way the driver disengages i think, it happens to me when i install the full install, then go back to just the xbcd drivers (i only an xbox stype but the new drivers have a few fixes)...
easiest way
plug in control
open device manager, and remove the control form there
unplug control
uninstall the xbcd drivers
RESTART
install the xbcd 1.07, then install the 360 patch installer
plugin in the control
pray it works
, it should though. does for me.- Thread Starter
- #12
Update: Just a few minutes ago I loaded up Zelda: Ocarina of Time and when I selected my save game file the controller rumbled and would not stop rumbling. Even if I stopped the emulation and closed Project64 the rumbling continued. It would only quit the rumbling if I opened the XBCD setup utility. After it stopped rumbling I went back to playing OoT and the controller did not rumble upon selecting the save file, but I tested the rumble again by having Link roll into a wall. Then the constant rumbling started again. I decided to restart Windows XP and it works normal now. I wonder what made the controller rumble on and on until I went into the XBCD setup utility?
squall_leonhart
The Great Gunblade Wielder
i had that once myself, i just unplugged the control and put it back in.
Smythe
New member
Same Problem as Above
Hope it's ok to bump this thread back up but I'm having trouble with the exact same problem and after following this thread I still can't get the forcefeedback/rumble to work on my controller. Admittedly I did deviate slightly as when I plugged the controller back in I had to change the driver by hand as detailed here Xbcd 360 Install Guide. I'm sort of guessing that something happened that caused me to need to do this and even though the controller works in the game panel that same something is preventing the rumble from working in Project 64.
The controller is the MadCatz XBox 360 controller as shown here http://www.gamestop.com/product.asp?product%5Fid=802218
I installed XBCDv107.exe and the XBCD360XP.exe and everything works in the XBCD testing interface. Both rumble motors work and all the buttons work (except for the silly xbox button in the middle). I've checked on several other sites and tried the N-Rage's Plugin v1.80a v1.83 and v2.00a. None of them activate the motors and even the "Test Rumble" button in the v2.00a plugin doesn't work.
Anyway, I would appreciate any help you guys can offer. I know this is sort of a trivial thing in the grand scheme of things, but I would just like to have it working mainly for MarioCart and Zelda (which is what my son and I like to play together). Thanks for any help and for a great emulator that keeps the N64 alive.
-Smythe
Hope it's ok to bump this thread back up but I'm having trouble with the exact same problem and after following this thread I still can't get the forcefeedback/rumble to work on my controller. Admittedly I did deviate slightly as when I plugged the controller back in I had to change the driver by hand as detailed here Xbcd 360 Install Guide. I'm sort of guessing that something happened that caused me to need to do this and even though the controller works in the game panel that same something is preventing the rumble from working in Project 64.
The controller is the MadCatz XBox 360 controller as shown here http://www.gamestop.com/product.asp?product%5Fid=802218
I installed XBCDv107.exe and the XBCD360XP.exe and everything works in the XBCD testing interface. Both rumble motors work and all the buttons work (except for the silly xbox button in the middle). I've checked on several other sites and tried the N-Rage's Plugin v1.80a v1.83 and v2.00a. None of them activate the motors and even the "Test Rumble" button in the v2.00a plugin doesn't work.
Anyway, I would appreciate any help you guys can offer. I know this is sort of a trivial thing in the grand scheme of things, but I would just like to have it working mainly for MarioCart and Zelda (which is what my son and I like to play together). Thanks for any help and for a great emulator that keeps the N64 alive.
-Smythe
squall_leonhart
The Great Gunblade Wielder
uninstall the xbcd drivers cmpletely and try reinstalling
Smythe
New member
Thanks for the quick reply Squall.
I removed the XBCD driver (Couldn't find a remove for the 360 exe), I followed the install path detailed above in post 10 tossing in an extra reboot or two to make sure the old drivers were gone.
Went through the entire process of re-installing XBCD and the 360 exe and then plugged the controller back in. In device manager the controller comes up under "Microsoft Common Controller For Windows Class" as a sub key "Microsoft Common Controller For Windows".
Checking the Driver Details it's still using "C:\WINDOWS\system32\DRIVERS\xnacc.sys"
When I launch the XBCD Setup Utilitiy I get no controllers showing up in the drop down.
One thing I noticed was when installing XBCD I received the following in a dialog box
If this is not an upgrade, you will need to unistall
the existing XBox controller in Device Manager before continuing.
Do you with to continue?
I checked Device Manager again and saw nothing; I also googled for this without finding anything. Is the controller not getting deleted properly when I uninstall it from Device Manager?
Just some extra micelaneous info. The System is WinXP Pro fully updated. 3Gigs of Ram and a pair of 2.4 Ghz Xeons (It's a beast for Database Development work I do). The Controller Device Instance Id is USB\VID_0738&PID_4716\243DD9A.
Thanks again,
-Smythe
I removed the XBCD driver (Couldn't find a remove for the 360 exe), I followed the install path detailed above in post 10 tossing in an extra reboot or two to make sure the old drivers were gone.
Went through the entire process of re-installing XBCD and the 360 exe and then plugged the controller back in. In device manager the controller comes up under "Microsoft Common Controller For Windows Class" as a sub key "Microsoft Common Controller For Windows".
Checking the Driver Details it's still using "C:\WINDOWS\system32\DRIVERS\xnacc.sys"
When I launch the XBCD Setup Utilitiy I get no controllers showing up in the drop down.
One thing I noticed was when installing XBCD I received the following in a dialog box
If this is not an upgrade, you will need to unistall
the existing XBox controller in Device Manager before continuing.
Do you with to continue?
I checked Device Manager again and saw nothing; I also googled for this without finding anything. Is the controller not getting deleted properly when I uninstall it from Device Manager?
Just some extra micelaneous info. The System is WinXP Pro fully updated. 3Gigs of Ram and a pair of 2.4 Ghz Xeons (It's a beast for Database Development work I do). The Controller Device Instance Id is USB\VID_0738&PID_4716\243DD9A.
Thanks again,
-Smythe
squall_leonhart
The Great Gunblade Wielder
Smythe, if you can wait, i've just isolated why the full install doesn't work for anyone and have passed the info to Teal
Smythe
New member
Not a problem I can wait. My son and I already enjoy PJ64 as is I was just hoping to add to it by getting the old Rumble pack effect. Let me know what I can do to help. I'm availible to test out anything and I'm a java/C# programmer by trade so I'll help out with what I can, but I'm not really a driver developer so I'll most likely be pretty limited.
-Smythe
BTW, I checked out your post at redclouds to teal'c is all that's needed is adding the Reg Keys? That'd be pretty simple to test out.
-Smythe
BTW, I checked out your post at redclouds to teal'c is all that's needed is adding the Reg Keys? That'd be pretty simple to test out.
Last edited:
squall_leonhart
The Great Gunblade Wielder
yeah, the 1.07 installer creates them but the xbox360 full install doesn't.
..that and redclouds has gone down again ...well i can't get on there anyway
the code i posted over there you can just add to a textfile and rename it to (name).reg an install it
err.. but you'll need to move the 3 xbcd files from the main windows folder to system32
..that and redclouds has gone down again ...well i can't get on there anyway
the code i posted over there you can just add to a textfile and rename it to (name).reg an install it
err.. but you'll need to move the 3 xbcd files from the main windows folder to system32