what's this doing in the "analog controls" menu anyway?
In general, digital speed is how fast mame fakes "increasing" the analog value when translating digital to analog, while sensitivity is the percentage of mame's internal analog value mame sends the game.
Example: sensitivity is 50%. If you have an analog joystick, and it's all the way to the right, and the game input type is analog stick or paddle, mame will send the game that it's half way to the right (assuming mame is set to emulate the stick/paddle at 100%). Dial/TB/spinner is a little different in that at 50%, mame sends the game that it's turning half the rate that mame gets it (think TT2's 1200 cpr, tempest had 72 cpr, so set sensitibity to 6% mame sends the game 72 cpr of TT2).
Digital speed, and it's related centering speed, is only for digital to analog translation, the former for when the digital button is pressed, the latter when it's not pressed and the input type in mame is set to autocenter. Example: if set to 10, and button pressed, mame changes the analog value by 10 per frame until the button is released. Important: this is assuming sensitivity is set to 100%; sensitivity changes this, so if sensitivity was at 50%, the delta would be 5 instead of 10.
Positional input type is a special analog input type that could be like a spinner, or like an analog stick, or a combination of the two, and has other special properties, and is still WIP. One property is that when the digital speed is set to 0, mame changes the value by one the first time it sees it pressed, but doesn't change the value after that (until button released and then pressed again of course).
How do all these add up in mame in ikari type rotary games?
If sensitivity was less than 100%, then mame would change the value by less than 1. But mame work in integers, so you can lose info.
If digital speed was not 0, the player will continue to turn as long as mame sees the button is held down.
If the positional type code inside mame is broken, things wouldn't work as they should.
So....
How current is your RJI? It was fixed, but for a while the RJI would send the pressed button signal so shor mame would not detect the press, as mame uses a "current state" method of viewing inputs, not the normal "event based" method. From your symptoms, it almost sounds like it's just barely too fast for mame to constantly poll when the "button is pressed".
Another possibility, how tight is your CPU speed to run those games? If it's a borderline computer, that might be the cause instead.
