Menu
What's new
By:
Filters

Games don't see rumble pack.

M

Marfoo

New member
Well I've been trying to get this Xbox 360 controller to rumble for quite some time. I have tried the XBCD 360 drivers and N-rage with no success. I have tried the original MS drivers and N-Rage with X-input with no success.

Then I noticed (testing with Conker's Bad Fur Day) in the original N-rage and modified N-rage with Xinput, with rumble pak inserted, on the menu screen it was still displaying "Insert Rumble Pak". It seems F-Zero can't see it as well, nor Banjo Kazooie or Tooie.

Any ideas?
 
Last edited:
OP
M

Marfoo

New member
That's the installer I used for XBCD, and I've tried that N-rage too. I've read just about every forum on 360 rumble and I'm pretty well informed on how all this works. The problem is not XBCD, I know those installed correctly, but games don't see the rumble pak when I tell N-rage to use one. No matter what N-rage plugin I use. I've tried just rumble pak, raw data and visual rumble, and the games still don't see it.

Just for future reference - I'm not asking about getting my 360 controller to rumble, I need help getting N-rage's rumble pak to work period.

No offense to the above response, that should work as it's worked for everyone else.
 
Tre

Tre

Oops. Died again.
You might have artifacts of previous versions of N-Rage's (and other) input plugins stuck in your registry. Maybe if you clear THOSE out, uninstall PJ64, and the XBCD drivers, and then try installing the drivers (there's a bunch of explaination for this in Squall's link he gave, including installing the drivers SEPERATELY and NOT bundled), followed by PJ64, and lastly test to see if with N-Rage (try the v1.83 FIRST) you actually GET rumble to appear on games that you KNOW how them.

The FAQ page teaches you how to kill the Registry files, and you won't have to worry about killing your computer because of it, as it saves the registry files for the plugins under their ~author(s)~ and those files can be deleted without harm to Windows. I'd get into more details on it, but I've not the time right now.

This solution I am offering has helped me with ~speed~ issues in the emulator because my computer was being greatly bogged by plugin artifacts and may well help you with your ~controller~ troubles. It's a start, at least.
 
OP
M

Marfoo

New member
Sounds like a good approach. Microsoft should really work on a way to keep that registry clean so we don't have to ;) .

I'll see what I can do, I appreciate all the help!
 
Tre

Tre

Oops. Died again.
Usually a registry plugin purge, followed by a clean reinstall will clear up bigger problems (as in your case). So I'm glad it worked for you too. Make sure that (in the future) when you're installing plugins to remove the former ones (if you want to update or switch totally, that is) before you install your new ones. This will keep you from having artifact problems with your N64 emulators, such as slow down, garbled sound, video corruption, and controller glitches.

As for Microsoft's registries becoming dirty, a small (okay big really) part of the problem is that PJ64 (and other N64 emulators) have to save to the registry to keep the plugins working with Direct X applications. While this isn't normally a problem (as it keeps the settings for you and makes loading the games and plugins VERY quick opposed to non-registry entries) if you remove the plugin, it still has it's entry in the registry and it's settings still. So PJ64 will go "Hey, didn't I have xxx installed? Where is it?! Now I'm not going to work because I can't find the plugin but I want to follow it settings!".

I think that it would be wonderful if PJ64 and N64 emulators in general could not only uninstall the software, but the registry entries too. ^_~
 
Milkrosoft

Milkrosoft

New member
I just installed this too and was really impressed... until I played Perfect Dark. I set the C buttons to the left joystick to allow me to strafe like in modern first person shooters. I was only able to move forward, backward, left and right. I was unable to move diagonally like I used to. I don't know if it's the new version of NRage's plugin or the XBCD drivers, but one of those is preventing the diagonal position of the joystick from recognizing the two primary direction buttons. Does anybody know how to fix this? Do I need to explain the problem better?
 
Tre

Tre

Oops. Died again.
I don't have experience in playing Perfect Dark (don't have it actually) but I would think that combining C-Left and C-Up would not product a Up-Left diagonal direction, even if you mapped to the analog stick. This would be because the C-Buttons are independantly mapped without intention of them being treated as a directional movement. But this is only being said from my limited experience outside of Perfect Dark.

Were you able to get "diagonal" movements with a previous version of N-Rage (like 1.83) with similar button mapping, or was this always the case?

Also, when you open up the "Game Controllers" option in "Control Panel" and test the axis of your joypad there, does it read the diagonals correctly? Have you gone through the configuration process?

And when you play other games with your analog stick mapped to the stick, does it give you diagonals? If not, then something is wrong with the way the controller is read (drivers, or plugin). If it is, then this supports the idea that C-Buttons can't be used together (without hitting the extreme) to produce a diagonal direction.
 
OP
M

Marfoo

New member
I noticed the same problem while playing the South Park game, but figured it out. Because the analog sticks are mapped as axis, you have to push them far enough out for it to register. When you go diagonally, neither axis fully registers. To fix this problem (haven't tried it out but theoretically should work if programmers put diagonal into Perfect Dark, which they most likely did) I would just use the D-pad for c-buttons (c-button movement isn't pressure sensitive anyway) and then use the modifiers to register POV HAT diagonals as two c buttons.
 
squall_leonhart

squall_leonhart

The Great Gunblade Wielder
Tre

an easy way to uninstall reg keys is to export the key from the registry and add a - before the key name (after the [)
 
Tre

Tre

Oops. Died again.
I never knew that! Question. Does it require that all fields with a bracket have you add a minus sign to remove all of it's components, or only the inintial bracket?

And I'm only assuming here, but do you only have to export the "default" registry entry only, and it will remove all of it's brothers and sisters in the registry file/folders?

Also... after saving the "new" registry entry, I just double click it like a file to have it remove the mastercopy like I would to install it in the first place?

Wow... so many questions. Heh.
 
squall_leonhart

squall_leonhart

The Great Gunblade Wielder
heres an example

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\OpenGL]

[HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\OpenGL\Debug]
"ShaderObjects"=dword:00000001

say you added that and want to remove it

simply add a - to the actual key then run it like a normal .reg file

Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\OpenGL]

[-HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\OpenGL\Debug]
"ShaderObjects"=dword:00000001

but :p not the place
 
Tre

Tre

Oops. Died again.
Still don't think I get it. Ah well. Heh, registry isn't my thing. And since this isn't quite the place, no worries. You could pm me a (from my standpoint) clearer explaination... because I still keep thinking "Okay, export the file. Give it a name when prompted. Edit the file. Add - to the after[ parts. Save it. Run it. Done!" for some reason. >_>
 
Tre

Tre

Oops. Died again.
Ah! Heh, darn I feel stupid sometimes. :) But now I have learned something useful.

Back on topic; I wonder if Milkrosoft has been able to get the diagonals working right...
 
Milkrosoft

Milkrosoft

New member
Tre said:
I don't have experience in playing Perfect Dark (don't have it actually) but I would think that combining C-Left and C-Up would not product a Up-Left diagonal direction, even if you mapped to the analog stick. This would be because the C-Buttons are independantly mapped without intention of them being treated as a directional movement. But this is only being said from my limited experience outside of Perfect Dark.

Were you able to get "diagonal" movements with a previous version of N-Rage (like 1.83) with similar button mapping, or was this always the case?

Also, when you open up the "Game Controllers" option in "Control Panel" and test the axis of your joypad there, does it read the diagonals correctly? Have you gone through the configuration process?

And when you play other games with your analog stick mapped to the stick, does it give you diagonals? If not, then something is wrong with the way the controller is read (drivers, or plugin). If it is, then this supports the idea that C-Buttons can't be used together (without hitting the extreme) to produce a diagonal direction.
Click to expand...

I was able to get diagonal movements with previous versions of N-Rage using the XBCD drivers so the problem is with the updated N-Rage plugin. The diagonals read correctly in the "game controllers" test.

Using V1.83, I was able to get rumble, and the L and R triggers registered properly using the XBCD drivers so I don't see the need for V 2.00. I am still having problems with the analog stick in all versions of N-Rage. For some reason, diagonal directions slow down and you come to a walk when you should be running. This is most obvious for me in the Zelda games. Is there a way to fix that?
 
Last edited:
You must log in or register to reply here.

Top