Hardware & Technical Thrustmaster warthog trigger no longer working as menu item select

[Klcomley]

So I have happily been playing all year with the warthog on win 8.1 using the in game warthog config (not target) with a few customisations. A few days ago I upgraded to win 10 (well, clean install) and after re-installing ED I found that the trigger button (Joy1) would no longer select in menus - was in the options config menu at the time, but same in game. Checked the button and works ok, shows as joy1 correctly when setting as primary fire etc. reinstalled drivers.

After no googling joy got withdrawal symptoms and trashed win 10 back to win 8.1. Unfortunately the problem has followed me back to win 8.1. Completely at a loss now, toyed with target but it was working fine before without, so there must be a solution out there someplace which is relatively painless.

Can anyone help please? (before I go completely bonkers!)

 

[huwthomas]

No idea why it stopped working, but presuming that Enter still works(*) to select in menus, maybe configure the stick button to send Enter. You could do this in TARGET, I personally don't like TARGET so do it with GlovePIE.

* I have noticed that sometimes certain inputs stop being recognised by the game GUI ... menu selection and escaping to the main menu being the two I've seen.

 

[Klcomley]

I did start to configure in TARGET, and that was the very thing I tried and yes it worked. The bad thing was I had no other config without going through the full TARGET setup, I could go the TARGET route in the absence of something else, I suppose the more time I sit and brood on it could be time setting it up.

Interesting comment about the inputs stopping being recognised too. GlovePIE I've not heard of will give that a google in the morning.

Thanks will have a brood on it overnight.

 

[Klcomley]

Well I've taken the option in the interim to configure Target, certainly as a starting point. I've followed through the excellent reference https://forums.frontier.co.uk/showthread.php?t=22379 (to the letter) and remain, er, baffled.

I've got the TG2 (secondary trigger press) mapped to ENT (mapping TG1 - light trigger press - to ENT meant JOY-1 wasn't recognised in the Control options). TG2 (JOY-1+JOY-6) works for making selections in the ED->Controls menu, so all looked promising. However, when in game the TG2 depress doesn't pass the ENT as it does in the config. Currently then I can't play :'( - the keyboard doesn't pass Enter (nor space as a menu selection), so that's not even an option.

I will have a go with GlovePIE as kindly suggested by huwthomas but the failure of TARGET leaves me a little pessimistic.

As a parting note, I also reverted to Win8.1 (then did an upgrade to Win10 immediately), with the controllers out - I had wondered whether leaving the controllers plugged in during the windows install might have led to windows installing it's own favoured drivers. Will probably try a clean install of 8.1 again (with controllers unplugged) and not upgrade to 10 - it's about the only other thing I haven't tried which would put the system in the working state it was the day I bought the Warthog.

 

[Rolandnc]

ThrustMaster Cougar HOTAS, T.A.R.G.E.T. with windows 10. I actually rebuilt an old computer to Windows XP standards and was able to flash the firmware to my TM HOTAS COUGAR. I just installed a new SSHD drive in my Windows 10 Sys. I downloaded and installed TARGET to the new drive "E" . I can not get the TargetFUI.exe nor the Targetscripteditor.exe to run... any ideas?

I already tried running as admin when selecting the three fils (TMservice.exe being the third) and no joy. I flashed remember using Winxp and not Vista. Your help would be appreciated.

Roland

 

[huwthomas]

I will have a go with GlovePIE as kindly suggested by huwthomas but the failure of TARGET leaves me a little pessimistic.

Have a look at the ED-oriented tutorial in my sig if you like.

In case you're not already doing it, I find it useful to have a text editor open and with focus when I'm testing this kind of config/scripting tool, at least you can be sure the required keystroke is actually being generated then.

 

[norcus]

So I have happily been playing all year with the warthog on win 8.1 using the in game warthog config (not target) with a few customisations. A few days ago I upgraded to win 10 (well, clean install) and after re-installing ED I found that the trigger button (Joy1) would no longer select in menus - was in the options config menu at the time, but same in game. Checked the button and works ok, shows as joy1 correctly when setting as primary fire etc. reinstalled drivers.

After no googling joy got withdrawal symptoms and trashed win 10 back to win 8.1. Unfortunately the problem has followed me back to win 8.1. Completely at a loss now, toyed with target but it was working fine before without, so there must be a solution out there someplace which is relatively painless.

Can anyone help please? (before I go completely bonkers!)

The following may go without saying, but I am learning the Warthog HOTAS right now and I learned this:
When you launch a TARGET configuration/script it removes the connected Thrustmaster controllers (Cougar, Warthog Throttle and Stick, and 2 MFDs) and combines them into a single virtual controller. Lets say you only have 2 game controllers; the Warthog throttle and stick. Typically when you start your PC the stick will be "Joystick 1" and the Throttle "Joystick 2". When you run a TARGET config, they are both removed and replaced with a single Joystick 1. So, make sure you always have a TARGET config running when you make changes to the controller setup in the game.

This means that if you have other game controllers connected to an USB port, the virtual controller may or may not be assigned the same ID on the USB bus each time you launch the configuration. This behaviour is intended to make the controllers backwards compatible with systems that can only recognize a single game controller. So, make sure you unplug any unused game controllers when using the Warthog HOTAS with TARGET. That way you ensure that the game always looks for button presses from the right controller (Joystick 1).

This also has the side effect that you have more buttons on your controllers than DirectX supports. DirectX support 32 buttons (DX1-DX32) and 8 axis for each controller, but the throttle and the stick combined have over 50 buttons (not counting 5 shift states). By default all the switches on the throttle will have no buttons assigned to them when you use TARGET and the axes are also switched around somewhat. To use all switches and buttons you will have to manually bind some of them to keyboard presses or use a script to create more advanced functionality.

I have owned the Warthog HOTAS now for only 5 days and already I have decided that I will need to use the Script Editor. The GUI is not powerful enough compared to what relatively simple script techniques can do.

Not at all sure if this helps OP at all, but I thought it might be of interest.