Thanks again Pete for getting back to me. First of all I'd like to thank you for the wonderful work you've done for FS over the years.... I've haven't taken the opportunity to say anything before and since we're discussing this issue there's no better time than the present. Everyone in this hobby owes you a dept of gratitude for the wonders you've worked with FS over the years. I was happy to contribute financially to your efforts when you started charging for registered copies of your module. So again thanks so much, you are one of the key players that make this hobby so great.... :wink:
All that being said let's get back to the issue at hand. First off I know there is nothing going on with my CH Yoke/Peddles because I don't have this problem with any other aircraft. Anything related to USB would carry over into other things...
As far as resetting the trim, there is no way to do it in the air unless you shut the engines down which is not a good idea on a landing approach. Anything related to pitch control is a mute point once the autopilot is disconnected. Now the autopilot can still control pitch if I turned it back on so there is diffidently a problem with the autopilot disconnecting fully. Actually that's the best way to describe this problem, ‘The Autopilot Doesn't Fully Disconnect’....
As far as common differences between users I haven't found any. My setup is basically the standard setup. Some may have different controllers but overall there really is no difference that I've been able to ascertain (Dell 8300 P4 2.5gig, Radeon9800).
I haven't tested flying a route without using the MCDU. That’s a great suggestion that I'll have to look into soon as possible. I'm really leaning toward an MDCU problem. This is not an issue of short versus long flights but more so I think when a route is planned in the MCDU and flown using it. Once you get to your destination the autopilot doesn't want to let go. As far as the PSS A320 support :roll: , we are the support unfortunately.... That's why I give you so much credit in hanging in there with us. Some companies leave you hanging high and dry but still expect you to keep buying their products. That's another topic for another time sorry.... :roll:
There is trim indication in the cockpit of the A320, it just reads 8% down on the display... I know that’s not exactly how another gauge would read the trim but let's just say the time is maxed out in an attitude that would force the plane into an uncontrollable dive if it were in the air. The trim doesn’t max itself out like this until the wheels hit the ground. The A320 will perform autolandings correctly I’m happy to report… Like I said above the autopilot doesn't fully disconnect and in essence the plane is still trying to fly itself. It's like PSS designed this thing with two autopilots, one to control the Horizontal axis and another to control the Vertical axis. Problem is, one of those autopilots doesn't turn off with the off switch in the cockpit...
Last but not least this has happened for me since FS2k4 was released. It has nothing to do with the FSUIPC version. I wrote PSS on this a number of times in the past and once was told it would be fixed with the upcoming patch at the time. That didn't happen so I shelved the package only to find no one else releasing a payware quality A320. I began using the aircraft again hoping PSS patched some more things up but that was not the case. Now they flat out refuse to support the product anymore. I'd hate to give up on such a nice add-on that I've enjoyed over the years and besides the issue I have here, this package still shines and there are no other problems. I'm just exhausting all options before I delete this product forever..... :cry:
P.S. José, I have the CH Control Panel installed (control wouldn't work right without it)... Thanks for the advice anyway.
