CMS Left doesn't work when HOTAS combined
-
Interesting find……
-
I have used dx buttons in target, also have them mapped in key file. No problem here using cms left. I have just installed new target software as well. I would try a reinstall. Or go into Ui select key file and push cms left to see what it is mapped to.
Ok, I’ll try reinstallation. If it still won’t work I’ll get back to versions suggested by Frederf.
Which Windows do You use sub101? - Win7 or Win10? -
Had exactly the same problem. Rolled target back to 1.0 and it’s now working fine.
-
Ok, I’ll try reinstallation. If it still won’t work I’ll get back to versions suggested by Frederf.
Which Windows do You use sub101? - Win7 or Win10?win 10 64 bit. But I don’t have mfd or pedals. I will check my profile again, just to make sure. then I will try and replicate your problem. It seems you are not alone with this.
-
I’ve tested it now couple times with exactly same results. I even tried plugging Warthog to other USB ports, unplugging my Saitek Pro Combat Pedals and updated TMHW Firmware.
1. Uninstalled TARGET 3.0.16 > Uninstalled TW Warthog HOTAS Drivers > Restarted > Installed again 2014_TMHW_1 Drivers > Restarted > Updated HOTAS Firmware > Installed TARGET 3.0.16 again exactly how instructions sais (TMWH unplugged under TARGET installation) > Restarted > Run TARGET GUI > Run Configuration combining Stick and Throttle = CMS Left doesn’t work (checked in DEVICE ANALYZER and CONTROL PANEL/CONTROLLERS)> Run TARGET Script Editor > Run Script = CMS Left doesn’t work (checked in DEVICE ANALYZER and CONTROL PANEL/CONTROLLERS)
2. Uninstalled TARGET 3.0.16 > Restarted > Installed TARGET 1.0.11.304 > Restarted > Run TARGET GUI > Run Configuration combining Stick and Throttle = CMS Left works > Run TARGET Script Editor > Run Script = CMS Left works
3. Uninstalled TARGET 1.0.11.304 > Restarted > Installed TARGET 3.0.16 again > Restarted > Run TARGET GUI > Run Configuration combining Stick and Throttle = CMS Left doesn’t work > Run TARGET Script Editor > Run Script = CMS Left doesn’t work
4. Uninstalled TARGET 3.0.16 > Restarted > Installed TARGET 1.0.11.304 again > Restarted > Run TARGET GUI > Run Configuration combining Stick and Throttle = CMS Left works > Run TARGET Script Editor > Run Script = CMS Left works
I’ve also noticed something else - TARGET 3.0.16 DEVICE ANALYZER shows many other HID devices. I don’t see them in TARGET 1.0.11.304 DEVICE ANALYZER…
Only thing I had to change in my script to work with TARGET 1.0.11.304 was deleting these lines:
Configure(&T16000L, MODE_EXCLUDED); Configure(&TFRPRudder, MODE_EXCLUDED); Configure(&TWCSThrottle, MODE_EXCLUDED);
^ Obvious reasons - TARGET 1.0.11.304 doesn’t know these newest TM controllers.
So I guess it’s time to contact TM support to look at this issue.Thanks to Frederf once more! :bowd:
[EDIT] I’ve just got the answer from TM Support:
@TM:
Thank you for contacting Thrustmaster Technical Support.
The issue you are experiencing is due to a bug brought in by the new version of TARGET.
Our programmers are working at the moment at an update to fix this.
In the meantime the only thing we can do is wait as there is no ETA for the release of a new version.
-
So I won’t be upgrading my Target Software, not that I normally would unless I had too…
Good info.
-
Interestingly I also had this problem. In addition I have Thrustmaster MFDs included in my Thrustmaster Combined set up. On both MFD’s OSB18 doesn’t work despite being set up in Target GUI. I’m using version 3.0.16.426.
I’ve since set up another profile that leaves the MFDs out and they are now programmed directly into BMS.
Defo need Target update. Trot on Thrustmaster.
-
Interestingly I also had this problem. In addition I have Thrustmaster MFDs included in my Thrustmaster Combined set up. On both MFD’s OSB18 doesn’t work despite being set up in Target GUI. I’m using version 3.0.16.426.
Oh, you mean you also have problem with those “magic” DX18s? I know, I know now! It’s the maliciousness of fate because TM didn’t show the Hornet HOTAS on last presentation that everyone was counting for. It’s 18s revenge. :mrgreen:
-
Oh, you mean you also have problem with those “magic” DX18s? I know, I know now! It’s the maliciousness of fate because TM didn’t show the Hornet HOTAS on last presentation that everyone was counting for. It’s 18s revenge. :mrgreen:
-
Thanks guys for finding this out - I’ve been tearing my hair trying to understand these issues, I thought it was a switch failure.
Which is weird, because my pinky switch has just definitely failed too!