I start this thread mostly to clarify some things, to see what controllers were/are used by Atari STE, Falcon users. Then some explanations about general support possibilities.
As I see, most spread controller is JagPad:
In Steem it is emulated it seems 100%:
How to read it in SW is explained well in this, for instance:
The Atari Enhanced Joystick Ports
Fequently Asked Questions
Version 0.90 - 24th September 1996
So, adding read of JagPad to some game seems as not big deal, and we can ask, why so few games support it - there is sadly short list of games supporting it in that FAQ.
What is really barely supported is analog imput - there is 2 of them on each port. Usually it is X-Y axe of analog stick. It seems that only one game supports analog paddles - Moonspeeder for Falcon.
And as I see, emulators don't support it. Even FAQ is unclear about it, and asks for help. Most likely because almost nobody of Atari people had such joystick.
Edited:Now the first question:
is it possible to attach some old PC analogue joystick to STE adv. port via adapter ? Connectors are not same, pin number is, and here I mean only analog X-Y lines to connect. According to AnthonyJ reply here: viewtopic.php?f=3&t=31699&start=25
End of edit.
Some people suggested some kind of wrapper, what would map JagPad input to some keyboard key presses, or regular (9 pin) joystick input.
That would be indeed very handy, and with that expansion lot of games would be playable with JagPad or some other compatible controller.
Unfortunately, that's not so simple. Atari is not PC with WIndows or some other modern OS. There is lot of direct communication with peripherals in SW, especially in games. So, if some game uses own code to read keyboard, joystick - wrapper simply will not work. Just to mention that in modern OS-es, direct access to HW is forbidden. Atari coders used direct access for good reason: speed, + could do some things hardly possible via TOS calls.
Since I dealt with lot of games, I can even give aprox. %-age of games where wrapper would work: ~15% .
In all other cases you need to add advanced port read code in middle of game's code for reading input devices. This is what I do when add options for saving gamestate and exit to Desktop. But that's much simpler than adding some new device input. And I have wrapper for it in TOS 1.04 running in RAM, so for games using TOS functions to read kb. all I need to do is to set which keys to assign for those 2 functions (it's usually * and / on NumPad)
All in all, doing that wrapper is worth only if there is some number of candidates, which read inputs via TOS calls. That needs making some list.Second question:
any people with some different controller than JagPad for their STE, Falcon advanced ports ?
You do not have the required permissions to view the files attached to this post.
Negative feedback has usually positive effect.