I just purchased a Sigma 8000TB, and it's working great. However, I'm having issues with the autofire rate.
I have the autofire set at maximum, yet Raiden DX's dedicated autofire button has a much faster rate of fire (which should definitely not be the case). I think it might have to do with the 'Off' 'N' 'Slow' switch at the top:
However, when that switch is set to anything other than Slow, none of the directions or buttons work. Any ideas?
Slow just adds an automatic turbo for the Start button at a preset rate. It's the same as any Slow button on console controllers and is intended for console games where Start pauses the game. If you're playing a game that doesn't have a quick Start pause (e.g. a game that slowly opens a pause menu), then the Slow feature may not work. Slow has no affect on turbo for other buttons. If you didn't mistype and really do mean that nothing works when "that switch is set to anything other than Slow," then you have a defective Sigma 8000TB.
As for autofire for other buttons, maximum speed isn't always the best for most games. The maximum autofire rate seems to produce a very fast pulse. However, most games can't process inputs that quickly. That means it'll ignore excess inputs sent in, causing the next input to perhaps not arrive as fast as possible. Some will start to ignore all inputs if a certain rate is surpassed (i.e. an autofire blocker either incidentally or accidentally). That's why there's a Speed knob at the top to adjust the autofire rate. You're supposed to tone that down until it's as fast as possible for the specific game being played. The 8000TB has no clue what's the maximum rate of input allowed by any given game.
I haven't seen a case where the ideal 8000TB autofire speed is slower than a game-provided autofire button's speed but if that's really the case, then it's possible a game has variable input frequency or has a specially designed autofire button that exceeds input frequency.
Thanks for the explanation.
I just realized that when the switch is set to N or Off, input does work, but only if the start button is being held.
Is that normal behavior?
