Simple Pause TIR for Warthog??

[Elnocho3]

Hey everyone,

 

I've recently started flying DCS Warthog with the HOTAS warthog. It's obviously fantastic but with Track IR i've been getting a very stiff and painful neck from keeping my head so still. I've changed the track IR deadzone & response curves, but to no avail.

 

I would like to know if there is a SIMPLE way to assign the Track IR pause command to a button on the throttle??

 

I do not want to have to reprogram both the joystick and throttle in TARGET (and learn how to)......... I've just got flying again, the last thing I want to be doing is sitting on the ground, staring/swearing at code!

 

 

 

Thanks in advance!!

[Rhinox]

I would like to know if there is a SIMPLE way to assign the Track IR pause command to a button on the throttle?

Of course there is one method (as easy as assigning keybard button): simply plug in your THW (I recommend both joy and throttle), go to TIR profile editing, click "assign new button" (or something similar, I do not have it here) for "pause" and click desired joy-button. And instead of "F10" (or whatever it is in default settings) you will see something like "Joy8". TIR-software captures even joystick-keypresses, so there is no need first to assign some keyboard-key to joy-key. I did it this way some time ago when I was using x52, but it should work with any game-controller recognised as directx-peripherial (now I have THW and using TARGET, which imho is worth to learn!)...

Edited December 20, 2011 by Rhinox

[Elnocho3]

Thanks for the quick reply!! Very simple, lol - never used track IR itself to do those commands!

 

And I agree, I always scripted the Cougar but want to fly a bit before spending time with TARGET

[cichlidfan]

There isa gotcha with doing that. Since TIR does not seem to keep track of which device sent the input, if your joystick is plugged into different port or if there are other controllers plugged in, it can lose track of what button is supposed to control it.

 

Now if you never change what is plugged in where, it may work all the time but I found that I had to periodically go into TIR and reset the pause function key.

[Supersheep]

I used this myself for a time, but that way is not as good as it seems.

 

I started an own thread about my issue, where I learned that the TIR oftware does not distinguish same buttons on different devices.

 

Example:

I mapped TrackIR controls to the MIC switch no the Warthog throttle, and every time I hit the pickle button on the joystick, this triggered the TIR to freeze.

The buttons are all like JOY1...X on both parts of the HOTAS and TIR ignores this.

 

 

 

To circumvent that problem (there is no fix, TIR software is the issue), I mapped the TIR controls to the arrow keys on my keyboard, which I position so that it points away from me. Keeps it out of the way and and the ITR commands in reach.

 

 

 

 

EDIT:

Sniped?

I think the post above describes still another issue I have not experienced before...

/EDIT

 

 

 

HTH,

Supersheep

[PoleCat]

It is an absolute must to have both TIR center and pause on the HOTAS and in a good postion. This makes TIR a breeze and deadly effective. Without quick access to both of these functions, and I mean quick, you are at a disadvantage in all respects.....IMHO. I use the WH Joystick S4 paddle for Teamspeak push to talk, the WH Throttle slider for zoom, the mic switch press for pause TIR, and mic switch up for center TIR. Using these buttons still allows you to use the default config in A10-C as well.

 

Map it, learn it, use it or burn it. :)

 

Out

Edited December 20, 2011 by PoleCat

[Supersheep]

@PoleCat:

[Edit: Removed, factually incorrect]

 

 

Thanks,

Super-

Edited December 20, 2011 by Supersheep
Mistake

[cichlidfan]

 

 

 

EDIT:

Sniped?

I think the post above describes still another issue I have not experienced before...

/EDIT

Supersheep

 

The bottom line is that the TIR software could use a couple of tweaks. Recognizing the controller and not just the DX input and being able to tell a left shift from a right shift are both badly needed.

[PoleCat]

The bottom line is that the TIR software could use a couple of tweaks. Recognizing the controller and not just the DX input and being able to tell a left shift from a right shift are both badly needed.

 

Meh, as long as you can program a DX button or a keystroke it doesn't much matter to me. I have no issues with it at all. ;)

 

Out