TDC cursor using Warthog Slew - a quick guide using TARGET

[sharkfin61]

Yes, the Target software disables the Warthog throtte (USB disconnect sound). This prompted me, for the first time, to actually program the throttle though the target software, buttons and all. I now have the three way flaps, exterior lights on a three way etc. Never played with Target before, didn't realise it was so easy:thumbup:

 

 

Anyway it would be nice, if the throttle would be enabled again when shutting down TARGET or stop running the profile.

[SinandGrin]

Yes that fixed it. Thanks very much.

 

 

Must be the target software.

 

Is there any better workaround/fix available rather than going into the Device Manager to re-enable the throttle? This is an annoying multi-step process.

 

Is this an actual bug in the TARGET software, does Thrustmaster know about it?

[Thermal]

Target is working exactly as designed. By default when you run a Target script, the Joystick and Throttle are removed from the system and the Thrustmaster Combined device is created in its stead.

You can stop this:

[color=#1e90ff][b]int[/b][/color] main()
{
   Configure(&Joystick[color=#ffffff],[/color]MODE_KEEPENABLED); 
   Configure(&Throttle[color=#ffffff],[/color]MODE_KEEPENABLED); 
   Configure(&TWCSThrottle[color=#ffffff],[/color]MODE_KEEPENABLED);
   Configure(&TFRPRudder[color=#ffffff],[/color]MODE_KEEPENABLED);

(If you dont have a TWCS or Rudder it will be ignored).

 

 

In this mode you end up with, in effect, three devices.

 

• The (complete and original) Joystick
  
• The (complete and original) Throttle
  
• The (virtual) "Thrustmaster Combined" device.
  

 

If you then define any Buttons or Axis in the rest of the Target script, then those, and only those, are mapped into the Thrustmaster Combined device.

 

For example, to only remap the Throttle Slew:

[color=#1e90ff][b]include[/b][/color] [color=#a52a2a]"target.tmh"[/color]

[color=#a52a2a][color=#1e90ff][b]int[/b][/color] main()[/color]
{
   Configure(&Joystick[color=#ffffff],[/color]MODE_KEEPENABLED); 
   Configure(&Throttle[color=#ffffff],[/color]MODE_KEEPENABLED); 
   Configure(&TWCSThrottle[color=#ffffff],[/color]MODE_KEEPENABLED);
   Configure(&TFRPRudder[color=#ffffff],[/color]MODE_KEEPENABLED);
   
   [color=#1e90ff][b]if[/b][/color][color=#ffffff]([/color]Init(&EventHandle)) [color=#1e90ff][b]return[/b][/color] [color=#ffffff]1[/color]; [color=#32cd32]// declare the event handler, return on error[/color]

   [color=#32cd32]//MapKey(&Joystick, S1, DX1);[/color]

   KeyAxis(&Throttle, SCX, 0,AXMAP2(LIST(0,25,75,100),',',0,'/'));
   KeyAxis(&Throttle, SCY, 0,AXMAP2(LIST(0,25,75,100),';',0,'.')); 
}


[color=#32cd32]//event handler[/color]
[color=#1e90ff][b]int[/b][/color] EventHandle[color=#ffffff]([/color][color=#1e90ff][b]int[/b][/color] type, [color=#1e90ff][b]alias[/b][/color] o, [color=#1e90ff][b]int[/b][/color] x)
{
   DefaultMapping(&o, x);
   
   [color=#32cd32]//add event handling code here[/color]
}

The Thrustmaster Combined device will still look like a full devices with lots of axis and buttons. It just wont map through any physical button presses into the virtual device.

(Unless you un-comment the MapKey statement above, and then only S1 and the Slew will be mapped through).

 

In this example, the end result when you move the Throttle Slew is two events, a keypress of ,/.; coming from Thrustmaster Combined *and* the (original) Throttle Slew axis will move.