At the end of the day. How does it feel at this new setting?
I still haven’t gotten to the update to see it for myself.
Is it completely eliminated at 100? So super responsive to head movement?
I would agree. This seemed the logical decision. I guess we have to form, yet another, wishlist item.
Personally I think it’s much better than the previous beta. The laziness effect is certainly gone, at least.
Haven’t had time to actually get in the air and do some circuits but at first blush the new default is very responsive. However I’m not finding it difficult to hold my view steady to fiddle with dials and switches.
Adjusting the Camera Boost Ratio seems to mellow out this responsiveness without re-introducing any laziness.
My guess is that somewhere in the code Head Tracking Responsiveness and Camera Boost Ratio are multiplied. When HTR was only 0.5, the CBR only had half the intended effect.
Again, speaking only for myself, I can definitely live with this current situation and overall the performance is very good and feels smoother than SU4. But I can also see where other people may not be as happy.
I don’t want to suggest a middle-ground number because I’m afraid that will become to new default 
IMO a proper solution is to introduce a slider. Maybe that will come later? 
Exactly this. The laziness/dampening effect seems to have gone now, I had to turn the camera boost right down. Overall, very happy after a first test flight.
I am glad to hear this got somehow resolved that quickly.
Even if it is not the perfect solution. As long as it is working that is all I could hope for.
Kudos to MS/Asobo taking quick action! Thx
OK! After spending the morning doing some patterns and then off to the neighbouring airstrip for a $100 breakfast (more like $200 these days!) I have to say that I’m very, very happy with the performance of MSFS’s native Tobii headtracking.
Any complaints I could have are either a “me” thing or I’m just being picky for the sake of being picky.
A theory I came up last night is that maybe the settings.HeadTrackingRotationResponsiveness variable was always supposed to be 1 and not necessarily user-facing, and the other settings are the modifiers that are applied over top of that?
Regardless, I’m very pleased with how SU5 v1.7.21.0 is performing and I consider this issue solved.
This is great news! I still have yet to get to the sim since the build was released.
Soon…
I appreciate how involved you were in helping get this issue sorted. Your contributions were invaluable.
I was wrong and I’m sorry, thank you team for fixing this!
This Tobii implementation is really good now.
I finally got a moment to sit down with the latest build and, indeed, Tobii has the responsiveness it had in SUs past, without the noted lag.
I appreciate the responsiveness (see what I did there) of the CMs & development team in helping get this resolved.
Still playing around with my settings a bit. Could those who are really happy with their settings share them here please? I’d like to compare 
Did you try these from @rottenbk ? You may want to reduce/zero Camera Boost Ratio (ignore all the dev mode business):
These were what I started with, but I have been experimenting with @rottenbk ‘s settings, too:
IMO other people’s settings are a ok place to begin if you have no idea where to start but getting it working it’s best for you will depend on many factors:
Fortunately we now have a decent set of tools to make these adjustments!
Great news! I am soooo happy, that my Tobii is fixed plus some tweaking possibilities
cheers, I’ll go play around
edit: and, got it back to where I loved it. Thanks for the fix.
TBH, i just find it very jerky now and over-responsive. For me, 0.700 responsiveness was perfect !
Why not to simply add this value to the controls and give us an extra fine tuning tool ?
Or it least make the setting on the dev tool save the selection between restarts.
I understand that the current fix was the easiset, but still…
did you reduce the ‘camera boost ratio’? I’ve set it to 0, and it works well for me.
Yes, set it to 0. It doesn’t affect the responsiveness and twitchiness.
Now the issue is that when trying to compensate for this, i reduce the yaw/pitch sens, which in return limits the amount of movement.
I dont get why to limit the options which are possible with the device.
Please Asobo, add this setting with the others so we can save the value we like… and it will be perfect.
