FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: lukehall on October 28, 2024, 12:25:48 am
-
Hi,
I have just updated GSX Pro to 3.2.3 And ticking the Seated Passengers box in the FSDT Installer now breaks liveries.
If I install a livery via the PMDG OC, then go to the FSDT installer and un-check, then re-check the Seated passengers box, the aircraft doesn't load properly (has the external model missing and the cockpit not loading properly). The house livery appears to be unaffected.
If I then exit MSFS, remove the liveries and re-install them, then enter the sim without re-checking the seated passengers option, they work fine, but with passenger textures missing.
It is completely repeatable. It has only started happening with the 3.2.3 update.
Thanks!
Luke
-
I have same issue with the 737. Unchecking the seated passenger option and it loads fine
-
I cannot reproduce it, but I only tested a couple of liveries (all official, of course). As usual, when reporting a problem, try to be as precise as possible, clearly indicating the precise, exact, livery used.
-
I cannot reproduce it, but I only tested a couple of liveries (all official, of course). As usual, when reporting a problem, try to be as precise as possible, clearly indicating the precise, exact, livery used.
PMDG official United Airlines, American Airlines, British Airways, Air France.
In addition, I have also tried completely uninstalling and reinstalling PMDG. Same problem.
-
It's the same for me. House liveries are not affected. If you don't update GSX, it doesn't happen, but you lose the textures and go pink. The aircraft is completely broken; the seating rolls out onto the threshold alone, and the rest of the plane doesn't exist. Would any screenshots help Umberto?
-
Livery-wise, All of mine were affected. Here are just some of them:
https://flightsim.to/file/76740/emirates-main-pack-w-cabin-pmdg-b777-300er
https://flightsim.to/file/57065/ryanair-package-w-cabin-pmdg-b737-800
https://flightsim.to/file/76795/official-air-canada-c-fitw-go-canada-go-olympic-livery-8k-pmdg-777-300er
I also had the same problem on PMDG 777 Qatar and then gave up and flew the iFly :)
-
Found the problem, just run the FSDT Installer again, you should get an updated version that will fix the it.
-
Awesome. Thank you.
-
Found the problem, just run the FSDT Installer again, you should get an updated version that will fix the it.
Thank you Umberto. I'll try this evening :-)
-
Not fixed for me. Hasn't worked and was updated prior to loading the sim. House livery Qatar 777. Same for the 737 house Jet2.
-
Not fixed for me. Hasn't worked and was updated prior to loading the sim. House livery Qatar 777. Same for the 737 house Jet2.
Installer says latest version 3.2.3 FYI
-
I'm sorry to report that it's not fixed for me either.
I ran a "check" first in the FSDT installer - Reporting same version 3.2.3
Removed then reinstalled liveries via the PMDG OC
Rechecked "seated passengers" in the FSDT installer.
House livery aircraft loads correctly and passengers board but disappear when seated.
Other liveries - aircraft doesn't load correctly.
-
I'm sorry to report that it's not fixed for me either.
I ran a "check" first in the FSDT installer - Reporting same version 3.2.3
Removed then reinstalled liveries via the PMDG OC
Rechecked "seated passengers" in the FSDT installer.
House livery aircraft loads correctly and passengers board but disappear when seated.
Other liveries - aircraft doesn't load correctly.
Same for me for 737. House livery worked but the ones I use from .to do not
-
I think even if you have seated passengers from house or dot to liveries, the textures will go pink (if GSX is not updated first). If you turn off seated the liveries will possibly be fine.
-
Same problem here!
All my PMDG aircraft (737-700, 737-900, 777) appear in MSFS as a flying cabin/cockpit. No fuselage, no wings, nothing, just the cabin and cockpit (777) or even just a cockpit (737-700 & 900). All models are completely broken.
The steps I took (unsuccessfully):
- made sure GSX Pro is up-to-date V (3.2.3), performed the CHECK in the FSDT Universal installer
- un-ticked Seated Passengers for all aircraft under CONFIG. Started the sim- all aircraft/liveries appear correctly.
- closed the sim, ran the FSDT Universal installer and CONFIG again and ticked Seated Passengers. Started the sim - nothing but flying cockpits/cabins again. All models/liveries broken. Closed the sim.
- ran the FSDT Universal installer and CONFIG again, un-ticket Seated Passenger. Started the sim - all aircraft/liveries appear correctly. Closed the sim.
- removed all my PMDG liveries (using the PMDG Operations Center 2.0)
- ran FSDT Universal Installer again. Under config, I ticked & un-ticked Seated Passengers
- re-installed a couple of liveries per aircraft (using the PMDG Operations Center 2.0)
- re-ran the FSDT Universal installer and CONFIG again and ticked Seated Passengers. But again, after starting the sim, I had nothing but flying cockpits/cabins. Frustrating, to say the least.
Nothing seems to fix the GSX/PMDG issue. Everything worked fine until installing GSX Pro 3.2.3.
Now, I can't fly any PMDG airliners using GSX w. pax anymore which is sad because it's what i normally do in the sim. Please help!
Liveries used (all stock PMDG):
737-700 Virgin Australia VH-NJV, Spirit N779NK, Ryanair EI-SEV, Delta N308DE
737-900 Alaska N306AS
737-900ER Alaska N280AK, Delta N870DN, Lufthansa D-ACMD
777-300ER American N717AN, British G-STBC, Cathay Pacific B-KQU, Emirates A6-ENE, Etihad A6-ETG
-
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"
(https://i.postimg.cc/rFrnmDLy/image.png)
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.
(https://i.postimg.cc/9Qcdh0mn/image.png)
-
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?
-
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"
(https://i.postimg.cc/rFrnmDLy/image.png)
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.
(https://i.postimg.cc/9Qcdh0mn/image.png)
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!
-
Yeah :D
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...
-
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.
-
Is there any update on the timescale for a fix for this?
Cheers!
-
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.
-
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.
(https://i.postimg.cc/k4qD7dVC/image.png)
Perfect
MaddogX_exterior.xml loads
Starting to look for the gltf file... FAIL. No GLTF in the referenced livery folder!
(https://i.postimg.cc/rmwchy0D/image.png)
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.
(https://i.postimg.cc/hPSwTZmG/image.png)
The correct reference should be like something: "..\..\MaddogX\model\MaddogX_exterior.gltf" etc...
-
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 ?
-
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!
(https://i.postimg.cc/t4kfCK4b/image.png)
When I correct it and step outside the "Behaviors" folder (or just simply delete the Behaviors) it will load as expected.
(https://i.postimg.cc/bY2V7DX1/image.png)
Please note that I only corrected the Emirates one, the KLM still fails
(https://i.postimg.cc/s2qqWpdD/image.png)
(https://i.postimg.cc/hGdMH66c/image.png)
-
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.
-
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.
-
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... :o
-
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.
-
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).
-
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
-
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.
-
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">
-
Glad I ran into this thread; all of my iFly liveries are broken -- no fuselage showing since I updated GSX Pro.
-
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.
-
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.
-
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!
(https://i.postimg.cc/pTRWWqhF/image.png)
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
-
Please any help or guide to fix this problem in fenix A320 liveries?what should be changed and where? thank you very much
-
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
-
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.
-
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.
-
The issue is still there. Wrong paths in all files.
-
The issue is still there. Wrong paths in all files.
The issue has been fixed long ago, the lines are added correctly. If you have an example of a specific livery that doesn't work, post a link to it (if it's a 3rd party), or clearly identify it if it's an official one, so we can check it.
-
I'm sorry to say that it's not solved on my side.
GSX version is 3.3.0. It is working fine with default PMDG livery, but not with AIR FRANCE and AMERICAN AIRLINES liveries from PMDG.
I've checked the model folder for the link and that's why I have (I tried several time to link/unlink GSX with the 777 in GSX settings) :
exterior = PMDG773ER_EX.xml
interior = ../../pmdg 777-300er/behaviors/pmdg773er_vc.xml
So, I had to modify manually the culprit...
-
exterior = PMDG773ER_EX.xml
interior = ../../pmdg 777-300er/behaviors/pmdg773er_vc.xml
So, I had to modify manually the culprit...
Those lines ARE correct.
The issue is, the installer should have copied the PMDG773ER_EX.xml in that livery folder so it could be modified, so maybe the problem is that something external ( antivirus, add-on linker ) is maybe preventing it from doing that.
-
Well, a bit strange then, because when I change the lines to :
exterior = ../../pmdg 777-300ER/Behaviors/PMDG773ER_EX.xml
interior = ../../pmdg 777-300er/behaviors/pmdg773er_vc.xml
then everything is working fine.
Basically I'm just changing the first line from "exterior = PMDG773ER_EX.xml" to "exterior = ../../pmdg 777-300ER/Behaviors/PMDG773ER_EX.xml" then it's working. Do you think it's my firewall/antivirus that prevent the first line to be modified by GSX ?
-
then everything is working fine.
Of course it works, but that doesn't mean the modification made by the installer is "wrong" because, as I've said already, IT IS correct.
The problem is NOT the modification ( which is correct ), the problem is you should have a copy of PMDG773ER_EX.XML file there in that folder, which is made by the installer, and it normally does it, so the issue is why it doesn't on your system.
-
I have a copy of this file in the texture folder, it's just the line I mentioned that is not updating.
-
then everything is working fine.
Of course it works, but that doesn't mean the modification made by the installer is "wrong" because, as I've said already, IT IS correct.
The problem is NOT the modification ( which is correct ), the problem is you should have a copy of PMDG773ER_EX.XML file there in that folder, which is made by the installer, and it normally does it, so the issue is why it doesn't on your system.
I tried GSX passengers for the first time today, ALL of my PMDG 737-800s and All of my Ifly 737 Maxs are now broken. I'm running the latest GSX, I have run the checks and I've tried checking and unchecking the pax box to fix and tried just unchecking it all together. Still broken. I am not willing to modify files as I should not have to, the program should work correctly.
What I would like to know is how to fix my airplanes and use them without the pax feature enabled.
Side note: I've been working 20 days straight and have only today for simming and I'm spending it fixing this instead of flying my cartoon airplane. I hope you can understand the frustration this causes.
Another side note, next day: Now my Coualti doesn't even start so ....more wasted time.
-
Yes I have this issue also with my pmdg 777 and737 aircraft and some of the maddog x planes. Not sure just came out of nowhere and all I can do is disable the seated passengers to fix it. I'm hoping someone comes up with a fix for this. I'm not that good at going in and changing config files around.
Thank you
-
Yes I have this issue also with my pmdg 777 and737 aircraft and some of the maddog x planes. Not sure just came out of nowhere and all I can do is disable the seated passengers to fix it. I'm hoping someone comes up with a fix for this. I'm not that good at going in and changing config files around.
Thank you
I also disabled passengers put it didn't fix mine. I spent a few hours uninstalling and reinstalling aircraft and liveries and rebinding Ifly controls. Whole day wasted, squeezed in one short flight last night now I'm back to working the next couple weeks before I can sim again. I'm not super heartbroken that I can't use the passengers, but I am a little irate that checking a box ended up wasting so much of my time AND would like to know exactly why it occurred.
-
As I confirmed multiple times, there are no issues whatsoever with any PMDG airplane, they are all correctly patched and they are all working.
That is, of course, assuming you are using the current version of the installer. Fact somebody said "Couatl doesn't start", suggests a possible same root cause: not getting the latest version of the installer AND Couatl not starting, possibly because the antivirus blocking both so, configure the antivirus to exclude the whole Addon Manager folder and try again.
Also, if you had issues with PMDG caused by an OLD version of the FSDT Installer, just updating the installer won't fix this, you need to uninstall/reinstall the airplane.
-
I fixed my pmdg aircraft problem, I totally removed both 777 and 737 and all liveries. Did a reinstall now GSX works perfect. thanks for the help
-
As I confirmed multiple times, there are no issues whatsoever with any PMDG airplane, they are all correctly patched and they are all working.
That is, of course, assuming you are using the current version of the installer. Fact somebody said "Couatl doesn't start", suggests a possible same root cause: not getting the latest version of the installer AND Couatl not starting, possibly because the antivirus blocking both so, configure the antivirus to exclude the whole Addon Manager folder and try again.
Also, if you had issues with PMDG caused by an OLD version of the FSDT Installer, just updating the installer won't fix this, you need to uninstall/reinstall the airplane.
All requirements met, new installer, GSX 3.3.2, antivirus exception and passengers broke the Ifly 737. Let's assume the mistake is on my end; what exactly is GSX, assuming I have something wrong, doing to my Ifly installation to cause this issue that would not occur if I had everything on my end correct?
-
passengers broke the Ifly 737.
Impossible to say more without precise reproduction steps as in, which models were affected, which liveries, etc.