[16FEB18] Update for Prepar3D v4.2 users via the Operations Center

[rsrandazzo]

Captains,

We have just issued an update for Prepar3D v4 users that will alleviate the onset of a ctd/hung screen/black screens problem in the PMDG 747-400 induced by a change Lockheed Martin made during the release phase of Prepar3D v4.2.

If you are a Prepar3D v4 user who has the 747-400 installed, you can obtain the update directly via the PMDG Operations Center.  A red notification bar will appear on the top right of the Operations Center when it is run, and you can probably follow the instructions from there. 

NOTE: This update does not apply to any aircraft other than the PMDG 747-400, and can be installed to any version of Prepar3D, but will only make a noticeable change in behavior for users of P3D v4.2 because it installs a small fix necessary to keep the 747-400 compatible with this new version of Prepar3D.  This "fix" is not necessary for any PMDG product OTHER than the 747-400.

A couple of notes on some items that will inevitably confuse a few people- so please help me un-confuse the confused:

1) This update makes changes to Prepar3D v4.2 in order to eliminate a CTD issue.  However, for our own sanity, we updated identical files on the Prepar3D v3 side in order to maintain product commonality because that will be important in a few <time descriptor deleted by moderator> when we release the PMDG 747-8.  Don't let this confuse you if you are a Prepar3D v3 user and you see an update flag.  You can install it... or not...  it is mostly just some file swaps to help us on our end and you aren't getting anything "new" per se.

2) If you are a heavy user of any product that needs to install or modify any panel entries into the panel.cfg file for the 747-400, we STRONGLY encourage you carefully consider whether you need this product installed or not.  If you DO decide to go ahead with the installation and you see problems, then you will need to uninstall it and return the 747-400 to it's original state to get back to normal operations- and in that case we recommend that you forgo whatever product is inducing the CTD (most likely FS2Crew ) when using Prepar3D v4 until further notice.  (Likely the release of Prepar3d V4.3 or possibly later if we cannot get Lockheed Martin's attention on the issue they created.)  Our apologies to anyone this impacts, but there isn't much to be done by us- as the problem is latent to the Prepar3D v4.2 update...

We will do our best to get LM's attention to the issue- but they have many many developers shouting at them all the time, and often quiet efforts to get their attention fail to get noticed...  We will do our best, however. 

 

[PinkPony]

Thank you Rob and PMDG team!

[Boomer]

Cheers.

[ahuimanu]

Hello, what is the expected version number?

[scandinavian13]

19 minutes ago, ahuimanu said:

Hello, what is the expected version number?

The one listed in the OC.

[kdfw__]

back in business!  thanks.

[Nicrative]

Who is this mysterious moderator editing the posts of mr. Randazzo. I want names 

anyways, thanks for this update!

[Scott434]

"NOTAM: This is a P3D v4.2 fix ONLY."

For those who remain at 4.1 and do not install this update, what does that mean for future updates and purchasing the -8?

 

 

 

[rsrandazzo]

Scott,

Nothing.  It means absolutely nothing.

Don't over-think it...  

 

[B777ER]

Thanks gentlemen. 

[Scott434]

3 minutes ago, rsrandazzo said:

Scott,

Nothing.  It means absolutely nothing.

Don't over-think it...  

 

Ok, thanks, toooo easy!

[Peter Webber]

Hi Robert, thanks for the update. I'm not a code expert by any means, but could you please give an idea, in laymans terms, what is/was the issue? Just to satisfy my OCD side! Thanks.

[Greggy_D]

So, what was the issue?  LM's code or PMDG's?

Greg Dee

[cgsmithmo]

Fixed! Thank you!

SO! We can expect the 747-8 in a few...hours? Cool!!!   :P

[Wise87]

It was mention programs that modify the panel.cfg should be avoided. Does ChasePlane or Ezdok fall under the this category?