[Solved] Very glitchy controls.

[Fixmylife]

I applyed the line to the code .. it worked great no more double clicking or skipping and button are still fast and responsive. Thanks alot

[YaYa]

Could you change the topic title to add a [SOLVED] to help future people ?

[salami738]

I applyed the line to the code .. it worked great no more double clicking or skipping and button are still fast and responsive. Thanks alot

Hi, thanks for testing it out and replying.
Please remove the "line: " from your code. It is not necessary. Code should be:

"
// Send everything to USB
Joystick.setState(&joySt);
delay(50);
}
"

Please also report this change back to the original creator thread.

A little theory: A lower delay value means more inputs/second. A higher delay value means less inputs/second.
e.g.:
delay(50) --> <= 20 inputs/s (should be more than enough).
delay(100) --> <= 10 inputs/s
...
delay(1000) --> <=1 inputs/s (not enough for most games, possible high delay between presses and the game reaction)

greetings from Germany

[DeRock89]

I applyed the line to the code .. it worked great no more double clicking or skipping and button are still fast and responsive. Thanks alot

Hi, thanks for testing it out and replying.
Please remove the "line: " from your code. It is not necessary. Code should be:

"
// Send everything to USB
Joystick.setState(&joySt);
delay(50);
}
"

Please also report this change back to the original creator thread.

A little theory: A lower delay value means more inputs/second. A higher delay value means less inputs/second.
e.g.:
delay(50) --> <= 20 inputs/s (should be more than enough).
delay(100) --> <= 10 inputs/s
...
delay(1000) --> <=1 inputs/s (not enough for most games, possible high delay between presses and the game reaction)

greetings from Germany

I FINALLY got the time to try this and I believe my Leonardo is broken now.... At Least that is what Google is informing me when I google the issue. It will not recognize when plugged into my PC. In the Arduino IDE , the Serial port selections is grayed out. The IDE software is saying that its not finding anything on COM 5. Serial Port Monitor does not find anything. Three LEDs are lit up on my Leonardo when plugged in, two Red and one green.

Everything worked fine a few weeks ago when I initially programmed it other then the button issues. All I did is change this Code you stated and attempted to upload it.

I am still following Sotas instructions in his guide for two analog sticks and 14 buttons to the T other then the edited code.

[DeRock89]

I applyed the line to the code .. it worked great no more double clicking or skipping and button are still fast and responsive. Thanks alot

Hi, thanks for testing it out and replying.
Please remove the "line: " from your code. It is not necessary. Code should be:

"
// Send everything to USB
Joystick.setState(&joySt);
delay(50);
}
"

Please also report this change back to the original creator thread.

A little theory: A lower delay value means more inputs/second. A higher delay value means less inputs/second.
e.g.:
delay(50) --> <= 20 inputs/s (should be more than enough).
delay(100) --> <= 10 inputs/s
...
delay(1000) --> <=1 inputs/s (not enough for most games, possible high delay between presses and the game reaction)

greetings from Germany

Nevermind.... MY USB wire wasnt plugged in well enough. Problem solved as far as that. Im also having an Issue with my Start and Select Buttons. I have to really jam my finger nails into the start and select to make it register. Ive tried different conductive pad silicone. The Button PCB is screwed down as tight as I can get it.

[DeRock89]

I applyed the line to the code .. it worked great no more double clicking or skipping and button are still fast and responsive. Thanks alot

Hi, thanks for testing it out and replying.
Please remove the "line: " from your code. It is not necessary. Code should be:

"
// Send everything to USB
Joystick.setState(&joySt);
delay(50);
}
"

Please also report this change back to the original creator thread.

A little theory: A lower delay value means more inputs/second. A higher delay value means less inputs/second.
e.g.:
delay(50) --> <= 20 inputs/s (should be more than enough).
delay(100) --> <= 10 inputs/s
...
delay(1000) --> <=1 inputs/s (not enough for most games, possible high delay between presses and the game reaction)

greetings from Germany

The Delay Code worked!!! No more double button pushes. I got the start and select working a LITTLE better by centering up the PCB better.
Now I have to figure out why left and right on my left analog stick is inverted.... I set the left and right correctly in emulation station. its just inverted when a game is launched.

Also now that I have it back togeter, the sound volume output is decreased a lot.... I dread taking my GB back apart again.... It takes me an hour to reassemlbe it because everything is fit so tight and there are so many wires to manipulate to make the two halves fit together...

[goosewerks]

This worked for me! I hadn't run into this issue with any previous builds (3 down, no problems) but this 4th was having so many "A" button bounces that it was unusable. Added the small snippet of code as stated above, and the delay of 100 worked for me. 50 wasn't good enough. Everything works like a charm now.