Modded Gamecube controllers triggers not being recognized

[McDonald's in the Pentagon]

TL;DR - I had the springs cut to half on my shoulder buttons so the travel distance is lower. The game won't recognize them anymore.

I've been really enjoying the game despite not being able to wavedash and I KNOW I'd love it even more if I could. Only issue is that the game just isn't reading my trigger's presses.

I had gotten my triggers modded at a smash tournament so the spring is basically like half it's size so the travel distance is significantly less. I had this issue with Rivals of Aether as well but with that game, in a match and in menus the game still recognizes it, just not in button remapping. So I just use a spare GCN controller to map my buttons but that controller has issues with so I don't ever use it.

However, in this game, my controller isn't being recognized inside the game either so I'm unable to press the break buttons unless I remap them to another button.

Does anyone know how to fix this? I use the Nintendo licensed GCN adapter for the Wii U with a normal GCN controller aside from the modded shoulder button. Do I have to use a secondary program like vJoy or joytoKey?

[Coda]

So the gamecube controller triggers have 2 separate inputs: an analog slider input, that reads incrementally from 0%-100%; and digital press, that reads as either ON or OFF.

If you cut the spring and it doesn't work. that would be because this game seems to only register the analog slider input and is not traveling enough distance to register the threshold for input. For example, if the game were to register the trigger once the slider reaches, say, 60%, the game will register a trigger input when the slider has traveled 60% units

So THEN say your triggers sit lower at about halfway, essentially resting at 50%; when the slider travels from 50% to 100% it has only traveled 50% units, therefor not registering a successful input, being off by 10% in this example.

the best solution would be to get the wonderful developer, WILLS, to add a digital trigger press input to register as intended. :)

a quick, but annoying, solution... every time right before you plug in the controller, pull the triggers up to simulate a normal trigger resting height, then let it drop to, and hopefully it doesn't yet register at the current resting height. warning, the trigger will be sensitive and may register very easily.

a more involved solution could be to lightly stretch the trigger spring to allow the trigger to sit a bit taller and hopefully registers an input when fully pressing.
(all you need is a triwing and phillips screwdrivers to open the controller. AND WHEN YOU DO, open upside down, remove the back shell and leave the front half alone, again leave the frontside laying buttonside down. then to access the trigger springs, you need a fairly small, size 00, phillips screwdriver. careful not to strip the delicate screws. apply pressure and be as perfectly straight and perpendicular as you can. it helps)

[McDonald's in the Pentagon]

Origineel geplaatst door Coda:

So the gamecube controller triggers have 2 separate inputs: an analog slider input, that reads incrementally from 0%-100%; and digital press, that reads as either ON or OFF.

If you cut the spring and it doesn't work. that would be because this game seems to only register the analog slider input and is not traveling enough distance to register the threshold for input. For example, if the game were to register the trigger once the slider reaches, say, 60%, the game will register a trigger input when the slider has traveled 60% units

So THEN say your triggers sit lower at about halfway, essentially resting at 50%; when the slider travels from 50% to 100% it has only traveled 50% units, therefor not registering a successful input, being off by 10% in this example.

the best solution would be to get the wonderful developer, WILLS, to add a digital trigger press input to register as intended. :)

a quick, but annoying, solution... every time right before you plug in the controller, pull the triggers up to simulate a normal trigger resting height, then let it drop to, and hopefully it doesn't yet register at the current resting height. warning, the trigger will be sensitive and may register very easily.

a more involved solution could be to lightly stretch the trigger spring to allow the trigger to sit a bit taller and hopefully registers an input when fully pressing.
(all you need is a triwing and phillips screwdrivers to open the controller. AND WHEN YOU DO, open upside down, remove the back shell and leave the front half alone, again leave the frontside laying buttonside down. then to access the trigger springs, you need a fairly small, size 00, phillips screwdriver. careful not to strip the delicate screws. apply pressure and be as perfectly straight and perpendicular as you can. it helps)

Yeah I thought that was what was happening. Is there any way to contact the dev aside from twitter or is that the best way to maybe hope I can get a personal patch?

I have opened and cleaned my controller before so I definitely can open it every time but just seems like a hassle lol. I might buy another GCN controller lol.

[schmoo]

Entropoly right now only supports digital press for the Brake input. I am working on a solution to map analog input to it