Emulator

Bug got entered a little prematurely...pressed enter to add a line break and
since "Save Changes" is highlighted by default...well there you go. Title should
be "Rumble does not work on the 64 bit version Njoy 0.3 plugin" - or something like
that.

I'm reopening this as I feel it was closed out as "invalid" for an invalid reason.
The bug was confirmed by mikey as not an issue with the drivers (see above). The
plugin just is not working correctly. I think this is a bug with the plugin and I
should not be forced to change to a crappy driver, with no config utility (like
XBCD) and only support for games made in the last few years. Sorry, I like playing
games from more than just 2005 and on. And there's no need to be rude! Argh!! :O

This is obviously a issue with this particular input plugin and should be fixed
properly and not just forced to switch out my gamepad's drivers and input plugins.
That's called a workaround, not a fix. Can some other people comment on this and
confirm please.

It's not the driver, I have the same problem with standard Microsoft drivers. As for
as why I don't use the xInput pad plugin, with my crappy madcatz controller pushing
completely in one direction causes it to go to the opposite direction. There doesn't
seem to be any options for me to change with that plugin.

Thanks Mikey! Hopefully this can go on the todo list and be resolved someday!

I take it no news on this? Any ideas what it could be? Can we get this confirmed
and "accepted". I hate having to chose between rumble and 64 bit speed. :(

well, rumble works for me with 64bit dolphin...but only with Logitech Rumblepad 2.
Xbox360controller stays still...but I think it wasn't different when I was using
Dolphin 32bit shrug

Still no change for me - just tried it with a clean install.

Njoy + 64 bit + 360 controller (directinput or Xinput drivers) = No rumble.

I wonder if this ever worked. There's a lot of work being done on input lately -
maybe this one will make the cut!

why would you use nJoy with a x360 pad when there's a plugin dedicated to x360 pads ?
also, nJoy uses SDL which uses DirectInput and you can't access the rumble feature of
a x360 pad through DirectInput (at least with the normal XInput driver)

I'm looking to use Njoy with my X360 w/ directinput drivers (XBCD).

The 32 bit version works fine (along with all my other emus and PC games) - so
there's just something wrong with the 64 bit version of Dolphin, the Njoy.dll or the
SDL included.

I mainly use XBCD for the 360 pad (as everyone should)- you get DirectInput, plus
now it emulates Xinput so you get the best of both worlds.

I also think the Njoy plugin is better and you can do more with it than
the "Keyboard/x360 pad" plugin.

Still occuring in 4869. I do hope this can be resolved soon so users can use the
64bit version with rumble. F-Zero is calling me but that's a game where rumble is
really needed to play. Hopefully, a simple fix. Let me know how I can help!

i feel bad closing this a second time. maybe someone else will.

Please don't close this. Please fix it. Can't be an issue with both available sets
of drivers for the most popular pad around. Remember what Mikey said above:

"It's not the driver, I have the same problem with standard Microsoft drivers. As
for as why I don't use the xInput pad plugin, with my crappy madcatz controller
pushing completely in one direction causes it to go to the opposite direction.
There doesn't seem to be any options for me to change with that plugin."

Even if it is, perhaps a workaround...still think this is a Dolphin issue.

It doesn't make too much sense to use X360pad with Njoy. As X360pad should always use
PadSimple.
When you are meant to wear pants than skirts, you just follow the rule.

Well, I still believe this is a solvable issue within Dolphin. Again, I use XBCD
drivers - they are the best and DirectInput. So I can't use PadSimple when using
them. I can use Njoy 32 bit no problem, just not 64 bit. I like Njoy's UI and
functionality more than PadSimple also.

Can you guys just do a mini investigation to see what might cause this? Is it the 64
bit SDL maybe? That message exist in the code, when and why does that message appear?

Does anyone have this issue or know why I'm experiencing this? Is it probably the
64bit SDL.dll file? Are there other ones out there that I can try or is that
probably not it? What triggers that error message exactly? Any help would be greatly
appreciated!

What message?

BTW: I think now rumble works in x64 with GCPad_Plugin. Try out.

Hey, thanks sincerely for keeping an eye on this issue. Still not fixed for me in
build 4963. Here's the message I get. Happens when launching a GC game which is then
followed immediately by a crash - 100%, always. For the Wii games, I get the same
result but not at boot but rather when it tries to rumble the (emulated)
wiimote....and then it crashes also. Occurs with the new GC plugin, Njoy, Wiimote
plugins.

No matter what, stability issues shouldn't be occuring here. This is with panic
handlers OFF.

Again, works fine on the 32 bit version. My controller (and rumble) work perfectly
on all the other 10+ emulators as well as my PC games. Numerous 32 bit and 64 bit
apps work fine. Its trully only the 64 bit version of Dolphin.

Happens with all input plugins which maybe points to that 64bit verion of the SDL
file being the issue? I can't find any others on the internet, so I guess someone on
the Dolphin team modded the 32 bit one?

I wish someone (other than Mikey here)would comment!! Are there others that have
issues with rumble on the 64bit version?? Please speak up!

If it is only me, why am I getting these messages? What exactly in the code is
supposed to populate this error message?

It is an issue of DInput x64.

Issue 1977 has been merged into this issue.

This needs someone who has x64 OS installed to debug. I've only got 32bit OS.

this is because the implementation of rumble is just a big hack on top of SDL, I
tried to "fix" it by using the new (and flawed) "SDL Haptic" API in SDL 1.3 but the
lack of setting and their wish of being ultra simple just killed it as it turned out
even the sample didn't work on my pad...
(So the best way to make it work for everyone would be to have a DirectInput pad
plugin hmm...)

But DirectInput doesn't support Linux I guess?
Currently only Rumble employs DInput API so basic pad funtions are still supported on
Linux since we use SDL API.

wespipes69. I have x64OS I had this issue with XBCD drivers only. went back to the
standard drivers updated them and no problem with rumble. I hope it gets resolved for
XBCD though.

@btja: Hmm,that might be the case now, but nonetheless, XBCD=DInput while standard
drivers=XInput. So I would expect a difference between the 2, though you are the
first that I've heard that's confirmed rumble on x64 with M$ drivers.

I do hope this can be resolved sometime though.Good luck devs and let me know if
there's anything else I can provide/test!!

http://www.libsdl.org/tmp/SDL-1.3-docs/SDL__haptic_8h.html
seems like capable enough API, what is it missing?

Issue 1288 has been merged into this issue.

Works fine now on all plugins. I'm using XBCD 2.7 which has a fix for rumble on 64
bit apps. So I think we're all good here!