Joystick throttle?

[rhester72]

With the controller mapping choices being 2-button, 4-button, and Gravis, is it reasonable to assume that things like throttle levers on more advanced joysticks simply can't be mapped?

[Caldor]

Pretty sure its possible, do not see why it should be impossible. But probably pretty advanced compared to what has been done so far.

[rhester72]

OK, I intended that to read "can't be mapped by the current core". Most throttles show up as another axis, what isn't clear to me is whether that axis data is 'passed through' to the underlying OS.

[Kitrinx]

Standard controllers can have up to 4 axis and 4 buttons. Complex controllers (like gravis pro) attempt to serialize the data of one of the buttons to (very slowly) transmit more buttons and etc.

What you describe is a 4 button 4 axis joystick. I would have added this to the 4 button mode, however, MiSTer's framework currently only supports having 1 set of axis mapped. (ie one analog stick). The second controller's analog stick will still work in this mode, but I understand the akwardness of using it this way. If mister's framework gets support for a second analog stick in the future, I can add it.

[rhester72]

Makes sense and would be much appreciated (and a better reflection of the actual state of things in that era)!

[Bartdesign]

+1 for multiple axis support for controllers in the MiSTer framework. Flight sims run well on ao486 My thrustmaster is ready for x wing.

[ash2fpga]

I am curious if anyone is hooking up game port joysticks to the mister, and how they are doing it (simply game port -> usb adapters?). I wonder if there is any chance of a SNAC or SNAC-like interface for game port devices.

[remowilliams]

+1 for multiple axis support for controllers in the MiSTer framework. Flight sims run well on ao486 My thrustmaster is ready for x wing.

Yeah a throttle is almost a necessity for a good flight sim experience. Even support for something like the Gravis Analog Pro (3 axes, 4 buttons) would be great.

[Kitrinx]

I am curious if anyone is hooking up game port joysticks to the mister, and how they are doing it (simply game port -> usb adapters?). I wonder if there is any chance of a SNAC or SNAC-like interface for game port devices.

You'd need at least 8 wires for it, and we have 7 under the best of circumstances, so at least one button or axis wouldn't make it. I'm not sure if the timing chip lived in the joysticks for pc or in the game port card, like atari did it. If it's in the stick it might be possible, otherwise not.

[Kitrinx]

After looking it over, it seems most joysticks do have the timer on board. The lack of an 8th wire though will prevent it from ever being an ideal solution, missing one axis or button. IMHO the best route to an ideal scenario is to get a good gameport to usb converter (I believe McGyver is designing one) and work towards adding a second analog stick to the mister framework. Then all four axes and buttons will work with no downsides.

[MickGyver]

After looking it over, it seems most joysticks do have the timer on board. The lack of an 8th wire though will prevent it from ever being an ideal solution, missing one axis or button. IMHO the best route to an ideal scenario is to get a good gameport to usb converter (I believe McGyver is designing one) and work towards adding a second analog stick to the mister framework. Then all four axes and buttons will work with no downsides.

I am indeed working on a gameport to USB adapter. I'm currently implementing the Microsoft Sidewinder range. Since you have implemented GrIp support in the core, could you consider implementing the Sidewinder Precision Pro or 3D Pro? They use a similar principle, button1=clock and button2=data. The Sidewinder range need a trigger to send a data package, X1 is used as a trigger (pulled low for a couple of hundreds of microseconds). The good thing with these is they have four axes (X, Y, Throttle and Z-Rotation), hat switch and ~9 buttons.

[Kitrinx]

I am indeed working on a gameport to USB adapter. I'm currently implementing the Microsoft Sidewinder range. Since you have implemented GrIp support in the core, could you consider implementing the Sidewinder Precision Pro or 3D Pro? They use a similar principle, button1=clock and button2=data. The Sidewinder range need a trigger to send a data package, X1 is used as a trigger (pulled low for a couple of hundreds of microseconds). The good thing with these is they have four axes (X, Y, Throttle and Z-Rotation), hat switch and ~9 buttons.

Sure, do you have a link to a protocol description? Otherwise I can hunt it down.

[MickGyver]

I am indeed working on a gameport to USB adapter. I'm currently implementing the Microsoft Sidewinder range. Since you have implemented GrIp support in the core, could you consider implementing the Sidewinder Precision Pro or 3D Pro? They use a similar principle, button1=clock and button2=data. The Sidewinder range need a trigger to send a data package, X1 is used as a trigger (pulled low for a couple of hundreds of microseconds). The good thing with these is they have four axes (X, Y, Throttle and Z-Rotation), hat switch and ~9 buttons.

Sure, do you have a link to a protocol description? Otherwise I can hunt it down.

Great! Here is an avr implementation for the Precision Pro (with a description of the protocol): https://github.com/MaZderMind/SidewinderInterface. Here is the relevant code for the Linux driver implementation for the Sidewinder range: https://github.com/torvalds/linux/blob/ ... dewinder.c

[remowilliams]

IMHO the best route to an ideal scenario is to get a good gameport to usb converter (I believe McGyver is designing one) and work towards adding a second analog stick to the mister framework. Then all four axes and buttons will work with no downsides.

Having the second analog stick added to the framework would indeed be ideal. That way for using old sticks, it's simply a matter of obtaining one of the many gameport>usb devices and then mapping the controls in. And folks could map to modern dual stick controllers to if desired.

[Schyz]

Now it would be awesome that there was an option in ao486 to present the controller as a CH Flightstick Pro + Rudder Pedals, which should be compatible with most games (+Win9X) and relatively simple to translate: as far as I know, buttons to buttons, axes to axes and the only tricky part is to map the POV, as it sends 2-button combinations (also simultaneous button presses should send nothing to avoid interfering with the POV).