Yet Another T.16000M FCS HOTAS Review and Setup
-
Hi Logic,
I just want to say thank you for this script. Spared me quite some time as I have just obtained the T16kM and TWCS and didn’t found the TARGET Software too intuitive. Works well for me. I have tailored it a bit to my Needs in Terms of funtionality.
-
EDIT 2: The game has built in profiles in keybindings folder or whatever for VAC (Voice Activated Commands) which is a different program than Voice Attack, so you’re pretty much all set there. Again I am a bit of a button lover so I try to free up buttons. On a side note for First Trigger Detent (Manual Lasing) do you have to hold the button down or just push it once to toggle the laser?
Excellent question, I have this doubt too. :help:
-
@Thunderbolt: You need to hold the button down for the time you want to lase.
-
Hi,
sorry, but after a few attempts I decided to go ahead with my own setup throught the TARGET software… viewing around with SHIFT plus castle hat is about the least intuitive thing I can think of, and getting the throttle out of the idle detent worked at the FIFTH (!) attempt only. No offence, but this is not the way to operate an airplane (and I have 700+ hrs of real-life stick time). If you can’t even operate it, how do you expect to fight in it?! Thanks for your efforts, but I shall have to make my own to make this work.
EDIT: Enough valuable time wasted on this. Signing off.
Sigmar -
The download link in the first post redirects to the 3.1 version but the text says it is 4.0. Has the 4.0 version has been released? or I am missing something.
Thank you.
-
You were right! The link in top post has been updated to the v4 archive.
-
Logic, Thank you so much for this post. This should be a sticky for T16000 joystick set ups. This saved me hours of frustration getting my set up going. Again thank you and badass job on this. It works slicker-n-snot. Now I just need to learn how to put it all to good use.
-
This post is deleted! -
Thank you! Thank you! Thank you, Logic!
I’ve spent hours banging my head against a wall trying to get BMS to recognise my TWCS. Your script finally got it going.
Regards from Ireland! Go raibh maith agat, mo chara!
Strawkalling
-
Greetings! I have been using the script myself to much fanfare… it works! My only question is concerning pedals usage, my TWCS is connected to the TFRP pedals and I’d be very happy to use them. I saw in the script that there are lines provided, it seems, to activate the pedals, but when I removed the “//” from the ends of the lines in question it didn’t seem to add the axes I needed. Am I missing any steps? Thanks so much.
-
Hi Slicerer,
i don’t have pedals, so i can’t test, but imho you don’t need to change anything in the script.
I’d let the script handle the TWCS only. (The comments in the script aren’t from me - i should remove them probably)
I guess you can use the pedals just by choosing them as the yaw input controler in BMS (instead of the joystick yaw axis).
So no fiddling with the TARGET script is required here.Cheers
-
Thanks for the quick reply! I hopped in really quick to see if any of my pedal axes were being recognized, they aren’t. My pedals are connected straight into the throttle and show up as Slider 1 for the rudder, RY for the left brake and RX for the right brake, all under the normal throttle axes mapping without the script. I know very little about scripting, but is there a way for the axes to be included or added into the script?
-
Oh, ok, i see. My bad, I thought the pedals were just on another USB connection. If the pedals are connected to TWCS, then they are probably seen just seen as an additional axis on TWCS.
I’d suggest you remove the line “Configure(&TFRPRudder, MODE_EXCLUDED);” from the TARGET script. What happens then? -
So I removed the suggested line: no change in behavior. Reading through the script its hard to not notice the section all about the pedals. If I’m reading it right it seems like the value right next to the value that lists the actual axis is what that axis would be assigned to, ie the analogue ministick looks like its mapped to the X&Y rotation axes. That leaves the slider axis open, i think. so while I wouldn’t be able to assign the toebrakes axes because their places have been taken by the ministick (I assume the ministick and t1600 conflict with each other), I can at least assign the slider to the rudder axis and just use that rocker assignment on the side. Or I might be wrong, which happens often.
Edit: But just to be clear, I’m not sure how its supposed to be written.
-
Update, I found it in the definitions, recompiled: it works! Gonna try and see if the unused Z axes can be mapped too
-
Great you figured it out!
But you brought me onto something there. I don’t know if the joystick and ministick are actually conflicting, i mean they are on a different device after all.
I dont know if BMS will allow to map the same axis name, but on a different device to a different axis in game.
This could mean the setup could be made entirely differently, thus freeing more axes on the TWCS for the pedals.
I’ll do some testing in the next days and keep you posted. -
Following the exchange with Slicerer, i made and released a new version of the package (v5) which is compatible out-of-the-box with TFRP (pedals).
For this, i needed to change some of the axes used by TWCS though, so if you use v5 package, make sure you re-assign proper axes in BMS conifg. -
Am I doing things right, because my result is that I get a “Thrustmaster Combined” -device instead of a “virtual game controller”. Setting up for BMS 4.34, so when the script is on, in windows device list I have T16000M, TCWS Throttle with a yellow warning mark “device not working properly” and then the “thrustmaster combined” -device. In BMS I have the T16000M set as the preferred device and I can see also the “combined” device and I can map axis etc. in to it in the advanced tab and the throttle works. When I press the throttle POV hat it seems to work. Instead of function it displays some different numbers when i press it.
Edit: Actually now the throttle has also the correct functions in the buttons and POV hat. So seems to work even though the name is “thrustmaster combined”.
-
Amazing piece of work, all worked first time and saved me hours, or most probably days of work. The only difference is that I get a “Thrustmaster Combined” device instead of a “Thrustmaster Virtual Game Controller (root)” same as in the previous post.
One question regarding the buttons mapped for press and hold - when pressing and holding a button does the primary function execute first followed by the secondary function or does only the secondary function execute thus ignoring the primary function.
-
Amazing piece of work, all worked first time and saved me hours, or most probably days of work. The only difference is that I get a “Thrustmaster Combined” device instead of a “Thrustmaster Virtual Game Controller (root)” same as in the previous post.
Well as long as everything works it’s ok i guess. Do you have the pedals?
One question regarding the buttons mapped for press and hold - when pressing and holding a button does the primary function execute first followed by the secondary function or does only the secondary function execute thus ignoring the primary function.
Only the secondary function is executed when you press (hold) long.
This technically implies that the primary function is only triggered once you release the button after a short press, instead of when you press it, but you won’t notice the difference much.