Saltar al contenido principal

Búsqueda

Allow button mashing faster than 15 inputs per second

  • TAPgiles

    Logic runs at 30 fps. If you're using a pulse, that requires it to go from off to on--meaning a frame of no signal in between. Which means you can fit 15 pulses into 30 frames. So it's not actually to do with processing button presses, but how logic is run in general --which is not likely to change, honestly.

    You can still detect up to 30 presses per second with some creative logic.

  • CreamSohda

    Appreciate it, Giles. I decided on the simplest solution of allowing multiple buttons. Works well enough.

    What's required to detect a button press on all 30 logic cycles?

  • TAPgiles

    I haven't tried implementing it, but you could use a looped NOT gate (wired into itself so it sends a 1 and 0 on alternate logic frames) into a selector's active port (using channel A for a 1 and channel B for a 0) and use the signals coming from those channels to do whatever. So if you just want to count presses, put those through sig-manips to make pulses, and have them add to separate counters. Then add those counters together.

    Thing is, if your logic needs to be triggered and cannot be redone to respond to consecutive frames of activation, you'd have to duplicate that logic basically. It very much depends on what the logic is in the first place.

Iniciar sesión para dejar un comentario.