TrackIR Output Differs in game

[stinkx]

Hello people,

 

I did some research on the forums and the net but i was not able to find an answer to my specific problem.

 

Here is the deal. I encountered this both in FreeTrack and TrackIR.

 

My real head (with real hair loss) yaws 15 degrees to left.

TrackIR (or FreeTrack) amplifies this to about 45 degrees of yaw to the left.

However the game reflects this as 90 degrees yaw to the left.

 

It seems there is a hidden multiplier between the tracking software and DCS. My curve for the trackir yaw axis in the game is the default 1:1 line going directly from bottom left to top right corner.

 

Now this is easy to spot and fix in yaw. You just set y saturation of trackir in game yaw axis to about fifty. However it is really hard to tell if the same condition exists on z axis for example.

 

Any ideas?

[PiedDroit]

You might have a different profile that is loaded by trackIR software when you start DCS (it's on the "title" tab, you can attach a different profile for each program).

To make sure that no other profile is loaded, click the "exclusive" button on the trackIR software, in the "profile" tab. This will tell TrackIR software to always use this profile regardless of the game running (this is unlikely to be your problem if you have it also with FreeTrack).

 

Also try to alt-tab while DCS is running to check if trackIR is still doing as you expect, this will help to know if the problem comes from the TrackIR software or from DCS.

 

Since you have the problem with TrackIR AND FreeTrack, this is probably a DCS problem.

 

EDIT: One last thing: I had the problem with facetracknoIR (I wrote freetrack before, see edit2), it replaced the dll path from natural point (in the registry) with it's own dll path.

I guess it was done because DCS is hardcoded to look for trackIR dlls.

Thre problem wasn't fixed by reinstalling TrackIR, I had to go in the registry to manually restore naturalpoint paths.

So maybe what you experience is due to DCS loading different dlls.

 

EDIT2: I just noticed that you were talking about freetrack but I had the problem with FaceTrackNoIR actually. Anyway I leave this here as it might be a clue.

Edited February 20, 2015 by PiedDroit

[stinkx]

I wrote FreeTrack before and did a mistake there i guess.

I was using FaceTrackNOIR in point track mode with a home made clip. So probably the dll path switching happened in my case as well.

 

Could you perhaps give me a quick and dirty explanation of the fix? I'm not so good with regedit.

 

Thanks in advance

[PiedDroit]

FaceTrackNoIR does not need a clip, so you've probably been using FreeTrack.

You can still check the dll path just in case (see below).

 

In my opinion the best thing to investigate at the moment is:

- Start DCS without TrackIR running (maybe you're not using it in DCS after all, if FreeTrack took precedence).

- Start DCS with TrackIR running, alt-tab and check what's happening in TrackIR (did the profile change? is the precision mode enabled?).

 

---------- FaceTrackNoIR dll fix ----------

 

In my case it was the "Path" key at (in regedit) HKEY_CURRENT_USER\Software\NaturalPoint\NaturalPoint\NPClientLocation that had been modified (its correct value should point to your TrackIR dll path, for example C:/Program Files (x86)/NaturalPoint/TrackIR5).

 

You must launch regedit.exe with the same user that launches DCS.

I spotted this using procmon.exe, I noticed that DCS was attempting to load FreeTrackNoIR dll instead of TrackIR dll (after I uninstalled FTNoIR :mad:).

Regedit is pretty easy to use so just make sure you don't delete or modify anything by mistake. Just start it with the correct user, navigate to the key above, check the value and if the path of "Path" if not good, double click to modify the key and exit.

Edited February 22, 2015 by PiedDroit

[stinkx]

Thanks a lot PiedDroit, for the detailed explanation mate. I was able to follow and quickly fix the problem.

In game movement is 1:1 to the TrackIR output now.

 

After the fix i also found this from FTNoir wiki. It seems they have a script built in for changing the dll path. For future references, you just need to click locate dll button in the image below (taken from: http://sourceforge.net/p/facetracknoir/wiki/FreeTrack20/ ) and switch to the C:/Program Files (x86)/NaturalPoint/TrackIR5 path for example.

 

[PiedDroit]

... After the fix i also found this from FTNoir wiki. It seems they have a script built in for changing the dll path. For future references, you just need to click locate dll button in the image below (taken from: http://sourceforge.net/p/facetracknoir/wiki/FreeTrack20/ ) and switch to the C:/Program Files (x86)/NaturalPoint/TrackIR5 path for example.

Ah! I wasn't aware of that, I already had uninstalled it to I didn't have anything left (the dll was not here anymore either so my tracking was not working at all) - this "dll restore" should be put in the uninstaller as well.

Thx for the info and glad you finally got your TrackIR back to normal ;)

[Shaman]

OP is right,

this TIR bug persist in game for ages!!! Implementation by ED has never been 1 to 1 with TIR driver output!!!

Please search for my former posts on these forums regarding TIR issue you noticed.

 

What you need to do is reduce saturation-Y from 100 to 64~44 (preference) for YAW/PITCH/ROLL

 

MODERATOR! PLEASE LET ED KNOW!

[PiedDroit]

Do you have a link about this bug?

Thinking about it, I never looked the virtual head in TrackIR software, to tune my TrackIR curves I check directly in DCS...

What is the exact saturation value you use to get a 1:1 response?

I'll make some tests about this, but, not now, no time :music_whistling: