Help me provide the ultimate T.16000M FCS HOTAS T.A.R.G.E.T. profile!
-
I messaged BlueRaven and they suggested I post this in the forum as well so others could see their reply.
Hi BlueRaven,
Hope PMing you is ok. I’m just getting back into flight sims and decided to upgrade from my Logitech 3D Pro and after looking at my wallet and this forum I went for the joystick in the title.
I’m trying to setup the above as per your instructions and I’m running into some issues, I am getting wildly varying results.
Originally it wasn’t creating the one entry “Thrustmaster Virtual Game Controller (root)” and it worked as I expected, with a couple of things missing, the CMS,DMS switches were working just not the 8 way on the throttle. Now I can get Thrustmaster Virtual Game Controller (root) to appear in BMS but now the stick isn’t working or the throttle and the button assignments seem random. Most aren’t working but the 8 way on the top of the stick is now assigned to NWS, Pinky, Second Detent and Pickle.
Any ideas?
I’ve downloaded the drivers for stick and throttle from Thrustmaster.
I’m using your V1.1 configCouple of additional questions
I thought the Pinky switch was supposed to be like a shift function to allow more than one keypress to be assigned to a button but it doesn’t seem to have worked on any of my attempts.
Correct me if I’m wrong, but your setup doesn’t allow moving the radar cursor without keyboard?
SimTriggerFirstDetent -1 0 0x35 2 0 0 1 “STICK: FIRST TRIGGER DETENT” suggests a two stage trigger is setup but it doesn’t seem to work.This is what I see when I run your script
Running script: C:\Users\Jools\Documents\BlueRaven_BMS_TARGET_Prof ile_v1.1\FalconBMS.tmc
*** Allocated ProcInstances found from the previous run: use FreeProcInstance() ***
Mapped plugin module “C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll”
Compile Succeeded.
Physical USB HID devices managed by script!
Currently plugged USB HID devices[2]:
1: “TWCS Throttle” - “USB\VID_044F&PID_B687&REV_0110”
2: “T.16000M” - “USB\VID_044F&PID_B10A&REV_0500”
USB HID device “T.16000M”(USB\VID_044F&PID_B10A\5&DC4A972&0&1 0) selected
USB HID device “TWCS Throttle”(USB\VID_044F&PID_B687\5&DC4A972&0&13) selected
Virtual HID devices managed by script!
Connecting virtual joystick…Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard…Done
Connecting virtual mouse (absolute axes)…Donemain returned 0
-
I messaged BlueRaven and they suggested I post this in the forum as well so others could see their reply.
Hi BlueRaven,
Hope PMing you is ok. I’m just getting back into flight sims and decided to upgrade from my Logitech 3D Pro and after looking at my wallet and this forum I went for the joystick in the title.
I’m trying to setup the above as per your instructions and I’m running into some issues, I am getting wildly varying results.
Originally it wasn’t creating the one entry “Thrustmaster Virtual Game Controller (root)” and it worked as I expected, with a couple of things missing, the CMS,DMS switches were working just not the 8 way on the throttle. Now I can get Thrustmaster Virtual Game Controller (root) to appear in BMS but now the stick isn’t working or the throttle and the button assignments seem random. Most aren’t working but the 8 way on the top of the stick is now assigned to NWS, Pinky, Second Detent and Pickle.
Any ideas?
I’ve downloaded the drivers for stick and throttle from Thrustmaster.
I’m using your V1.1 configCouple of additional questions
I thought the Pinky switch was supposed to be like a shift function to allow more than one keypress to be assigned to a button but it doesn’t seem to have worked on any of my attempts.
Correct me if I’m wrong, but your setup doesn’t allow moving the radar cursor without keyboard?
SimTriggerFirstDetent -1 0 0x35 2 0 0 1 “STICK: FIRST TRIGGER DETENT” suggests a two stage trigger is setup but it doesn’t seem to work.This is what I see when I run your script
Running script: C:\Users\Jools\Documents\BlueRaven_BMS_TARGET_Prof ile_v1.1\FalconBMS.tmc
*** Allocated ProcInstances found from the previous run: use FreeProcInstance() ***
Mapped plugin module “C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll”
Compile Succeeded.
Physical USB HID devices managed by script!
Currently plugged USB HID devices[2]:
1: “TWCS Throttle” - “USB\VID_044F&PID_B687&REV_0110”
2: “T.16000M” - “USB\VID_044F&PID_B10A&REV_0500”
USB HID device “T.16000M”(USB\VID_044F&PID_B10A\5&DC4A972&0&1 0) selected
USB HID device “TWCS Throttle”(USB\VID_044F&PID_B687\5&DC4A972&0&13) selected
Virtual HID devices managed by script!
Connecting virtual joystick…Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard…Done
Connecting virtual mouse (absolute axes)…Donemain returned 0
Ok some additional. When I test the controller in windows I can see why it’s making no sense in BMS. Example - On the stick the 4 buttons on the top, trigger / 2 / 3 / 4 no longer do anything and UP DOWN LEFT RIGHT on the POV nipple has taken their place. When I use the TARGET device analyser I can see the original button mappings are still registering
-
That’s probably why my profile sets the stick POV hat as DX buttons, so that I can associate them with trim.
Did you by chance modify the DeviceSorting.txt file?
Andh what do you mean with “the original button mappings are still registering”? -
My DeviceSorting.txt file is from your v1.1 folder.
Regarding the button behaviour, if I use the device analyser everything looks as it should with the buttons presses, contrary to what I see for the controller in windows.
Thanks for your help, this is the setup I’ve settled on for now. As you can see there are plenty of shifted button options still available. Everything on there I need or anything else anyone would recommend as useful to have on the stick?
https://i.imgur.com/saKbJGC.png
Thanks BlueRaven for the initial key file I’ve based my setup on and thanks also to Eidolon for the image I’ve stolen for my use, very handy!
-
OK guys, first of all thanks again for the trust you gave me.
I want to deserve it, so - given that several others of you are experiencing problems due to TARGET working as it should (sounds crazy, but that’s it) - I will soon post a new version of my setup, following the idea :idea: I had some time ago to manage only the TWCS Throttle via TARGET.
This, at least in my expectation, should render TARGET behavior irrelevant… stay tuned, I’ll try to provide the updated version ASAP. :munch: -
Version 7 of my mappings
-
Hey guys, think is straightforward to adapt an FCS profile to a CH pro Throttle + T16000M?
-
As you can see there are plenty of shifted button options still available.
Out of curiosity, how to you activate these shifted button options? That is not pressing keyboard SHIFT is it??
-
Out of curiosity, how to you activate these shifted button options? That is not pressing keyboard SHIFT is it??
The HotasPinky button is one of the buttons mapped to the stick or throttle that acts as a shift button if held, it also has some zoom function on some screens in certain modes if tapped.
-
Quite late now (real life calling) but I am working on it… meanwhile, I updated drivers on my PC and now TARGET works correctly for me (hiding physical devices), so I hope to really solve the matter once for all.
-
OK guys, I think I finally made it! :woohoo:
As I said, I completely reviewed the idea: now the TARGET profile manages TWCS Throttle only, so T.16000M joystick remains visible and is configured purely via DirectX in the keyfile.
All the throttle buttons have been explicitly assigned a DX id, so no more “holes” in the sequence and the mappings in the keyfile have been reassigned accordingly.
For maximum ease and convenience, I also included my DeviceSorting.txt configuration file in order to make BMS see the devices in the right order and make the callbacks assignments in the keyfile match.
So the whole thing should only be a matter of following these few steps:- download and uncompress the attached .zip archive
- put both Blueraven.key and DeviceSorting.txt files in your BMS User\Config directory
- run FalconBMS.tmc profile with TARGET Script Editor
- fire BMS, load my keyfile and assign axes in the Advanced controller configuration
- enjoy!
Let me know if it’s working and how you think it could be further improved.
Thanks and have a nice fly! -
OK guys, I think I finally made it! :woohoo:
As I said, I completely reviewed the idea: now the TARGET profile manages TWCS Throttle only, so T.16000M joystick remains visible and is configured purely via DirectX in the keyfile.
All the throttle buttons have been explicitly assigned a DX id, so no more “holes” in the sequence and the mappings in the keyfile have been reassigned accordingly.
For maximum ease and convenience, I also included my DeviceSorting.txt configuration file in order to make BMS see the devices in the right order and make the callbacks assignments in the keyfile match.
So the whole thing should only be a matter of following these few steps:- download and uncompress the attached .zip archive
- put both Blueraven.key and DeviceSorting.txt files in your BMS User\Config directory
- run FalconBMS.tmc profile with TARGET Script Editor
- fire BMS and assign axes in the Advanced controller configuration
- enjoy!
Let me know if it’s working and how you think it could be further improved.
Thanks and have a nice fly!So how would you DX shift this? Just as normal?
-
-
FYI: I am successfully using BlueRavens TARGET script. I am using my own BMS key bindings and i’m using DX shift as mentioned. Attached is a PDF with the IDs of all the buttons as seen by BMS, produced by BlueRaven’s FalconBMS.tmc script.
This is for T.16000M (stick) first DX device and TWCS (throttle) second and with “set g_nHotasPinkyShiftMagnitude 256” in falcon bms.cfg (default). -
@BlueRaven: I find it difficult to use the radar cursors with the analog hat. I’m overshooting most of the time.
What are your BMS settings for those axes? (Deadzone, Saturation)
I’ll probably do some experiments and map these to DX buttons also. -
@BlueRaven: I find it difficult to use the radar cursors with the analog hat. I’m overshooting most of the time.
What are your BMS settings for those axes? (Deadzone, Saturation)
I’ll probably do some experiments and map these to DX buttons also.Hi, no deadzone and stock saturation.
I have no particular problems in being quite precise with radar cursor, maybe it’s only a matter of muscular memory of your left index finger.