I cannot get this to work at all.

[chuchulvc]

I'm running 64 bit windows and I cannot seem to get this to run. I've tried to install pgu and that doesn't work, I currently have version 2.7 of python and it doesn't seem to work or see any of the files of padpyght.

Thanks! And hellllp!!!

[chuchulvc]

Nevermind! I had to install pygame. but every time I press down the left trigger it disappears.

[lifning]

Glad you were able to work that out! As for your L-trigger problem, what physical controller are you using, and what skin are you using? Is there any console log output for the crash?

[chuchulvc]

I'm using a retrobit GameCube remake control with the ds3 tool. it doesn't read the L + R and Z buttons.

I'm using the GameCube skin that came with it. is there a better one?

On May 19, 2014, at 3:51 PM, Darren notifications@github.com wrote:

Glad you were able to work that out! As for your L-trigger problem, what physical controller are you using, and what skin are you using? Is there any console log output for the crash?

\ Reply to this email directly or view it on GitHub.

[lifning]

Perhaps, but it hasn't been written yet :) I don't have a retrobit GCN pad myself, but perhaps you can edit the skin.ini to match the button and axis mappings to what they should be. (Refer to: https://github.com/lifning/padpyght/issues/3#issuecomment-38241367 where Mayflash adapter support was added similarly) If that's a tall order, if you can tell me which numerical buttons and axes each button corresponds to, I can try to write it up myself; it'll just take some more time to go back and forth to verify.

[chuchulvc]

wow thank you! I will write down the button numbers when I get home. having a controller display for my resident evil speedruns is gonna make it more interesting :)

On May 19, 2014, at 4:09 PM, Darren notifications@github.com wrote:

Perhaps, but it hasn't been written yet :) I don't have a retrobit GCN pad myself, but perhaps you can edit the skin.ini to match the button and axis mappings to what they should be. (Refer to: #3 (comment) where Mayflash adapter support was added similarly) If that's a tall order, if you can tell me which numerical buttons and axes each button corresponds to, I can try to write it up myself; it'll just take some more time to go back and forth to verify.

\ Reply to this email directly or view it on GitHub.

[chuchulvc]

left trigger is button 5 and right trigger is button 6.

the z button doesnt work either and makes the left trigger disappear. the Z button on the gamecube is the Z-axis.

also the C-button is mirrored and kind of messed up

this is down -C http://gyazo.com/691a1dc13c22af4f74536fc3776a1ba0

up C http://gyazo.com/1a1733efc48f501d34b927fcf31ccbf3

left C * http://gyazo.com/51cf16464dbbbe550c0a5722d8b7fd62 http://gyazo.com/51cf16464dbbbe550c0a5722d8b7fd62*

right C http://gyazo.com/8bfaac0ee1959acc19bd25e921086c05

let me know what I can do in the INI to fix this ! thank you sooooo much

On Mon, May 19, 2014 at 4:25 PM, James Laurence jamestakeabow@gmail.comwrote:

wow thank you! I will write down the button numbers when I get home. having a controller display for my resident evil speedruns is gonna make it more interesting :)

On May 19, 2014, at 4:09 PM, Darren notifications@github.com wrote:

Perhaps, but it hasn't been written yet :) I don't have a retrobit GCN pad myself, but perhaps you can edit the skin.ini to match the button and axis mappings to what they should be. (Refer to: #3 (comment)https://github.com/lifning/padpyght/issues/3#issuecomment-38241367where Mayflash adapter support was added similarly) If that's a tall order, if you can tell me which numerical buttons and axes each button corresponds to, I can try to write it up myself; it'll just take some more time to go back and forth to verify.

— Reply to this email directly or view it on GitHubhttps://github.com/lifning/padpyght/issues/5#issuecomment-43569565 .

[lifning]

That's a very strange behavior... I would expect the L and R triggers to be the Z axis rather than buttons, seeing as they are analog triggers. And I would expect the Z button to be a... button, rather than an axis. Is this a quirk of the "DS3 tool" you mentioned?

Normally the L and R sprites in the skin get moved along with the analog motion of the triggers themselves, so I haven't implemented a "pressed" color for L and R. Your Z button is making the L sprite seem to disappear because pressing it is making the Z-axis go from "all the way up" to "all the way down" in one frame.

For the C-stick, try changing the order of the Axes under [Stick2].

[chuchulvc]

thanks! I'll try that for the cstick. ds3 tool is the driver that allows me to use my gamecube controller as a Xbox controller clone. that has to be the issue maybe? maybe I'll make it a ps2 clone and try that

thanks james

On May 19, 2014, at 8:19 PM, Darren notifications@github.com wrote:

That's a very strange behavior... I would expect the L and R triggers to be the Z axis rather than buttons, seeing as they are analog triggers. And I would expect the Z button to be a... button, rather than an axis. Is this a quirk of the "DS3 tool" you mentioned?

Normally the L and R sprites in the skin get moved along with the analog motion of the triggers themselves, so I haven't implemented a "pressed" color for L and R. Your Z button is making the L sprite seem to disappear because pressing it is making the Z-axis go from "all the way up" to "all the way down" in one frame.

For the C-stick, try changing the order of the Axes under [Stick2].

\ Reply to this email directly or view it on GitHub.

[lifning]

Is it possible to use this device as a joypad without ds3 translating it to Xbox/PlayStation? We could make a more direct mapping, if so.

On May 19, 2014 9:28:31 PM PDT, chuchulvc notifications@github.com wrote:

thanks! I'll try that for the cstick. ds3 tool is the driver that allows me to use my gamecube controller as a Xbox controller clone. that has to be the issue maybe? maybe I'll make it a ps2 clone and try that

thanks james

On May 19, 2014, at 8:19 PM, Darren notifications@github.com wrote:

That's a very strange behavior... I would expect the L and R triggers to be the Z axis rather than buttons, seeing as they are analog triggers. And I would expect the Z button to be a... button, rather than an axis. Is this a quirk of the "DS3 tool" you mentioned?

Normally the L and R sprites in the skin get moved along with the analog motion of the triggers themselves, so I haven't implemented a "pressed" color for L and R. Your Z button is making the L sprite seem to disappear because pressing it is making the Z-axis go from "all the way up" to "all the way down" in one frame.

For the C-stick, try changing the order of the Axes under [Stick2].

\ Reply to this email directly or view it on GitHub.

---

Reply to this email directly or view it on GitHub: https://github.com/lifning/padpyght/issues/5#issuecomment-43585384

Sent from my Android device with K-9 Mail. Please excuse my brevity.

[chuchulvc]

Hmmm, I've always used it that way. It's the only way it works in the PC versions of Biohazard 2+3 and Dino Crisis. What are the alternatives?

On Mon, May 19, 2014 at 10:49 PM, Darren notifications@github.com wrote:

Is it possible to use this device as a joypad without ds3 translating it to Xbox/PlayStation? We could make a more direct mapping, if so.

On May 19, 2014 9:28:31 PM PDT, chuchulvc notifications@github.com wrote:

thanks! I'll try that for the cstick. ds3 tool is the driver that allows me to use my gamecube controller as a Xbox controller clone. that has to be the issue maybe? maybe I'll make it a ps2 clone and try that

thanks james

On May 19, 2014, at 8:19 PM, Darren notifications@github.com wrote:

That's a very strange behavior... I would expect the L and R triggers to be the Z axis rather than buttons, seeing as they are analog triggers. And I would expect the Z button to be a... button, rather than an axis. Is this a quirk of the "DS3 tool" you mentioned?

Normally the L and R sprites in the skin get moved along with the analog motion of the triggers themselves, so I haven't implemented a "pressed" color for L and R. Your Z button is making the L sprite seem to disappear because pressing it is making the Z-axis go from "all the way up" to "all the way down" in one frame.

For the C-stick, try changing the order of the Axes under [Stick2].

\ Reply to this email directly or view it on GitHub.

---

Reply to this email directly or view it on GitHub: https://github.com/lifning/padpyght/issues/5#issuecomment-43585384

Sent from my Android device with K-9 Mail. Please excuse my brevity.

— Reply to this email directly or view it on GitHubhttps://github.com/lifning/padpyght/issues/5#issuecomment-43588601 .

[chuchulvc]

Hmmm, Which .ini do I edit?

On Tue, May 20, 2014 at 11:38 AM, james laurence jamestakeabow@gmail.comwrote:

Hmmm, I've always used it that way. It's the only way it works in the PC versions of Biohazard 2+3 and Dino Crisis. What are the alternatives?

On Mon, May 19, 2014 at 10:49 PM, Darren notifications@github.com wrote:

Is it possible to use this device as a joypad without ds3 translating it to Xbox/PlayStation? We could make a more direct mapping, if so.

On May 19, 2014 9:28:31 PM PDT, chuchulvc notifications@github.com wrote:

thanks! I'll try that for the cstick. ds3 tool is the driver that allows me to use my gamecube controller as a Xbox controller clone. that has to be the issue maybe? maybe I'll make it a ps2 clone and try that

thanks james

On May 19, 2014, at 8:19 PM, Darren notifications@github.com wrote:

That's a very strange behavior... I would expect the L and R triggers to be the Z axis rather than buttons, seeing as they are analog triggers. And I would expect the Z button to be a... button, rather than an axis. Is this a quirk of the "DS3 tool" you mentioned?

Normally the L and R sprites in the skin get moved along with the analog motion of the triggers themselves, so I haven't implemented a "pressed" color for L and R. Your Z button is making the L sprite seem to disappear because pressing it is making the Z-axis go from "all the way up" to "all the way down" in one frame.

For the C-stick, try changing the order of the Axes under [Stick2].

\ Reply to this email directly or view it on GitHub.

---

Reply to this email directly or view it on GitHub: https://github.com/lifning/padpyght/issues/5#issuecomment-43585384

Sent from my Android device with K-9 Mail. Please excuse my brevity.

— Reply to this email directly or view it on GitHubhttps://github.com/lifning/padpyght/issues/5#issuecomment-43588601 .

[lifning]

Should be gamecube/skin.ini for the one that corresponds to the Xbox 360 pad mappings.

Is the ds3 tool configurable? I get the feeling that the "proper" way to fix this for your use case is to use the X360 layout if that's what you need it to behave like anyway, but there's clearly a difference between how my X360 pad works and how this tool is representing one.

On May 20, 2014 3:32:43 PM PDT, chuchulvc notifications@github.com wrote:

Hmmm, Which .ini do I edit?

On Tue, May 20, 2014 at 11:38 AM, james laurence jamestakeabow@gmail.comwrote:

Hmmm, I've always used it that way. It's the only way it works in the PC versions of Biohazard 2+3 and Dino Crisis. What are the alternatives?

On Mon, May 19, 2014 at 10:49 PM, Darren notifications@github.com wrote:

Is it possible to use this device as a joypad without ds3 translating it to Xbox/PlayStation? We could make a more direct mapping, if so.

On May 19, 2014 9:28:31 PM PDT, chuchulvc notifications@github.com wrote:

thanks! I'll try that for the cstick. ds3 tool is the driver that allows me to use my gamecube controller as a Xbox controller clone. that has to be the issue maybe? maybe I'll make it a ps2 clone and try that

thanks james

On May 19, 2014, at 8:19 PM, Darren notifications@github.com wrote:

That's a very strange behavior... I would expect the L and R triggers to be the Z axis rather than buttons, seeing as they are analog triggers. And I would expect the Z button to be a... button, rather than an axis. Is this a quirk of the "DS3 tool" you mentioned?

Normally the L and R sprites in the skin get moved along with the analog motion of the triggers themselves, so I haven't implemented a "pressed" color for L and R. Your Z button is making the L sprite seem to disappear because pressing it is making the Z-axis go from "all the way up" to "all the way down" in one frame.

For the C-stick, try changing the order of the Axes under [Stick2].

\ Reply to this email directly or view it on GitHub.

---

Reply to this email directly or view it on GitHub: https://github.com/lifning/padpyght/issues/5#issuecomment-43585384

Sent from my Android device with K-9 Mail. Please excuse my brevity.

— Reply to this email directly or view it on GitHubhttps://github.com/lifning/padpyght/issues/5#issuecomment-43588601 .

---

Reply to this email directly or view it on GitHub: https://github.com/lifning/padpyght/issues/5#issuecomment-43692045

Sent from my Android device with K-9 Mail. Please excuse my brevity.

[chuchulvc]

you can make your own layouts in ds3 tool but the xbox pad emu for the gc clone is the xbox pad layout/emu??

doesnt make sense rly

On Tue, May 20, 2014 at 3:42 PM, Darren notifications@github.com wrote:

Should be gamecube/skin.ini for the one that corresponds to the Xbox 360 pad mappings.

Is the ds3 tool configurable? I get the feeling that the "proper" way to fix this for your use case is to use the X360 layout if that's what you need it to behave like anyway, but there's clearly a difference between how my X360 pad works and how this tool is representing one.

On May 20, 2014 3:32:43 PM PDT, chuchulvc notifications@github.com wrote:

Hmmm, Which .ini do I edit?

On Tue, May 20, 2014 at 11:38 AM, james laurence jamestakeabow@gmail.comwrote:

Hmmm, I've always used it that way. It's the only way it works in the PC versions of Biohazard 2+3 and Dino Crisis. What are the alternatives?

On Mon, May 19, 2014 at 10:49 PM, Darren notifications@github.com wrote:

Is it possible to use this device as a joypad without ds3 translating it to Xbox/PlayStation? We could make a more direct mapping, if so.

On May 19, 2014 9:28:31 PM PDT, chuchulvc notifications@github.com wrote:

thanks! I'll try that for the cstick. ds3 tool is the driver that allows me to use my gamecube controller as a Xbox controller clone. that has to be the issue maybe? maybe I'll make it a ps2 clone and try that

thanks james

On May 19, 2014, at 8:19 PM, Darren notifications@github.com wrote:

That's a very strange behavior... I would expect the L and R triggers to be the Z axis rather than buttons, seeing as they are analog triggers. And I would expect the Z button to be a... button, rather than an axis. Is this a quirk of the "DS3 tool" you mentioned?

Normally the L and R sprites in the skin get moved along with the analog motion of the triggers themselves, so I haven't implemented a "pressed" color for L and R. Your Z button is making the L sprite seem to disappear because pressing it is making the Z-axis go from "all the way up" to "all the way down" in one frame.

For the C-stick, try changing the order of the Axes under [Stick2].

\ Reply to this email directly or view it on GitHub.

---

Reply to this email directly or view it on GitHub: https://github.com/lifning/padpyght/issues/5#issuecomment-43585384

Sent from my Android device with K-9 Mail. Please excuse my brevity.

— Reply to this email directly or view it on GitHub<https://github.com/lifning/padpyght/issues/5#issuecomment-43588601

.

---

Reply to this email directly or view it on GitHub: https://github.com/lifning/padpyght/issues/5#issuecomment-43692045

Sent from my Android device with K-9 Mail. Please excuse my brevity.

— Reply to this email directly or view it on GitHubhttps://github.com/lifning/padpyght/issues/5#issuecomment-43692815 .

[chuchulvc]

Is there an easy way to switch skins? I want to use the PS skin

On Tue, May 20, 2014 at 3:47 PM, james laurence jamestakeabow@gmail.comwrote:

you can make your own layouts in ds3 tool but the xbox pad emu for the gc clone is the xbox pad layout/emu??

doesnt make sense rly

On Tue, May 20, 2014 at 3:42 PM, Darren notifications@github.com wrote:

Should be gamecube/skin.ini for the one that corresponds to the Xbox 360 pad mappings.

Is the ds3 tool configurable? I get the feeling that the "proper" way to fix this for your use case is to use the X360 layout if that's what you need it to behave like anyway, but there's clearly a difference between how my X360 pad works and how this tool is representing one.

On May 20, 2014 3:32:43 PM PDT, chuchulvc notifications@github.com wrote:

Hmmm, Which .ini do I edit?

On Tue, May 20, 2014 at 11:38 AM, james laurence jamestakeabow@gmail.comwrote:

Hmmm, I've always used it that way. It's the only way it works in the PC versions of Biohazard 2+3 and Dino Crisis. What are the alternatives?

On Mon, May 19, 2014 at 10:49 PM, Darren notifications@github.com wrote:

Is it possible to use this device as a joypad without ds3 translating it to Xbox/PlayStation? We could make a more direct mapping, if so.

On May 19, 2014 9:28:31 PM PDT, chuchulvc notifications@github.com wrote:

thanks! I'll try that for the cstick. ds3 tool is the driver that allows me to use my gamecube controller as a Xbox controller clone. that has to be the issue maybe? maybe I'll make it a ps2 clone and try that

thanks james

On May 19, 2014, at 8:19 PM, Darren notifications@github.com wrote:

That's a very strange behavior... I would expect the L and R triggers to be the Z axis rather than buttons, seeing as they are analog triggers. And I would expect the Z button to be a... button, rather than an axis. Is this a quirk of the "DS3 tool" you mentioned?

Normally the L and R sprites in the skin get moved along with the analog motion of the triggers themselves, so I haven't implemented a "pressed" color for L and R. Your Z button is making the L sprite seem to disappear because pressing it is making the Z-axis go from "all the way up" to "all the way down" in one frame.

For the C-stick, try changing the order of the Axes under [Stick2].

\ Reply to this email directly or view it on GitHub.

---

Reply to this email directly or view it on GitHub: https://github.com/lifning/padpyght/issues/5#issuecomment-43585384

Sent from my Android device with K-9 Mail. Please excuse my brevity.

— Reply to this email directly or view it on GitHub< https://github.com/lifning/padpyght/issues/5#issuecomment-43588601>

.

---

Reply to this email directly or view it on GitHub: https://github.com/lifning/padpyght/issues/5#issuecomment-43692045

Sent from my Android device with K-9 Mail. Please excuse my brevity.

— Reply to this email directly or view it on GitHubhttps://github.com/lifning/padpyght/issues/5#issuecomment-43692815 .

[lifning]

Yep, you can choose the "playstation" skin from the PGU menu, or you can run "python padpyght.py playstation"

On Tue, May 20, 2014 at 10:22 PM, chuchulvc notifications@github.comwrote:

Is there an easy way to switch skins? I want to use the PS skin

On Tue, May 20, 2014 at 3:47 PM, james laurence jamestakeabow@gmail.comwrote:

you can make your own layouts in ds3 tool but the xbox pad emu for the gc clone is the xbox pad layout/emu??

doesnt make sense rly

On Tue, May 20, 2014 at 3:42 PM, Darren notifications@github.com wrote:

Should be gamecube/skin.ini for the one that corresponds to the Xbox 360 pad mappings.

Is the ds3 tool configurable? I get the feeling that the "proper" way to fix this for your use case is to use the X360 layout if that's what you need it to behave like anyway, but there's clearly a difference between how my X360 pad works and how this tool is representing one.

On May 20, 2014 3:32:43 PM PDT, chuchulvc notifications@github.com wrote:

Hmmm, Which .ini do I edit?

On Tue, May 20, 2014 at 11:38 AM, james laurence jamestakeabow@gmail.comwrote:

Hmmm, I've always used it that way. It's the only way it works in the PC versions of Biohazard 2+3 and Dino Crisis. What are the alternatives?

On Mon, May 19, 2014 at 10:49 PM, Darren notifications@github.com wrote:

Is it possible to use this device as a joypad without ds3 translating it to Xbox/PlayStation? We could make a more direct mapping, if so.

On May 19, 2014 9:28:31 PM PDT, chuchulvc notifications@github.com

wrote:

thanks! I'll try that for the cstick. ds3 tool is the driver that allows me to use my gamecube controller as a Xbox controller clone. that has to be the issue maybe? maybe I'll make it a ps2 clone and try that

thanks james

On May 19, 2014, at 8:19 PM, Darren notifications@github.com wrote:

That's a very strange behavior... I would expect the L and R triggers to be the Z axis rather than buttons, seeing as they are analog triggers. And I would expect the Z button to be a... button, rather than an axis. Is this a quirk of the "DS3 tool" you mentioned?

Normally the L and R sprites in the skin get moved along with the analog motion of the triggers themselves, so I haven't implemented a "pressed" color for L and R. Your Z button is making the L sprite seem to disappear because pressing it is making the Z-axis go from "all the way up" to "all the way down" in one frame.

For the C-stick, try changing the order of the Axes under [Stick2].

\ Reply to this email directly or view it on GitHub.

---

Reply to this email directly or view it on GitHub: https://github.com/lifning/padpyght/issues/5#issuecomment-43585384

Sent from my Android device with K-9 Mail. Please excuse my brevity.

— Reply to this email directly or view it on GitHub< https://github.com/lifning/padpyght/issues/5#issuecomment-43588601>

.

---

Reply to this email directly or view it on GitHub: https://github.com/lifning/padpyght/issues/5#issuecomment-43692045

Sent from my Android device with K-9 Mail. Please excuse my brevity.

— Reply to this email directly or view it on GitHub< https://github.com/lifning/padpyght/issues/5#issuecomment-43692815> .

— Reply to this email directly or view it on GitHubhttps://github.com/lifning/padpyght/issues/5#issuecomment-43713303 .

[gersonberger]

Is it possible to map a 2 axis control stick to four buttons, e.g. the four buttons of an N64 controller?

[lifning]

@gersonberger That's not supported yet, but would be an interesting feature to add.

[chuchulvc]

anyway to get this working with the raphnet adaptor? I see the ini but dunno how to make it work

On Mar 22, 2015, at 11:33 AM, Darren notifications@github.com wrote:

@gersonberger That's not supported yet, but would be an interesting feature to add.

\ Reply to this email directly or view it on GitHub.

[lifning]

Should be as simple as python padpyght.py gamecube/skin-raphnet.ini (or with the pgu gui, selecting the "raphnet GC/N64_USB" joypad and "gamecube (raphnet)" skin)