Abandoned Clicker's ED_BASIC_T16000 script

ED_BASIC_T16000

THIS SCRIPT IS NO LONGER AVAILABLE.

I have released the following Enhanced TARGET Script which replaces this script and which has a BASIC keymap option.


~~~

Clicker
 
Last edited:
Hi :)

Good Post, I'm impressed. ;)

I'm a T16000m user here, have been for the last....🤔...somewhere in the region of perhaps 10 years?...can't honestly remember now.
Using (on my) my third thrustmaster, with a brand new one in reserve, I bought these last two as a part of a two stick combo. (it was cheaper than buying two separate ones, £80 or thereabouts I think for the 'duo').
I've never bought the separate throttle, or rudder pedals, in conjunction with a Logitech G19 keyboard and a 7 button (cheap) mouse all aspects of controls within the game are covered (to my requirements).
I don't think I've ever used the target software, that's not to say it isn't useful, not having used it I'm in no position to comment in that area! :)
Still, as I've said...an interesting post. Thanks for posting it up. (y)

Jack :)
 
Last edited:
I gave up on Target, since the darn thing gets borked regularly by windows update. And Thrustmaster have not updated the software since 1982.

I built a lot of the functionality into EDD instead.
 
I gave up on Target, since the darn thing gets borked regularly by windows update. And Thrustmaster have not updated the software since 1982.

I built a lot of the functionality into EDD instead.
All good...thanks for your perspective.

FYI Thrustmaster have provided updates each time they've released new TARGET compatible controllers.
The most recent of which was earlier this year.

Cheers
 
Well they must have woken up, because they did not for a long time.

But the main problem was not their sw, it was windows update. It would routinely stop the tool working and you would have to go thru lots of troubleshooting to make the virtual devices work again. That problem is all over the internet
 
Agreed.

I was seldom able to get the "Device Analyzer" to work properly so resorted to using some custom scripting to test.
Re Windows...for the longest time, I had to stay on Windows 10 1909 due to the USB bug.
This issue is also all over the internet and is also mentioned several times in Aussiedroid's Script thread.

Gladly, though, this seems to be fixed now for Windows 10.
I am yet to test my scripts and controllers + TARGET on Win11.

In the meantime, if anyone here runs Win11 and installs my scripts, I'd be grateful if they post their success or otherwise here.

Cheers
 
Back
Top Bottom