Tir5 True View

[Kobradelta1000]

I don´t really know, its a bug or are the invisible walls too close to the head in the cockpits-

But True view definitely doesnt work (anymore?)

So for example in the Mig15 i look to the right wing- then move with my (real) head forward (to the monitor) to get my game head closer to the canopys (right) glass- instead my game head moves to the front of the cockpit (so, it is left for my game head)- so no true view... or am i sliding on the invisible cockpit wall to the left?

 

 

UPDATE & solution

all Credits goes to PiedDroit- Thank you very much!

If you feel that your true view doesn´t work as expected, try these diff. settings=

 

I have tested all the modules except the M2000 & Albatros which i haven´t

 

Play around with your Tir5 yaw axis saturation (Y) in each DCSW modules axis controls, the settings who will work best are in the range between 75% to 43% saturation.

Some modules like the mi8 work ok out of the box, but with your Y axis set to 60% it feels better- at least for me.

 

Thanks again to the clever community here- what would be, if developers wouldn´t have such intelligent fans around, who care and support customers of ED without $$ in their mind!

Edited January 10, 2016 by Kobradelta1000
Solution

[Kobradelta1000]

..no one? :-(

[HiJack]

Check your axis assignments

[Kobradelta1000]

they are okay...

or should i unbind all the axis to become native supported with true view? hm...

[Sryan]

that's just not how it works. you need to lean over to right, over your shoulder and then turn your head to do what you describe. you can fiddle with the X value in tha TiR software to set how much you need to lean.

[PiedDroit]

So for example in the Mig15 i look to the right wing- then move with my (real) head forward (to the monitor) to get my game head closer to the canopys (right) glass- instead my game head moves to the front of the cockpit (so, it is left for my game head)- so no true view... or am i sliding on the invisible cockpit wall to the left?

This indeed looks like True View is not enabled, you will be ables to solve it in TrackIR software. Redo the same movements and check the output values.

 

EDIT: I did some tests and it looks like I have the same thing. Roll inversion works as expected but not translation, I'm looking into it now

 

they are okay...

or should i unbind all the axis to become native supported with true view? hm...

If anything, this has nothing to do with True View, True View is only a way to translate your head movement to trackIR outputs (x, y, z, pitch, roll, yaw).

DCS doesn't know that you're using TrueView or not, it's only seeing x, y, z, pitch, roll, yaw values.

 

You need to check your TrackIR outputs using the TrackIR software and see if there's a limitation there.

Maybe your camera is not seeing the reflector (or the clip) well enough and the movement stops in certain body positions.

This might happen if

- the camera is not placed high enough

- the camera is not oriented properly

- your body unmasks an interfering light source

Edited January 1, 2016 by PiedDroit

[Kobradelta1000]

Thanks got it!

Sryan pointed me in the right direction... i shortly updated to the new software (5.3)

There was a glitch in loading my old profile- made a new one and true view seems to work now!!

 

UPDATE Definitely a bug on some planes!

Will test PietDroit´s calibration

 

Thank you guys !

Happy 2016!!

Edited January 4, 2016 by Kobradelta1000

[PiedDroit]

Okay, I got it. It's a DCS axis calibration issue.

When moving my DCS view to 90° to the right, my TrackIR software thinks it's transmitting 35°.

So, the trackIR output is correct but DCS is exagerating movement. When moving my real head forward, I get mostly forward in game movement and a little lateral movement, because TrackIR thinks the in-game head is turned 35°, not 90°

What needs to be done to get True View working is to calibrate TrackIR axis so when the in-game heads is at 90°, trackIR output is also 90°.

 

I'll do that calibration and come back.

EDIT:Added screenshot to illustrate this

Edited January 1, 2016 by PiedDroit

[PiedDroit]

Hello, here's the correct calibration value for TRACKIR_YAW: saturation Y = 43

 

With this value I got an in-game angle that is the same as TrackIR output angle and now TrueView works as expected.

I don't know if re-creating a profile changed anything for you, I'd be curious to hear your test results about that.

[Kobradelta1000]

Hello, here's the correct calibration value for TRACKIR_YAW: saturation Y = 43

 

With this value I got an in-game angle that is the same as TrackIR output angle and now TrueView works as expected.

I don't know if re-creating a profile changed anything for you, I'd be curious to hear your test results about that.

 

 

Sorry PiedDroit!!, will report back as soon i am back

Thnx for your effort to help!

Edited January 4, 2016 by Kobradelta1000

[Kobradelta1000]

Conclusion to this issue see 1st post!

http://forums.eagle.ru/showpost.php?p=2623674&postcount=1

[PiedDroit]

:thumbup:

Other axis can be tweaked the same way (but are less important for True View), what worked for me is:

TRACKIR_YAW: saturation Y = 43

TRACKIR_ROLL: saturation X = 49

 

Of course you need to adjust the gains in you TrackIR profile after that.