How about Nunchuck games, can you assign and use the 360 contoller for that too
(04-29-2010, 07:06 AM)Jaz808 Wrote: [ -> ]How about Nunchuck games, can you assign and use the 360 contoller for that too
Yes, just go to Wiimote Settings, then choose Nunchuk at Emulated Extension, then go to Button mapping and there it is.
(03-27-2010, 06:37 AM)flukeSG2 Wrote: [ -> ]Ok, I just downlaoded Dolphin yesterday and I got both my wireless 360 and wired to both work. Here is what I did.
1. I inactivated the Wiimotes, under the Wiimote tab.
2. GC Pad tab, if you are mapping your first controller make sure it's on Gamecube Pad 1 tab, from the drop down select which controller it is you are going to map.
3. I had some issues with the analog sticks, move them around to make sure they are properly working in all x and y positions. My Analog 2 gave me the most problems. I had to click the button next to "Right X-Axis" a few times until it came up with the number "4" and the "Right Y-Axis" then turned to number "3". You may have varying degree's of success with this, use whatever numbers work for you, I won't guarantee those 2 settings for me will work for you.
4. Left Trigger and Right Trigger, click the buttons and squeeze according triggers, again my settings came to Left Trigger "1000" and Right Trigger "1001"
5. Mapping your Buttons and D-Pad, pretty self explanatory, the GC uses ABXY just like xbox, makes it simple. for the Z button I used the "back" button.
6. Main Stick, drop down menu select analog 1. At the bottom you see "Semi" click the button and press down on your analog 1 stick, to assign it.
7. C-Stick, drop down menu select analog 2, again on the "Semi" button press down on the Analog 2 stick to assign it.
8. Triggers, drop down menu select triggers. Now I tried to assign the L and R buttons to my triggers to no success. HOWEVER, they still work, I believe because we've mapped them above already in the "Analog Axes and Trigger" area. The Semi-L should be your LB button and the Semi-R your RB button on your controller.
P.S. I just realized for games like Super Mario Galaxy, you will have to enable the Wiimotes and map the keys in that area, as that game requires the Wiimote.
That is what I did and I have full control using my Xbox 360 Controller.
Let me know if this helps at all.
I followed all your steps exactly. In fact I did most of those already on my own like fixing the axis and the button mapping.
I even made sure the Wii mote was inactive... but the game when it runs doesn't receive any input from my 360 controller.
I'm using Revision 5475 and my XBOX 360 controller isn't working at all.
I previously had 4737 and it would work with my 360 controller but incorrectly plus I had no way of mapping the controls to it.
(06-05-2010, 06:08 PM)meshblorg Wrote: [ -> ]I followed all your steps exactly. In fact I did most of those already on my own like fixing the axis and the button mapping.
I even made sure the Wii mote was inactive... but the game when it runs doesn't receive any input from my 360 controller.
I'm using Revision 5475 and my XBOX 360 controller isn't working at all.
I previously had 4737 and it would work with my 360 controller but incorrectly plus I had no way of mapping the controls to it.
Why do you need to make the wiimote inactive
You could also try the gcpad new plugin.
(06-05-2010, 06:53 PM)Billiard26 Wrote: [ -> ] (06-05-2010, 06:08 PM)meshblorg Wrote: [ -> ]I followed all your steps exactly. In fact I did most of those already on my own like fixing the axis and the button mapping.
I even made sure the Wii mote was inactive... but the game when it runs doesn't receive any input from my 360 controller.
I'm using Revision 5475 and my XBOX 360 controller isn't working at all.
I previously had 4737 and it would work with my 360 controller but incorrectly plus I had no way of mapping the controls to it.
Why do you need to make the wiimote inactive
You could also try the gcpad new plugin.
I have it tried the GCPad new plugin.
I can set it up correctly in the controller setup but as soon as I start the game up... doesn't respond at all!
(03-27-2010, 02:58 AM)Xtreme2damax Wrote: [ -> ]Well my post was little over two months ago, the KB/X360 plugin wasn't removed from the SVN yet. I still include an build of the plugin in my Dolphin builds, however the plugin is from before it was removed from the SVN and likely won't be updated further.
Can't its auto-mapping functionality be merged onto GCPad New somehow?
I still use KB/X360 plugin because of it, in GCPad New it's a trouble when it comes to map the L & R analogs.
(06-07-2010, 12:08 AM)El Buga Wrote: [ -> ]I still use KB/X360 plugin because of it, in GCPad New it's a trouble when it comes to map the L & R analogs.
How is it "a trouble"?
Just map your left trigger to "L" and "L-Analog" and right trigger to "R" and "R-Analog". Then you will have the exact functionality of the KB/X360 plugin.
GCPad New can do everything the KB/360 plugin can do, in addition to being customizable and working with regular DInput devices.
(06-07-2010, 05:49 AM)Billiard26 Wrote: [ -> ]How is it "a trouble"?
Just map your left trigger to "L" and "L-Analog" and right trigger to "R" and "R-Analog". Then you will have the exact functionality of the KB/X360 plugin.
GCPad New can do everything the KB/360 plugin can do, in addition to being customizable and working with regular DInput devices.
Well, I had trouble configuring the L & R analogs in a past revision. Most accurately, 5579. Analogs were not recognized properly... Don't know if it's fixed, apparently it is now in 5629. Although now I needed to click two times in every option for the plug-in to let me press the right joystick button to configure it.
(06-07-2010, 09:02 AM)El Buga Wrote: [ -> ]Well, I had trouble configuring the L & R analogs in a past revision. Most accurately, 5579. Analogs were not recognized properly... Don't know if it's fixed, apparently it is now in 5629. Although now I needed to click two times in every option for the plug-in to let me press the right joystick button to configure it.
Xbox 360 controller input hasn't changed since the initial commit of the new plugin to the svn. I don't know why you were having trouble before.
You need to click what two times to do what exactly?