I'm wondering if anybody has experienced this:

I programmed switch macros to the left and right ENG OPER switches on the Warthog throttle base. With 3.0.16, I don't get any macro response when toggling the left switch between NORM and MOTOR. The right switch works just fine. I've verified in Device Manager that the left switch is properly detected, and I've also tested with a program that worked prior to the update and have the same issue. I've also rebooted and attempted these steps again with the same results.

Has anybody else experienced this?

I'm using Windows 7 x64 with TARGET 3.0.16 and a HOTAS Warthog, HOTAS Cougar, and 2 F-16 MFDs.

Same problem here.

It's H4L and EOLMOTOR. They are both button 18. DX detects the buttons fine, you can see them light up in Device Analyzer. However the script doesn't send any output. I tried mapping them as KB keys, DX buttons, everything.

I called TM support (Canada) just now. He said he was JUST reading an email from someone else about the same problem. He's sending it to headquarters in France, but it's night time there, so we won't know until tomorrow.

I'm fairly certain it's a bug in the new Target. Going to downgrade mine to the older one. Nothing really new that I needed in it anyways.

I couldn't find anything in the header files, so I figure the issue is in the binaries. I downgraded as well.

I found that the cause is tmhidcontrol.dll in TARGET folder.
You just need to replace it with tmhidcontrol.dll from the previous TAREGT version (you need to stop the Thrustmaster FAST service, replace the .dll and then restart the service).

I couldn't fix the issue by replacing DLLs between versions (service refused to run again). However I did find an older version of TARGET to install and rollback to the working version.

http://thrustmaster-target.software.informer.com/download/

FYI This is fixed now, new Target is out, 3.0.16(520).

Patchnotes:
V.3.0.16.520: Fixed a mapping bug on the HOTAS Warthog’s H4L button

Thanks. Appears to be working great now.