I re-downloaded the New NGX v1.10.6436 full installer to pick up the new updates since there is no incremental installer.  This version supports steam and classic FSX and includes the new weather radar if you have Active Sky Next installed.  Unfortunately it appears that FS2 is not compatible and I am informed at start up to seek support here at FS2Crew.

 

Anyway, I know it is hard to keep up with all the changes, but do you know if I need to uninstall FS2 and wait until there is a compatible installer for FS2Crew?

 

Please advise, soonest.

 

 

Joe

I installed Emergency and I don't get the warning in the cabin but now get CTD.  I also get the warning after install that I need to have SP1C installed.  The new installer is a new FULL install and includes all the updates. 

 

Help appreciated.

 

JP

The NGX Version of FS2Crew doesn't *officially* work with the new NGX Update, although some (including myself) have it working with Prepar3D. There are a few posts in this forum from people saying they have it working (much to the surprise of Bryan York the developer!)

 

If you're really having a lot of problems at the moment, just be safe in the knowledge that FS2Crew are working on a 'reboot' of the NGX version that will fully support the NGX new features which should be available "Soon"

 

(It's a paid upgrade btw, with discount available to customers)

I uninstalled FS2Crew, the 600-700, and the 800-900 base pack, then installed SP1D in reverse order, FS2Crew last. Ignored the SP1C warning and it has worked fine. Others have reported the same.

Thanks guys, I know that Bryan will be on it,(always is) and I will struggle thru it and give it another go.  I installed the new full PMDG (SP1d) installer over the old NGX install, uninstalled FS2 and then installed the FS2 NGX then FS2 Emergency.  I just keep getting the 1c warning, ignore it.  Now I will start all over and see if I can get it to work.  The CTD's now are concerning.

 

thanks for the feedback.

 

Joe 

I installed the new full PMDG (SP1d) installer over the old NGX install, uninstalled FS2 and then installed the FS2 NGX then FS2 Emergency

 

Have you made your own panel states  at all?

yes, but were for another paint that i deleted when i used the new NGX installer to update the 737NGX

 

 

I uninstalled FS2Crew, the 600-700, and the 800-900 base pack, then installed SP1D in reverse order, FS2Crew last. Ignored the SP1C warning and it has worked fine. Others have reported the same.

 

Correct, the SP1C warning can be ignored.

 

I don't recommend using your own panel states.  Use the default Long, Short or Cold and Dark panel states.

 

And never used saved panel states.  The default aircraft should always be the trike.

 

Saved panel states often causes complex 3rd party airplanes not to load properly.  Even PMDG recommends against them.

 

 

Cheers,

I think the issue with creating your own panel states is with the long, short, and cold and dark panel states some users (myself included) have reported fuel and anti-ice warnings when using anything other than the default panel state - it's a apparently a bug that's being looked at. The suggested short term work-around is using the default panel state and then creating your own long, short, and cold and dark panel states manually. I believe the issue may be that of the panel states that came with SP1D, only the default was created with the current service pack, while the others were older files. I'm not speaking for PMDG, but I believe that was the difference between the buggy and non-buggy panel states, therefore the suggestion of replicating long, short, and cold and dark manually from the non-bugged default state.

Saved panel states often causes complex 3rd party airplanes not to load properly. Even PMDG recommends against them.

I don't recommend using your own panel states. Use the default Long, Short or Cold and Dark panel states.

 

Seems  that pmdg have found a work around here  by  creating  your own panel  states as the link provided

 

http://forum.avsim.net/topic/463926-recall-error/