1) A/T sync options for controllers without servos...

 

I am using a Rhino X55 joystick and so, my throttles are far from what a good model of Boeing airliner throttle quadrant should be. I have this limitation when using both FSX and PSX.

 

Well, until recently I decided that "IN HOLD MODE ONLY" was the right option for me, but both during takeoff and during descents, when the A/T system sets the mode to HOLD, I often forget to have my hardware throttle properly synced to it... although I also have enabled the "SHOW THRUST LEVER POS" option.

 

So... I started using "NEVER" instead, and it does look better because when the system setts the A/T into HOLD mode I can still use the F2 / F3 keys ( or whatever alternative keys I have programmed ), to 

make my adjustments, specially in VNAV SPD if I want to use adjust my rate of descent by increasing / decreasing throttle.

 

Of course, if I switch the A/T system off altogether, I will be able, again, to make full use of my controller, right ?

 

What are you using, and why ?  ANy comments / suggestions appreciated, specially for those not luck enough to own a servo-controlled throttle quadrant

 

2) Joystick FBW null zone options...

 

I didn't get the idea behind this new option very well. I haven't touched these options, and I assume the zones will thus default to NULL, but I also do not experience problems hand-flying the aircraft because,

after manually trimming, I give way to my joystick, releasing it to the central position, and only after a couple of seconds get my hands back on it when the system has already intervened to adjust for the new trim setting. 

 

Am I interpreting this option in the wrong way ?

I use "IN HOLD MODE" override and "SHOW WHEN MOVING" for position.  Remember to return your throttle controller to idle before reaching 80 KIAS and the thrust mode changes to HOLD.

 

Null zone is simple, it is a "dead zone" where movement of the control does nothing.  Handy when your controller is a little sloppy, for example at neutral if slight unintentional movement is causing problems then increase null zone to eliminate this from happening.  On the other hand, a null zone too large will result in an unnatural response to control movement. It's a very individual preference.