Saitek X55, TrackIR and Centered Views

[KpgQuop]

Hello Everybody and a Happy New Year to all!

 

Does anybody use the X55 Rhino hotas and TrackIR? Do you also use Centered Quick Views? If so, how did you set them up?

I have everything laid out on the keyboard, and all works fine with key presses, including TrackIR; but when I've mapped keys to buttons on the 55, the results are glitchy at best.

 

I'm aiming to map a couple of buttons to look back left/right.

 

Any insight into this would be much appreciated.

 

[Bando]

When TIR is active, you can't go to any other view in the cockpit (I believe).

In my install, if I'm flying around and hit some view key, the image "stutters" somewhat, but TIR remains in control, so looking back means turning my head.

[Jade_Monkey]

Like Bando said, I think they are incompatible with TrackIR.

 

I have the X55 and TIR5 and i cannot use these keys to look around.

 

Why would you anyways? that's why you got TIR in the first place, to look around with your head.

 

You might wanna try Pausing TIR (F10) and pressing the keys, but sounds like it's not worth it to me.

Edited January 5, 2016 by Jade_Monkey

[Fidelity]

The HAT switch on the joystick left of the castle switch should automatically be bound to views. I have the red eject button on the throttle bound to "center view".

 

I can hold down on the hat and it will look backwards. It overrides the TrackIR input while held. BOS is set to Quick Snap mode. I would have to look at my TrackIR profile as I have custom made it.

[Remontti]

I don't have X55 but X52 Pro. I can definetly use quick views with TrackIR. Why should it not work with X55 if does work with X52? For example I have bound a instrument view to one of my hat buttons. I just mapped one of the quick views to hat button, adjusted it with mouse and saved it with F10.

 

Could the camera mode (panning / snap views) have something to do with it? Try changing that in game.

[KpgQuop]

Thanks for the replies everybody. Much appreciated.

 

Can confirm that the keyboard presses - by default numpad 1 and 3 -  do interrupt TrackIR and send the view to the desired angle. Translating those into X55 button presses however is problematical. So problematical in fact that after a while of mingling with the various permutations the game loses the ESC function and I have to ALT TAB to get back to the desktop.

 

I know what you're saying Jade_Monkey, there doesn't seem much point. However, my gaming environment contains a number of reflective surfaces that I'm not permitted to remove. Moving my head back left/right exposes these.

 

There's a keyboard/button conflict happening somewhere; and now you mention it Remontti, it might have something to do with F10 . Any road, I'll mess around a bit more and let you know what I find out.

[KpgQuop]

Finally got it figured out. 

 

It appears that the X55 was registering an instant press and release for each button press, regardless of when the button was released. Consequently, centering return kicked in before head movement could be achieved. So, turning to the Saitek programming software, I created an "Advanced Command" to register a press and keep it pressed, releasing only when the button was released.

 

Now, I'd done this before whilst trying to find a solution, without success. This time however I ticked the two "Macro" boxes on the press and hold sections and didn't "Quantise Time" on the release section. What difference this made I don't know, but it worked.

 

Apologies for posting in the wrong forum Mods and thanks for moving it to a more appropriate one.

 

Thanks for all your replies and all the best for 2016.

Edited January 6, 2016 by KpgQuop

[F/JG300_Gruber]

Some stuffs about the x55

 

- If you use programing, be careful to not have a key repeated indefinitely. For example I'm using the band mode for the rotary 1 to control the left-right command of the autopilot. If I forget to bring back the rotary to centered position, it will lock some of the keyboard keys (I'm for instance losing the escape key)

- Go in your device manager in the USB controllers section and see if you have multiple instances of the same device with some of them incorrectly installed (the yellow triangle). Delete all unnecessary instances as they can mess up programing as well.

- Teamspeak messes up with with the X55 software when reading the joystick input. Go into the settings of TS and in the hotkeys settings, set input as "mouse and keyboard only" and then bind the keyboard hotkey to the joystick via programming. 

 

Those are some stuffs that took me a while to figure out and may or may not be related to your problem.

 

 

By the way I can still use the quick views in the game with the X55, but for all basic commands, I always map the joystick buttons directly in the game and use only 2 or 3 programmed keys for advanced stuffs. 

[KpgQuop]

Sage advice F/JG300_ Gruber. The infinite key used to drive me up the wall back in the day.

 

I've got my X55 running on mode1 for take-off /landing, mode2 for flight and combat - allows for things like brakes and machine guns to be mapped to the trigger without interfering with each other. Hardly realistic, but I don't have pedals.

 

On a side note, I really miss the rocker rudder on the X45. I thought it was the bee's.

 

On another side note, I also really miss the shift state ability in the older Saitek hardware and programming software. That was supremely useful.

 

Thanks again Gruber et al. Enlightening stuff.

 

Cheers!

Edited January 6, 2016 by KpgQuop