TrackIR Behavior with 1.5.4 Release

[wilbur81]

You don't have a light source behind you?

 

Sent from my SAMSUNG-SM-N910A using Tapatalk

 

Not really...And I never had any problems before 1.5.4 setting changes. Do you not have this problem? Have you tried it in the F-15C?

[SkateZilla]

I'm glad that the old TrackIR performance is back in place. I did adjust TrackIR axis curves to take the limits all the way out the the horizontal (left & right) limits.

 

When I Pause TrackIR and when glancing around at the limits I see many many upper right messages about Head Tracking Disabled, or TrickIR Disconnected or whatever it says. These messages are false.

 

WC

 

I assume,

These Messages will appear when TrackIR Software loses tracking and doesn't send data to the DCS Interface.

 

The only time they show for me is:

-When I re-load a mission Just before cockpit is loaded

-When I pause TrackIR software

-When I move out of bounds

-When something (my arm, light source, etc interferes with tracking points).

[MagnumHB]

I haven't had a chance to thoroughly test the newest version, but from what I have seen so far, I do want to express my appreciation for the feedback in this thread being listened to and the default view angle being taken account in the latest patch.

 

That being said, I did notice some odd behavior that is most likely related to the orientation flipping that others are reporting. If I turn left or right to the limit to look behind me, the view will pause at the normal limit as in earlier versions, then suddenly snap to an offset position as if I had turned in the other direction. For example, if I turn all the way to the left, the view will suddenly snap to the position (give or take) that the view would be if I had turned all the way to the right, and vice versa.

 

Edit: After more closely reading the other thread about this issue, it's possible that the image is in fact being flipped, but I haven't had a chance to check this yet.

Edited July 19, 2016 by MagnumHB

[Fred00]

I get strange TrackIR behavior in version 1.5.4.54855. Head movement in for example the A-10C is quite sluggish to a point where I would have to adjust the curves to compensate. However, the M-2000C is just as snappy as before. Why is there such a big difference between modules (there hasn't been before)?

 

Also, when switching between aircraft TrackIR stops working and the game has to be restarted.

[SkateZilla]

I get strange TrackIR behavior in version 1.5.4.54855. Head movement in for example the A-10C is quite sluggish to a point where I would have to adjust the curves to compensate. However, the M-2000C is just as snappy as before. Why is there such a big difference between modules (there hasn't been before)?

 

Also, when switching between aircraft TrackIR stops working and the game has to be restarted.

 

3rd party Modules havent been updated to use the new Interface.

[mondaysoff]

3rd party Modules havent been updated to use the new Interface.

 

So, is this why I have no TIR movement internally and externally in the Gazelle/Hawk and Aviojet since the last update?

 

Huey, Mi-8, Sabre and all my other modules are fine.

 

Edit: I will also add to this, apart from the absence of TIR in the three modules I mentioned, there were also no keyboard commands working to move the view either.

Edited July 20, 2016 by mondaysoff
Added additional problem.

[theropod]

So, is this why I have no TIR movement internally and externally in the Gazelle/Hawk and Aviojet since the last update?

 

Huey, Mi-8, Sabre and all my other modules are fine.

 

same for mig-21, it has no TIR movement

[firmek]

3rd party Modules havent been updated to use the new Interface.

Can we get a list of those modules. No bad intention to point a finger at anyone but just to avoid guessing in case of issues and overall confusion.

[*Rage*]

Am I mssing something or is trackir cockpit zoom not working (axis highlighted in red in the configurator)?

[SkateZilla]

which Aircraft?

[*Rage*]

Su-27 for one...Will test the other now...

[*Rage*]

Nevermind. Seems to work now...

[Winston 60]

Am I mssing something or is trackir cockpit zoom not working (axis highlighted in red in the configurator)?

I had this axis in "red" in all my modules since the initial 1.5.4 release patch. I solved it by highlighting the TrackIR Z axis box and selecting "default". That was the only way I could get the Z axis to work. The "red" highlight was gone after a DCS restart. I had to do this on all modules.

[SkateZilla]

Can we get a list of those modules. No bad intention to point a finger at anyone but just to avoid guessing in case of issues and overall confusion.

 

 

AFAIK, The 3rd Party Aircraft May or May not have updated Headtracking Controllers Setup,

 

 

So Far from What I can See:

 

VEAO Hawk uses Old Controller

AvioDev C-101 uses Old Controller

Leatherneck MiG-21 uses Old Controller

RazBAM M-2000C uses Old Controller

Polychop SA-342 uses Old Controller

 

 

If you wish to use the new controller, you can likely delete the /TrackIr/ folder in the aircrafts Input folder.

// /Mods/Aircraft/<aircraft>/Input/<aircraft>/

[jjohnson241]

AFAIK, The 3rd Party Aircraft May or May not have updated Headtracking Controllers Setup,

 

 

So Far from What I can See:

 

VEAO Hawk uses Old Controller

AvioDev C-101 uses Old Controller

Leatherneck MiG-21 uses Old Controller

RazBAM M-2000C uses Old Controller

Polychop SA-342 uses Old Controller

 

 

If you wish to use the new controller, you can likely delete the /TrackIr/ folder in the aircrafts Input folder.

// /Mods/Aircraft/<aircraft>/Input/<aircraft>/

 

I too had no TIR movement in the aircraft listed above (I don't own the Gazelle) in both the BETA and Stable releases. I had to delete the aircraft from Config/Input in Saved Games then reassign the controller options.

I don't know what's causing the TIR problem but I had the same thing happen after the last update to 1.5.4. Is the fact that these aircraft have not been updated to the new TIR setup causing this problem?

[Wrecking Crew]

I assume,

These Messages will appear when TrackIR Software loses tracking and doesn't send data to the DCS Interface.

 

The only time they show for me is:

-When I re-load a mission Just before cockpit is loaded

-When I pause TrackIR software

-When I move out of bounds

-When something (my arm, light source, etc interferes with tracking points).

 

Yeah, Skate, me too :)

 

Really, I don't need a message about exceeding the limits because the view stops, and I don't need a message when TrackIR is Paused because the lights on it turn red. The DCS messages are a distraction.

 

WC

[escaner]

Hey, gents.

 

Anyone else have the problem of track ir view flipping 180 deg when looking (pitch) up or down to the limit in the cockpit? For example: you look far enough down in your lap, and the view suddenly (instead of stopping the view and correctly simulating a person's neck restriction) is from the instrument panel looking back. More importantly, when dogfighting and looking up as far as the neck and should seat allow in real life, the camera has the same behavior, and suddenly the pilot has his head on backwards.

 

It seems like there needs to be a view restriction with the new trackir settings that better simulates the actual human head and neck movement stopping points.

 

Wilbur, when your views do that, it means that your trackir has lost your clip. The new driver has less magnification in the movement, so you need to exaggerate it with your head to reach some areas. Then the clip leaves trackir tracking region and DCS views do those weird things.

 

I had only flown the A-10C since the fix and trackir felt a bit sliggish, but had lots of problems with the F-15 tonight, the view got stuck each time I transitioned between fwd and back views in dogfight, because my left/up and right/up diagonals were out of tracking range. Then reverted once more to the old driver and all was fine again, and really notice the difference between the two drivers.

 

So I am sticking with the old driver. It is either that or reconfigure trackir curves to increase the magnitude, which seems stupid to me because they work just fine with my other three flight simulators.

[SkateZilla]

Wilbur, when your views do that, it means that your trackir has lost your clip. The new driver has less magnification in the movement, so you need to exaggerate it with your head to reach some areas. Then the clip leaves trackir tracking region and DCS views do those weird things.

 

I had only flown the A-10C since the fix and trackir felt a bit sliggish, but had lots of problems with the F-15 tonight, the view got stuck each time I transitioned between fwd and back views in dogfight, because my left/up and right/up diagonals were out of tracking range. Then reverted once more to the old driver and all was fine again, and really notice the difference between the two drivers.

 

So I am sticking with the old driver. It is either that or reconfigure trackir curves to increase the magnitude, which seems stupid to me because they work just fine with my other three flight simulators.

 

There is an actual DCS bug where the axis flips when exceeding +90 or -90 degrees on the vertical axis.

 

Ive tested it with steep curves and shallow ones intentionally to make sure I wasnt losing tracking.

[Coug4r]

Funny thing is, this 'oversteering' also happens in the Mirage. May or may not be related. If you steer fully left while on the ground and start taxiing you go right. Thought it was the Mirage but it also happens in the F-5. It's almost as if they used a different value for PI in all their calculations since v1.5.4.

[SkateZilla]

Funny thing is, this 'oversteering' also happens in the Mirage. May or may not be related. If you steer fully left while on the ground and start taxiing you go right. Thought it was the Mirage but it also happens in the F-5. It's almost as if they used a different value for PI in all their calculations since v1.5.4.

 

umm wrong thread.?

[Coug4r]

No, the steering also flips.

[SkateZilla]

steering has nothing to do with with the TrackIR Commands or controllers

 

please open a separate thread with tracks tc as its a separate issue.

[Coug4r]

No, i don't care about the steering or TrackIR.. i just noticed a link here.

[SkateZilla]

No, i don't care about the steering or TrackIR.. i just noticed a link here.

 

So you noticed a possible bug, but dont wanna report any info?

[Coug4r]

I'm reporting it here so the devs may see a link as well, they're both inputs with the same behaviour.