Breakthrough for Thrustmaster TPR Rudder users

[Baffin]

I've found the solution for Thrustmaster TPR Rudder users (and probably other brands) who have been unable to get Thrustmaster's T.A.R.G.E.T scripting software to recognize them when running a script for controller programming. The problem lies in the fact that the Warthog uses all the DX axes, leaving nowhere for the TPR's to go in TARGET scripts. Basically, this procedure eliminates the little used "Mini-Mouse" on the throttle to make room for the TPR Rudders. I am including a link to my source website strictly for attribution to the author, with the actual script changes following.

https://forums.eagle.ru/topic/187501-tm-tpr-issues/

-----------------------------------------------------------------

So far as I know were still limited to 8 axis per controller. A full set of warthog and pedals accounts for 10.

You probably don’t need to manage pedals through target but if you actually do...or want to... you have to sacrifice 2 other axes to use rudder and brakes.

I’m running a profile right now that sacrifices the microstick on the throttle.

First comment out these 2 lines as shown (assuming they're in your standard / default script to start with)



//MapAxis(&Throttle, SCX, DX_XROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);

//SetSCurve(&Throttle, SCX, 0, 0, 0, 0, 0);

//MapAxis(&Throttle, SCY, DX_YROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);

//SetSCurve(&Throttle, SCY, 0, 0, 0, 0, 0);



Then you can add in the rudder & brakes like this:



MapAxis(&TFRPHARudder, TFRPHA_RUDDER, DX_Z_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);

SetSCurve(&TFRPHARudder, TFRPHA_RUDDER, 0, 0, 0, 0, 0);



MapAxis(&TFRPHARudder, TFRPHA_RIGHT, DX_XROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);

SetSCurve(&TFRPHARudder, TFRPHA_RIGHT, 0, 0, 0, 0, 0);



MapAxis(&TFRPHARudder, TFRPHA_LEFT, DX_YROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);

SetSCurve(&TFRPHARudder, TFRPHA_LEFT, 0, 0, 0, 0, 0);



Note, my system uses RZ and Throttle for the throttles. You could substitute DX_THROTTLE_AXIS in for "DX_Z_AXIS" on the TFRPHA_RUDDER mapping.
--------------------------------------------------------

I hope this helps someone besides nerdy Baffin!

[RAF74_Buzzsaw]

Sorry, mistakenly disliked this post when I meant to like it.... thanks Baffin for your post.

I've found the solution for Thrustmaster TPR Rudder users (and probably other brands) who have been unable to get Thrustmaster's T.A.R.G.E.T scripting software to recognize them when running a script for controller programming. The problem lies in the fact that the Warthog uses all the DX axes, leaving nowhere for the TPR's to go in TARGET scripts. Basically, this procedure eliminates the little used "Mini-Mouse" on the throttle to make room for the TPR Rudders. I am including a link to my source website strictly for attribution to the author, with the actual script changes following.

https://forums.eagle.ru/topic/187501-tm-tpr-issues/

-----------------------------------------------------------------

So far as I know were still limited to 8 axis per controller. A full set of warthog and pedals accounts for 10.

You probably don’t need to manage pedals through target but if you actually do...or want to... you have to sacrifice 2 other axes to use rudder and brakes.

I’m running a profile right now that sacrifices the microstick on the throttle.

First comment out these 2 lines as shown (assuming they're in your standard / default script to start with)



//MapAxis(&Throttle, SCX, DX_XROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);

//SetSCurve(&Throttle, SCX, 0, 0, 0, 0, 0);

//MapAxis(&Throttle, SCY, DX_YROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);

//SetSCurve(&Throttle, SCY, 0, 0, 0, 0, 0);



Then you can add in the rudder & brakes like this:



MapAxis(&TFRPHARudder, TFRPHA_RUDDER, DX_Z_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);

SetSCurve(&TFRPHARudder, TFRPHA_RUDDER, 0, 0, 0, 0, 0);



MapAxis(&TFRPHARudder, TFRPHA_RIGHT, DX_XROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);

SetSCurve(&TFRPHARudder, TFRPHA_RIGHT, 0, 0, 0, 0, 0);



MapAxis(&TFRPHARudder, TFRPHA_LEFT, DX_YROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);

SetSCurve(&TFRPHARudder, TFRPHA_LEFT, 0, 0, 0, 0, 0);



Note, my system uses RZ and Throttle for the throttles. You could substitute DX_THROTTLE_AXIS in for "DX_Z_AXIS" on the TFRPHA_RUDDER mapping.
--------------------------------------------------------

I hope this helps someone besides nerdy Baffin!

[ATAG_Noofy]

Sorry, mistakenly disliked this post when I meant to like it.... thanks Baffin for your post.

Would it make any sense to separate further the thumb up and thumb down buttons?

[DerDa]

Would it make any sense to separate further the thumb up and thumb down buttons?

No!
I really 'liked' this post!
I did NOT mistakenly hit the 'like' button that is much too close to the 'dislike' button!
Honest!

[ATAG_Noofy]

No!
I really 'liked' this post!
I did NOT mistakenly hit the 'like' button that is much too close to the 'dislike' button!
Honest!

Frohe Weihnachten DerDa!
You still have good eyesight.
This is not the case for many of us, me included…

[Baffin]

Would it make any sense to separate further the thumb up and thumb down buttons?

Nah! It keeps life interesting! Happy New Year!

[DerDa]

You still have good eyesight.

Sadly not, not even as a child. That's why then I believed that flying airplanes would stay just a dream for me.

Well, thankfully there are some chaps around who keep dreams alive