Jump to content

Thrustmaster TCA Throttle Quadrant and working Detents for the FSX Version of the Aerosoft Airbus


Veles

Recommended Posts

After receiving my TCA Officer Pack, i spent my last few days elaborating a workaround (because obviously there will be no Update for the Bus to support the quadrant) for achieving an alignment of the Quadrant detents with the simulated detents of the Aerosoft Airbus. And finally it works fine for me, so i thought i will share it with all of you remaining FSX users, to get the most out of your quadrant!

 

If you have not already installed, you need:

FSUIPC4 registered Version and, this is important! (otherwise you get random throttle movement), you need to alter the FSUIPC4.ini: There is a line that says UseAxisControlsForNRZ=No. Change this to UseAxisControlsForNRZ=Yes

Linda and the Linda Module for the Aerosoft Airbus to assign the IGN Switch, Engine Masters etc.

Thrustmasters T.A.R.G.E.T. Software

 

First run the Target Script Editor and Import this script and run it:

 

include "target.tmh"
int main()
{
    Configure(&HCougar, MODE_EXCLUDED);
    Configure(&Joystick, MODE_EXCLUDED);
    Configure(&JoystickF18, MODE_EXCLUDED);
    Configure(&Throttle, MODE_EXCLUDED);
    Configure(&A320Pilot, MODE_EXCLUDED);
    Configure(&A320Copilot, MODE_EXCLUDED);
    Configure(&TCAQuadrant34, MODE_EXCLUDED);
    Configure(&T16000, MODE_EXCLUDED);
    Configure(&T16000L, MODE_EXCLUDED);
    Configure(&LMFD, MODE_EXCLUDED);
    Configure(&RMFD, MODE_EXCLUDED);
    Configure(&TFRPRudder, MODE_EXCLUDED);
    Configure(&TWCSThrottle, MODE_EXCLUDED);
    Configure(&TFRPHARudder, MODE_EXCLUDED);
    if(Init(&EventHandle)) return 1;
    SetKBRate(32, 50);
    SetKBLayout(KB_GER);
    SetShiftButton(0, 0, 0, 0, 0, 0);
    MapAxis(&TCAQuadrant12, QT_LEFT, DX_X_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
    SetCustomCurve(&TCAQuadrant12, QT_LEFT, LIST(0,0, 3,14, 23,14, 24,14, 29,24, 48,24, 49,24, 73,73, 74,74, 75,75, 80,80, 100,100));
    MapAxis(&TCAQuadrant12, QT_RIGHT, DX_Y_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
    SetCustomCurve(&TCAQuadrant12, QT_RIGHT, LIST(0,0, 3,14, 23,14, 24,14, 29,24, 48,24, 49,24, 73,73, 74,74, 75,75, 80,80, 100,100));
    MapAxis(&TCAQuadrant12, QF_FLAP, DX_Z_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
    SetSCurve(&TCAQuadrant12, QF_FLAP, 0, 0, 0, 0, 0);
    MapAxis(&TCAQuadrant12, QS_SPEED, DX_ZROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
    SetSCurve(&TCAQuadrant12, QS_SPEED, 0, 0, 0, 0, 0);
    MapAxis(&TCAQuadrant12, QR_RIGHT, DX_XROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
    SetSCurve(&TCAQuadrant12, QR_RIGHT, 0, 0, 0, 0, 0);
    MapAxis(&TCAQuadrant12, QR_RUDDER, DX_SLIDER_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
    SetSCurve(&TCAQuadrant12, QR_RUDDER, 0, 0, 0, 0, 0);
    MapAxis(&TCAQuadrant12, QR_LEFT, DX_YROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
    SetSCurve(&TCAQuadrant12, QR_LEFT, 0, 0, 0, 0, 0);

}
int EventHandle(int type, alias o, int x)
{
    DefaultMapping(&o, x);
}

 

It's the default script i copied from the T.A.R.G.E.T. GUI after creating a new profile only including the quadrant. However i made only this change:

MapAxis(&TCAQuadrant12, QT_LEFT, DX_X_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
SetCustomCurve(&TCAQuadrant12, QT_LEFT, LIST(0,0, 3,14, 23,14, 24,14, 29,24, 48,24, 49,24, 73,73, 74,74, 75,75, 80,80, 100,100));
MapAxis(&TCAQuadrant12, QT_RIGHT, DX_Y_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
SetCustomCurve(&TCAQuadrant12, QT_RIGHT, LIST(0,0, 3,14, 23,14, 24,14, 29,24, 48,24, 49,24, 73,73, 74,74, 75,75, 80,80, 100,100));

 

SetCustomCurve is the command which allows you to create a custom sensibility curve for the axis. So i figured out where to set the detents, created dead zones inbetween and made the area between idle and clb more sensible. If my values do not align with your Quadrant you can change the values as follows: LIST(0,0, 3,14, 23,14, 24,14, 29,24, 48,24, 49,24, 73,73, 74,74, 75,75, 80,80, 100,100) 0 is the max thrust position of the quadrant, 100 the minimum (full reverse) position, you can delete and add any value between 0 and 100. The first value of a group (e.g. 80,80, ) is the position of the hardware, the second value the output value. So in my case i chose 49/24 for the clb detent - TCA at position 49, output value 24 where the aerosoft Airbus axis detects the clb position. 29,24, 48,24, is the deadzone between clb and flx, 24,14 my flx detent, 3,14, 23,14 deadzone between max and flx, 0,0 max detent. The section 73,73, 74,74, 75,75, is my attempt to stabilize the idle area (otherwise the idle pos of the TCA would already produce thrust in the sim), 80,80, 100,100 is just to get a linear sensibility for the rest of the axis. For further information read the T.A.R.G.E.T. manuals.

 

So far so good.

Next step is to assign the throttle axis via FSUIPC: Option "direct to FSX", Calibrate the Axis: Enable "no reverse", set the Quadrant to idle pos and set the minimum values. To get the reversers: Tab "Buttons" (you need the virtual buttons of the TCA enabled), bind to Keys, set one quadrant thruster to max reverse and bind to F2 (option repeat checked) and for the option release button bind to F1. You can bind both reversers to F2 which is not necessary, but i did it anyway. You could also try and bind the reversers with FSX itself or LINDA. I did not try. I cannot guarantee if it works.

 

Last step is to bind the switches etc. with LINDA. But you can easily find out yourself how this works!

 

I hope i could help some of you!

Happy landings!

 

Victor

 

Edit: I forgot to mention, that a Target Script or the Profiles fom the Target GUI create a virtual Joystick with an obvious name and they hide the Name of your Quadrant and also your Sidestick if you happen to include it in the profile/script. Also do not forget to delete all default FSX Axis and Button assignments. The virtual buttons would otherwise cause weird behaviors like gear up, change of view and so on! Also the target script (always start this the very first) and LINDA need to run in the background of the flightsim!

Link to comment
Share on other sites

  • 1 month later...
  • 3 weeks later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use