You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My arcade cabinet has 2 USB TurboTwist2 Spinners connected. I'm running groovymame as the executable on Arch Linux (GroovyArcade CD install).
When launching groovymame directly from a bash terminal (from the LXDE desktop), e.g. groovymame outrunb
I can press TAB in groovymame and assign the spinner to dial inputs no problem. They come up as Mouse1Y, Mouse1X when I move the spinners.
When launching groovymame through another frontend (AdvanceMENUPlus) installed on the same Arch Linux/GroovyArcade setup, again I can assign the dial inputs by moving my spinners with no problems.
When launching groovymame through attractmode installed on GroovyArcade, the TurboTwist2 spinners are not recognised when they are moved.
I believe this is an attractmode issue (when running on Arch Linux) because: -
spinners work in groovymame when running directly from bash terminal
spinners work in groovymame when running directly from AdvanceMENUPlus frontend
spinners (or a connected mouse) do NOT work in groovymame when running directly from attractmode
groovymame's verbose debug output is identical in all the above 3 cases (attached)
My arcade cabinet has 2 USB TurboTwist2 Spinners connected. I'm running groovymame as the executable on Arch Linux (GroovyArcade CD install).
When launching groovymame directly from a bash terminal (from the LXDE desktop), e.g.
groovymame outrunb
I can press TAB in groovymame and assign the spinner to dial inputs no problem. They come up as Mouse1Y, Mouse1X when I move the spinners.
When launching groovymame through another frontend (AdvanceMENUPlus) installed on the same Arch Linux/GroovyArcade setup, again I can assign the dial inputs by moving my spinners with no problems.
When launching groovymame through attractmode installed on GroovyArcade, the TurboTwist2 spinners are not recognised when they are moved.
I believe this is an attractmode issue (when running on Arch Linux) because: -
attract.txt
I'm running Attract-Mode v2.2.1-43 (Linux)
The text was updated successfully, but these errors were encountered: