CMS Left doesn't work when HOTAS combined
-
You say “Control Panel doesn’t see this button being pressed…” but then affirm that Target sees button 18 being activated ???
What do you define as “Control Panel” ??
Edit:
"Maybe it’s worth to mention I had Saitek X52 HOTAS and Logitech G25 (racing wheel and pedals) connected earlier, before connecting my brand new Warthog. I still have their drivers and profilers installed on my system. I’ll try to uninstall them and see how it goes without them. "
Good idea.
-
Maybe it’s worth to mention I had Saitek X52 HOTAS and Logitech G25 (racing wheel and pedals) connected earlier, before connecting my brand new Warthog. I still have their drivers and profilers installed on my system. I’ll try to uninstall them and see how it goes without them.
Still no go.
You say “Control Panel doesn’t see this button being pressed…” but then affirm that Target sees button 18 being activated ???
What do you define as “Control Panel” ??
No, that’s not what I meant. Take a good look in what states it sees the button - separate OR combined when script is running.
By “Control Panel” I mean this (look at images):
Before running the script you can see joystick separate from throttle - button works.
After running the script you see joystick and throttle combined - button doesn’t work.
^ It’s exactly the same for DEVICE ANALYZER.
So as you can see it’s not a mechanical problem. IMHO it’s something with the system, registry I guess (?).
I’m on WIN10 x64 BTW. -
Then it has to be the script I would think ?
Have you tried just creating a Target GUI profile (.fcf ) that includes stick & throttle but no programed events ?
-
Consider the following .TMC code
include "target.tmh" //program startup int main() { if(Init(&EventHandle)) return 1; // declare the event handler, return on error MapKey(&Joystick, H4L, PULSE+'a'); MapKey(&Joystick, H4R, PULSE+'b'); //add initialization code here } //event handler int EventHandle(int type, alias o, int x) { DefaultMapping(&o, x); //add event handling code here }
This code compiles and runs. If I press H4R I get a “b” but if I press H4L I do not get an “a”.
I think you have found a genuine bug in TARGET. I am running TARGET Script Editor v.3.0.16.413 and have this issue. If anyone can get the above simple code to run and output ‘a’ and ‘b’ using current or older TARGET version that would be useful info.
Also I do not get a functioning Device Analyzer since upgrading to Windows 10 x64 from Windows 7 x64.
–-
OK I found the problem and fix. It turns out that both H4L and EOLMOTOR are not functioning in the latest TARGET software. Both are the “DX18” of their respective controllers under non-TARGET mapping. The fix is to replace the tmhidcontrol.dll with the one from the previous version of TARGET. I have a few friends with Warthogs and I’ll see about getting the DLL from them from the previous version and share it.
-
I got someone to send me the DLLs but I couldn’t get the service to run again with the file replacements. I did find a copy of TARGET 1.0 to download which avoids the problem (unless you have the new pedals). I uninstalled TARGET 3.0.16 and reinstalled the older 1.0.11.304 and the issue isn’t present in the older verison.
-
Thanks a lot Frederf! I’ll do that when I get back home. Thanks again.
-
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.
-
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!