PMDG 777 - Seated passengers breaking model

[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.

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

Yes. That is the only one which working if I not changing the route manually for all others

[RolandKov78]

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).

Thanks Umberto, I confirm that with the offline installer the Behavior entry is gone, so the 777 liveries are all fine.

[virtuali]

Thanks Umberto, I confirm that with the offline installer the Behavior entry is gone, so the 777 liveries are all fine.

Have you tested the Maddog too ? I installed some liveries that stayed in their separate package, and all of them seems to be fine, the ModelFile attribute is correct:

<LOD minSize="5" ModelFile="..\..\MaddogX\model\MaddogX_exterior.gltf">

[moxiejeff]

Glad I ran into this thread; all of my iFly liveries are broken -- no fuselage showing since I updated GSX Pro.

[virtuali]

Glad I ran into this thread; all of my iFly liveries are broken -- no fuselage showing since I updated GSX Pro

This thread doesn't have anything to do with the iFly, it's related to the PMDG 777, which is confirmed to be fixed in the latest update, with some mentions of the Maddog X, which is also fixed.

[moxiejeff]

So why are all my iFly liveries showing the same as the PMDG ones from other users in this thread? I haven't touched any of my iFly liveries in a week or two; the only thing I've updated is GSX Pro.

[RolandKov78]

Thanks Umberto, I confirm that with the offline installer the Behavior entry is gone, so the 777 liveries are all fine.

Have you tested the Maddog too ? I installed some liveries that stayed in their separate package, and all of them seems to be fine, the ModelFile attribute is correct:

<LOD minSize="5" ModelFile="..\..\MaddogX\model\MaddogX_exterior.gltf">

Hello Umberto, yes I tested it and I think found out what is caused the issue.

After running the offline updater the 777 was fixed with a simple tick on / off in the config section.
The Maddog still had the <LOD minSize="5" ModelFile="MaddogX_exterior.gltf"> entry, so I opened up notepad++ and started to check what is happening when I remove and add the checkmark in GSX.

If I understand correctly how your script is working, then it is the following:
1, it takes the original exterior xml file and add the necessary model merge entries for GSX in the original aircraft folder.
2, copies this updated file into all the 3rd party livery folders and update the model.cfg to the new external xml
3, when I take out the checkmark it should do it in reverse and restore the original file state without the GSX seated pax model merge entries.

Here where I found the root cause. Now, I'm not sure it is only for me (as other people sees the issue too), but the "restored" MaddogX_exterior.xml file looks like this!


I have no idea how the original file from Leonardo have the reference or just my installation is corrupted, but this is without GSX entries.
It will work in normal case, but as soon as the GSX script copies this file, the address will make the external model xml corrupt.

As I had no intention to delete all my logged flight hours and state saves, I did not deleted and did a clean install of the latest Leonardo version, therefore I cannot say what the original file contains, but this is how it is in my case.

After that, based on your screenshot, I manually updated the file to ..\..\MaddogX\model\MaddogX_exterior.gltf and put the checkmark back in GSX.
Voila, all livery worked because now it copies the files with the good address.

Maybe someone from the community can confirm what the original file contains.
Your script does what it supposed to do, but the outcome is wrong if the input is incorrect.

Thanks

Roland

[D.Fidalgo]

Please any help or guide to fix this problem in fenix A320 liveries?what should be changed and where? thank you very much

[D.Fidalgo]

this way its correct?

[model.options]
; if true, when showing the exterior, also show the interior model (default false)
withExterior_showInterior=true
; if true, when showing the interior with the exterior, exclude interior.lod.0 (default false); only has an effect when withExterior_showInterior is true
withExterior_showInterior_hideFirstLod=true
; when showing the interior, force showing lod0 (default true)
withInterior_forceFirstLod=true
; when showing the interior, also show the exterior model (default false)
withInterior_showExterior=true

[models]
exterior=FNX320_Exterior_CFM.xml
interior=FNX320_Interior_CFM.xml

[virtuali]

There's no need to post such complex instructions. If you are using the latest 3.2.6 installer, everything should work. If you still find a livery that doesn't, please post a download link to it, and we'll check it.

[virtuali]

if you explain in detail what I should do and where I should do it I can do it in each of the liveries

I already explained in detail the only thing you should do:

If you still find a livery that doesn't, please post a download link to it, and we'll check it.

This way, I can DOWNLOAD the livery, and verify if and why it doesn't work.