Lately I've been getting a lot of SDK errors (even from 2D panel) and the plane also becomes unresponsive. I have to keep hitting Reset Flight until everything works again.

 

Not sure if there's anything that can be done about it but I just wanted to say that I have this problem.

 

Since it started suddenly there's got to be a way to fix it though?

I've removed FS2Crew and NGX, then reinstalled NGX, NGX SP1c, and latest Fs2Crew and am still getting this unresponsive behavior.

 

I don't know which addon is responsible for this.

 

In case you're curious, here's what the abnormalities look like:

 

FD vertical guidance gets stuck

 

Vnav not complying with restrictions (just busted the MCP alt here)

 

Silly pressurization logic (taken at around FL240 here).

 

The reason I'm posting this here is because I can seem to trigger it when running FS2crew. From my tests: I ran NGX without FS2C for about an hour without any problems, vs about 30 minutes (another test was 14 minutes) with FS2C before the plane becomes unresponsive.

 

It used to work. Something is messed up somewhere--just wish I know what to reinstall!

Hi Preston,

 

If it started happening "suddenly", what did you change on your system between the time it worked and the time it didn't work?

 

Something is clearly messed up with your NGX as I haven't seen those issues before.

 

You might also want to ask the PMDG forum as they might have some insight.

 

Did you recently install any new programs?

 

Cheers,

Hi Bryan,

 

The newest thing on my system is Opus, but I've been running that for about 2 weeks before this shows up.

 

I uninstalled 1.4 and reinstalled 1.0 I saved when I bought FS2C. It's running the longest without this problem so far. Just for testing, do you think I could get a copy of the 1.3?

Same with me. If I start from cold and dark and run Pre-Flight everything powers up but the guages wont display current info. The Primary Flight Display and Navigation Display initialize when power comes on, but there is little info with everything highlited in Yellow. NO TCAS in yellow, no route showing in Nav Display, no airspeed and relevant info showing. Then I get the SDK errors, only sometimes however. If I start on runway with power, everything is fine. I did one flight each two nights in a row, and on the third night this stuff started happening. I uninstalled both 737 ngx and FS2Crew and reinstalled and it still happens. Weird as I had not installed anything during that period.

 

I will have to try cold and dark setup myself without FS2Crew and see if it still happens to try and narrow it down. I have not tried that yet.

Same with me. If I start from cold and dark and run Pre-Flight everything powers up but the guages wont display current info. The Primary Flight Display and Navigation Display initialize when power comes on, but there is little info with everything highlited in Yellow. NO TCAS in yellow, no route showing in Nav Display, no airspeed and relevant info showing.

 

Hi Preston,

 

I'd also fire off an email to PMDG Support regarding that.

 

Maybe they'll have some insight.

 

Sure you don't have some kind of IRS failure? Maybe clear all your failures.

 

Wish I had a better answer for you!

 

Cheers,

Hi Bryan,

 

Failures are not active.

 

I spent the entire weekend reinstalling FSX. I flew the NGX for at least 6 hours for each test and here's the result:

 

 

The good news is I've isolated the problem. The bad news is I don't know how to fix it

 

FSX (fresh install) + NGX = ok

FSX +NGX + Opus = ok

FSX + NGX + FS2Crew 1.4 = occasional unresponsiveness

 

I'm going to try FS2Crew 1.1 now...

Got it with 1.1 too, but when it got unresponsive the A/P "woke up" after a minute and corrected itself.

 

With FS2Crew, somewhere in the system, somehow, the A/P forgot that it was flying the plane (which always cause the pressurization to stop working, too).

 

Bryan, do you think I can try 1.3?

Now it won't work at all: starting FS2C (from 2D panel) doesn't give any indication of SDK error, but it's not interacting with NGX correctly (runaway MCP, values not being read, etc.)

I finally got the anomaly on recording. It was like trying to get Bigfoot on camera.

 

 

The A/P becomes either unresponsive or overcontrols the plane.

 

It starts with the A/P not keeping altitude

Neither F/D or A/P will follow the selected Heading Select mode

A/T not responding to Speed commands

F/D doesn't respond to the selected Level Change mode. A/T commands Retard but throttles do not respond.

LNAV reselected by the plane overshoots and overbanks

A/P misses the MCP commanded altitude. F/D responds by commanding nose up but A/P does not respond.

Selecting CMD B forces the plane to respond

Plane over responds to Level Change command

The elevator was stuck in extreme Up position

CMD B deselected to manually neutralize the elevator

CMD A reselected--no result

No control surfaces input by A/P

 

After this it eventually work and A/P regains control of the plane.

 

This happens nearly always about 1 hour after takeoff, and occurs again about 3-4 hours after takeoff.

 

This happens regardless of flightplan, aircraft variant or repaint, aircraft location, with weather or without.

 

No joysticks were plugged in. The only manual input given to the plane was at 2:43 via keyboard to neutralize the elevator.

Version 1.1 won't let you know if there's an SDK error.

 

I only added that check in later versions.

 

So that explains why there is no SDK error message yet FS2Crew isn't interfacing with the plane (because the SDK didn't connect properly).

 

 

Did you ever ask PMDG about this?

 

I'm afraid I don't have any ideas.

Hm, ok I'll ask them. I figure to ask you because this is exactly repeatable with FS2Crew running only.

 

I'm up to 1.4 now but can't seem to really use it.

Not sure if this may help but anything is worth a try. Do you ever defrag your hard drive? I recently began using Ultimate Defrag4 and in the beginning I didn't have that parameters set right. After a defrag run my FSX went haywire. Still ran but had numerous 'quirks' that were never there before. Reinstalled, reset my parameters and now she runs smooth as silk. Anyway, just some additional info. Good luck.

That section with the loss of control was probably worse than China Airlines Flight 006! Hope you find a solution.

Bryan et. al.,

 

Well bad news, this is PMDG support response:

 

"I have honestly never heard of any behavior like that from any other customers so i'm not sure what exactly the problem is. Unfortunately, since it only happens with FS2Crew, it is not something we can really do much to correct. Short of a clean install of FSX and the NGX and FS2Crew, I don't have any other recommendations that I could make. Brian would be the only one who could likely figure out what the issue might be."

 

Looks like I'm all alone :(