To Mc-Escher:
Thanks for developing this. I am looking forward to testing it out.
To LilWolf:
There is also another advantage in MC-escher implementation of this over using 12 button inputs as you suggest. The original hardware did use 12 button inputs, but the LS-30 joysticks restricted your movement. For example, let's say that Button 1 corresponded to Player 1 pointing at 1 o'clock and Button 9 corresponded to Player 1 pointing at 9 o'clock. Using your set-up, it would be possible for the character to move from 1 o'clock to 9 o'clock without rotating through the intermediate positions. The current MAME and MC-Escher's implementation prevent this.
To All:
This is a summary of how things stand:
Official MAME build: supports mice, optical rotary joysticks, spinners, and keyboard keys/arcade buttons very well for rotation. Will support SNK LS-30's using Druin's interface, but requires tweaking of the analog settings and speed settings, and provides imperfect results (some missed clicks and double clicks). Does NOT directly support LS-30 joysticks.
Mc-Escher's build: Does NOT support opto-rotary devices, Provides much better support for LS-30's using Druin's interface, Provides limited keyboard/button support but requires multiple keypresses for rotation. Should support a custom joystick design that I may be reviving
. Does not directly support LS-30 joysticks.
LilWolf's proposed build: Does NOT support opto-rotary devices. Does NOT support LS-30's using Druin's interface. Does not easily support keyboard/buttons (if you had twelve buttons arranged in a circle, maybe . . .), Does directly support LS-30 joysticks. No one has done this yet, AFAIK, however, I would like to see it available for 3 reasons: 1) It would be possible to support this using LS-30's on a removable control panel using an IPAC-4, MK64, or KE-72 encoder. 2) It would allow owners of original rotary game cabinets to play the game with original hardware, (if say the original board was fried), without having to use Druin's interface. 3) Most importantly, this is how the original hardware was set up, thus, in keeping with MAME's stated purpose of preserving the original arcade games, it should be emulated this way at least somewhere.
Questions to All:
Once Mc-Escher's build is availble, I would like to see about submitting it to the dev team and getting it added to the official build, but I have the following questions:
Ideally, it would be great if MAME were set up to handle opto-rotary devices using the current code, Druin's interface using MC-Escher's build, and straight LS-30's using LilWolf's proposed build, all in the same driver. I have no idea how to do this! Anyone???
Another idea would be to set up MC-Escher's build and Lil-Wolf's proposed build as new drivers. Thus for IKARI, you would have games named "Ikari Warriors (US) (opto-rotary)", "Ikari Warriors (US) (mechanical rotary with interface)", and "Ikari Warriors (US) (orignal hardware). The problems with this is you are adding two new games per version and clone, and it would be confusing to the casual user. This is similar to what MAME has done on Combat School, for example.
Any other ideas on how to implement this???