Hi Preston,

 

There's something weird on your system.

 

PMDG can't explain it.

 

I can't explain it either.

 

We have 1000's of happy NGX customers... this is one we haven't seen before.

 

You might just have to do a clean install of FSX.

 

Something is clearly bungled somewhere.

 

Wish I had a better answer.

This would be the second time I done that. The video shown is from a newly formatted FSX drive with bare minimum of addons.

 

Which means the change is outside of FSX? Something in Windows? I guess that's the next step: wipe out windows--both of them, since I dual boot.

Now you've got an excuse to get Windows 8... and do a clean install.

 

My guess is something on your system is mucking with Simconnect...

 

What it is... who knows...

Just to second what Bryan has said,

 

With your explinations, including the vnav behaviour on your second picture. It honestly does not look like something FS2crew related.

 

A vnav bust [FL 200] as on your screen is an autopilot and FMC function. Fs2crew does not control the vnav.

 

I would second what Bryan suggested with a clean install. I think it is the only way forward as I am 99% sure it is not something FS2Crew related.

 

Please keep us posted on your progress!

 

Alex

I think I've solved the A/P. If you're curious: it was the BIOS clock failing to keep correct time. I've corrected it (somehow) and with a working and correct clock, the NGX flies smoothly. There were a lot of reformatting, cussing, and drinks on the road to solution (I'm sure you understand).

 

I can't imagine what impact the clock has on FSX and its addons, but, there it is.

There were a lot of reformatting, cussing, and drinks on the road to solution (I'm sure you understand).

 

Glad you got it sorted!

 

We've all been there B)