You aren't using a joystick or yoke or whatever, maybe configured with FSUIPC?....
That could be the culprit.... as FSUIPC is tampering directly into memoryareas etc. I've heard of people getting inot all kind of troubles when calibrating their "sticks" with one version of FSUIPC and then it goes heywire when the next version comes out :roll:
Personally I'm not too much pro-fsuipc, but that's only my personal oppinion.
I only use it because of FLYNet.....
Best Rgds
Dan
Who's General Failure, and why is he reading my harddisk?
Then I'm more than sorry to say, that you probably are on your own! .... Bugger!
One last resort though....
Try to zip up your whole folder structure including all necessary files (not all the textures) and send it to me... that's the last thing I can offer, otherwise I'm baffled!
dan DOT k DOT hansen AT mail DOT dk
Best Rgds
Dan
Who's General Failure, and why is he reading my harddisk?
I'll mail you before I send anything over. Before this, I think I'll take all the VC10 out of FS9, then do a defrag. It seems lile it's one command that doesn't behave - otherwise the aircraft handles perfectly.
I installed my altitude Concorde last night. After restart, FS9 refused to start saying FSUIPC was not compatible with this version of FS9.
I downloaded the latest FSUIPC and installed, fired FS9 up and had a play with the Concorde....
Just now, I loaded up G-ARVM for a play - and lo and behold, the autopilot is functioning perfectly. A blast up to FL250 and as I passed the coast I set her at 500fpm climb via the datum...
Maybe the old FSUIPC was to blame.....? In any event, a big wooohooooooooooo!!!! :drinkers:
:roll: 
