GCPad Issue

[YoD]

Hello guys,

I have an issue with the GCPad settings. I am using:
- r-6122
- PS3 controller via WinDS3

When I open the GCPad settings, I see my PS3 controller as a SDL pad and as a DInput pad. If I select the DInput one, nothing works, but if I select the SDL one, everything works except the Y-axis of the right analog stick. Everything else is recognized.

Everything works fine in 2.0, where I can use the DInput without any problem and all the controls work fine.

Anyone else is having this issue?

Also, I can't change the plugin for the GCPad New, is this because the .dll has been built into the .exe or can I just change the .dll for the old one? If so, where can I find it? It's not in the /plugins directory.

Thanks!

[Billiard26]

Like I said in my reply to your other post, Dolphin no longer uses pad plugins. GCPad New has been merged into Dolphin.

Not even the buttons work when using DInput?
If you right click an input detection button on the pad config dialog, does it list all of your ps3 controller's inputs? (Button 0-XX, Axis XX...)

I suppose you could try clicking the "Refresh" button, dunno.

[YoD]

(08-25-2010, 12:14 PM)Billiard26 Wrote: Like I said in my reply to your other post, Dolphin no longer uses pad plugins. GCPad New has been merged into Dolphin.

Not even the buttons work when using DInput?
If you right click an input detection button on the pad config dialog, does it list all of your ps3 controller's inputs? (Button 0-XX, Axis XX...)

I suppose you could try clicking the "Refresh" button, dunno.

Sorry about the double post, I will remember that in the future

When I use DInput, none of the buttons work. They do in GCPad New from 2.0 though. I tried clicking refresh, but it didn't help.

   

I tried updating my DX runtime files (they were already up to date) and my VC++ runtime files as well, but with the same results.

Best regards

[YoD]

Any clue about what was changed between now and the 2.0 release for this plugin as far as DirectInput goes?

Thanks!

[Billiard26]

Only thing I can think of is that it now prefers buffered data over polled data, but it should fall back to polled data if the device requires it.
Which drivers are you using with your ps3 controller?

[YoD]

(08-28-2010, 05:13 AM)Billiard26 Wrote: Only thing I can think of is that it now prefers buffered data over polled data, but it should fall back to polled data if the device requires it.
Which drivers are you using with your ps3 controller?

It's WinDS3, which acts as a native gamepad and uses the freebt driver for the bluetooth stack.

Thanks!

[Billiard26]

Revision 5619 had the switch from polled to buffered data.
You could check if r5619 works and r5618 doesn't to see if that is the issue.

[YoD]

(08-28-2010, 05:55 AM)Billiard26 Wrote: Revision 5619 had the switch from polled to buffered data.
You could check if r5619 works and r5618 doesn't to see if that is the issue.

Hello,

That's exactly what it is! I tried revision 5613 and in the dropdown I could only see the DInput controller. And it worked perfectly for all controls.

Then I tried 5628 and would see both DInput and SDL controller. If I picked the DInut one, no control would respond and the SL one would work, but not with the Y axis of the right analog stick.

Do you think you could switch back the polled data?

Thanks!

[Billiard26]

I'd rather not switch back to polled data. Some other devices don't work well with it.
I'd rather figure out a better way to check that your device doesn't support buffered data to fall back to polling.

Can you compile code if I give you a patch to test some things, or do I need to compile it for you?
If the latter, x64 or x86?

Can you come on the dolphin irc channel? Forums are slow.

[Billiard26]

Give r6143 a try. I made some changes to the DInput stuff.