Originally posted by Balsy
Mace,
What is "trueview" and what is it supposed to do?
Balsy
Trueview is supposed to correct the problem that some have been having with the translation axis that I discussed
here . According to NaturalPoint that's all it does.
In a nutshell the translation axis are either "locked" to the centerline (CL) of the airplane or are "locked" to your direction of view. When locked to CL whenever you move your RL head to the left the virtual head ALWAYS moves to the left side of the
cockpit regardless of the actual direction you're looking. With the axis locked to the direction of view your movements are always relative to what you're seeing on the monitor. I have never been able to figure out why someone would want the translation axis locked to the CL because it completely dorks up the natural movement when facing any direction but straight ahead.
I haven't been able to figure out why, but there are some who complain that the "defaut" translation axis are locked to CL. This is not the case with my system, mine has always been locked to my view direction. Whichever way your system is the Trueview feature reverses it so if your axis are locked to CL then turning Trueview ON will switch the axis to your direction of view. In my case, turning Trueview ON switches me from direction of view to locked to CL.
It gets more complicated. AH has the "TrackIR Object Relative Move" function which is selected from the view options menu. TrackIR ORM does
almost exactly the same thing as Truview does. If you're locked to CL you can turn ORM on and you're now locked to direction of view, and visa versa. So, in my case, if I have Trueview ON my axis are dorked so then I turn ORM ON and it corrects it back. Got it? That's why I operate with both "features" turned OFF since they're both just canceling each other out. One last complication. I mentioned ORM is "almost" exactly the same as Trueview. Where it differs is that to me, ORM appears to cancel out the new virtual head pivot point that is the main reason for .029 and you lose the more natural movement. In other words instead of having the pivot point at the neck it is back where it always has been which is the center of the head.
My recommendation if you're going to try out .029 is to make sure that both Trueview and TrackIR ORM are turned OFF when you first start. I'd be real curious to hear if your axis are correct or not. If your axis are wrong then switch JUST Trueview ON, that should fix it and you'll still have the new pivot points. I can't see any reason to ever have TrackIR ORM on.
So if you end up running with Trueview and ORM both off what's the point of .029? There are a few changes including the new pivot points and movement algorythms, and they've done a few housekeeping changes (you can chose to disable the warning when you attempt to shut down TIR for instance). The other significant change is that it'll support the new Track Clip Pro which replaces the three vector expansion reflectors.
Last, I flew with .029 quite a bit last night and it definently is more stable than the previous alpha version. The only problem seems to be that if you look down for too long it'll lose track and your view will snap straight down. A quick "recenter" is all that's needed to correct the problem so it's little more than an annoyance.
