PMDG 777 - Seated passengers breaking model

[RolandKov78]

You can correct it and use the seated pax... Go into the livery model folder and change the model.cfg file. Simpliest way to change the "exterior =PMDG773ER_EX.xml" entry to "exterior = ../../PMDG 777-300ER/Behaviors/PMDG773ER_EX.xml"



As I can see that the reference to the gltf files are incorrect (in the liveries model folder) , therefore you can reference the file in the aircraft original folder.

[Lonzo]

Changing the livery's model.cfg fixed it - thanks!

Which file in the aircraft original folder are you referring to, Roland?

I guess there will be an GSX Pro update so we don't have to change the model.cfg for every livery ourselves, right?

[lukehall]

You can correct it and use the seated pax... Go into the livery model folder and change the model.cfg file. Simpliest way to change the "exterior =PMDG773ER_EX.xml" entry to "exterior = ../../PMDG 777-300ER/Behaviors/PMDG773ER_EX.xml"



As I can see that the reference to the gltf files are incorrect (in the liveries model folder) , therefore you can reference the file in the aircraft original folder.

This is what my PMDG773ER_EX.xml in my liveries folders looks like...

I'm guessing that there are a few too many "behaviours" in those file paths!

[RolandKov78]

Yeah

Just change the link in the model.cfg file to the main aircraft one as per my first picture.
That will work.
The links in the individual liveries are incorrect. Same as for the Leonardo Maddog. Had to edit it myself that one too...

[RolandKov78]

Changing the livery's model.cfg fixed it - thanks!

Which file in the aircraft original folder are you referring to, Roland?

I guess there will be an GSX Pro update so we don't have to change the model.cfg for every livery ourselves, right?

There is a "PMDG773ER_EX.xml" in the main aircraft (777) Behaviors folder and also in the individual liveries ones too. The main aircraft folder has the correct reference to the gltf model files so that is the reason, why we have to do a manual correction.

In normal case a main GSX update not change these files, but if you take out the tick marks from the plane seated pax option, it will revert back to the incorrect one.

Again, I did it for the Maddog too as it has the same issue. Calling the model files in the wrong folder.

[SkyBoundSim]

Is there any update on the timescale for a fix for this?

Cheers!

[virtuali]

Again, I did it for the Maddog too as it has the same issue. Calling the model files in the wrong folder.

You are describing a behavior that happened only *before* the installer was fixed as I previously reported. The current version that is online since after I said it was fixed, correctly sets the exterior model for extra liveries as in the attached screenshot.

The GSX version number hasn't changed, because GSX itself hasn't changed either, it's just the installer that has bee fixed. Maddog works as well.

[RolandKov78]

Again, I did it for the Maddog too as it has the same issue. Calling the model files in the wrong folder.

You are describing a behavior that happened only *before* the installer was fixed as I previously reported. The current version that is online since after I said it was fixed, correctly sets the exterior model for extra liveries as in the attached screenshot.

The GSX version number hasn't changed, because GSX itself hasn't changed either, it's just the installer that has bee fixed. Maddog works as well.

Let me tell you why it isn't then... (Please note that I updated and "checked" all files in GSX and reenabled the Maddog liveries)

In the model.cfg you call the "MaddogX_exterior.xml" in the same folder.


Perfect
MaddogX_exterior.xml loads
Starting to look for the gltf file... FAIL. No GLTF in the referenced livery folder!


You doing it correctly for all the PMDG products where the GLTF is in the Aircraft main folder, but not in the Maddog...
The "..\..\" is missing and you are not going out of the original folder.



The correct reference should be like something: "..\..\MaddogX\model\MaddogX_exterior.gltf"   etc...

[virtuali]

The correct reference should be like something: "..\..\MaddogX\model\MaddogX_exterior.gltf"   etc...

That's what I have in fact, this is how an MD83 livery for AAL (with a new model folder created by GSX) looks like here. Are you referring to an 3rd party livery installed in a separate package maybe ? If yes, do you have a download link for it ?

[RolandKov78]

I checked the Emirates (default) livery again. For me it is still wrong as well.

There is no "model.300ER" directory in "Behaviors" folder, therefore it fail the exterior model to load in the sim!



When I correct it and step outside the "Behaviors" folder (or just simply delete the Behaviors) it will load as expected.



Please note that I only corrected the Emirates one, the KLM still fails

[virtuali]

There is no "model.300ER" directory in "Behaviors" folder, therefore it fail the exterior model to load in the sim!

As you can see from the screenshot I posted about the Emirates 777, the Behaviors folder is not used, and it points to the correct folder.

<LOD minSize="90" ModelFile="..\..\PMDG 777-300ER\model.300ER\PMDG773ER_LOD0.gltf">

I posted an image of my editor opened side by side with MSFS showing the livery working.

[RolandKov78]

Every livery is in a separate package because that's how the official livery manager loads them. Except the AAL which is in the aircraft folder.

[RolandKov78]

There is no "model.300ER" directory in "Behaviors" folder, therefore it fail the exterior model to load in the sim!

As you can see from the screenshot I posted about the Emirates 777, the Behaviors folder is not used, and it points to the correct folder.

<LOD minSize="90" ModelFile="..\..\PMDG 777-300ER\model.300ER\PMDG773ER_LOD0.gltf">

I posted an image of my editor opened side by side with MSFS showing the livery working.

What step I missing then, to get the latest correction as mine is still as per my previous screenshots... 

[virtuali]

Every livery is in a separate package because that's how the official livery manager loads them. Except the AAL which is in the aircraft folder.

Is the MD83 AAL livery working for you ? I'll surely check all the others now.

[virtuali]

What step I missing then, to get the latest correction as mine is still as per my previous screenshots...

You might suffer from network replication delays. Try updating again, or use the Offline installer (Sticky thread on this area).