FacetracknoIR 170 in DCSW

[Gavski1]

I'm having problems getting FTnoIR working in DCSW.

I Installed CL driver (for my ps3 eye) works

Installed FTnoIR v170 works

 

(I have assetto corsa car sim and this works fine, no dll's or anything).

 

In DCSW I now have a settings column that says virtual joy..... (or something) and it seems the views are assigned to this but when I run the sim there is no head movement.

 

I have searched for answers but a lot of stuff refers to stand alone A10c or older V's of facetrack.

I have seen threads that suggest a headtracker.dll in the bin file but I have no headtracker.dll ??

 

My setup

win 7 pro

I5 2400

Radeon 7870

 

also use a gravis eliminator joystick - (not ideal but works fine in DCSW.)

 

I'm new to DCSW have FC3 and Sabre F86-F help to get me up and running appreciated.

[Gavski1]

I'm kind of answering my own question in the hope it may help someone else?

 

Finally got it working ok, after downloading the Headtracker.dll for the A10-c I was instructed to put it in a sub folder dcsw\bin\headtracker\ but this did not work.

I then read someone elses post and they had put a copy of the headtracker.dll file in the main bin directory dcsw\bin\ So I tried this and it worked. :)

 

I now have another problem. It works in all my FC3 planes and the stock Mustang and SU25 but not with F86 Sabre?

 

Anyone got an answer to this? perhaps I need a separate .dll file for the Sabre?

[Zibell]

In 1.70 you don't need the headtracker.dll anymore. Just select FreeTrack 2.0 under game protocol, go to settings, check start dummy TrackIR.exe, and under Select Interface, choose use TrackIR, hide FreeTrack. Be sure to adjust the curves ingame.

 

Also, anyone losing track after the first mission? I always have to restart the game for it to work again.

[julian265]

I use FTNIR 170, however I do not use any special protocols - but rather manually assign the axes in each DCS module using the vjoy emulated controller from FTNIR.

 

Zibell, I don't need to restart anything using this method.

 

I can give more details if required.

[Gavski1]

I use FTNIR 170, however I do not use any special protocols - but rather manually assign the axes in each DCS module using the vjoy emulated controller from FTNIR.

 

Zibell, I don't need to restart anything using this method.

 

I can give more details if required.

 

I'd like to know the Axis settings you apply to vjoy.

 

When I removed the Headtracker.dll file from my bin directory (as above post) FTNIR stopped working so I had to put it back again, all is working again except F86 Sabre?

 

Maybe if I can assign them in vjoy it may work.

 

Cheers

[Gavski1]

Fix for this - a known bug

 

Fixed it.

 

Go to the

 

\Eagle Dynamics\DCS World OpenBeta\Mods\aircrafts\TF-51D\Input\TF-51D\headtracker

 

folder and copy the default.ini file found there. Then go to

 

\Eagle Dynamics\DCS World OpenBeta\Mods\aircrafts\F-86\Input\F-86F\headtracker

 

and paste the copied file, replacing the older default.ini file.

 

Still need headtracker.dll in \bin directory but who cares.

[Knowlynn]

Also, anyone losing track after the first mission? I always have to restart the game for it to work again.

 

I've had this problem before. I thought putting headtracker.dll in the right spot fixed it but I'm not really to sure. Whenever the problem went away I rejoiced and forgot what exactly I did.

 

Thinking back, it's either the headtracker.dll or adjusting the Freetrack settings. Maybe play around with use/hide trackir/freetrack. If I remember correctly, one of them might only work for 1 mission. My Freetrack settings are the same as yours so maybe I solved the problem with a clean install.

 

Good Luck!

 

EDIT: Sorry, I was looking at my arma3 settings. For dcs I uncheck start dummy trackir.exe and use freetrack/hide trackir.

Edited December 10, 2014 by Knowlynn

[Zibell]

Hotfix1 for version 170 fixes the losing track bug ;)