FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: Sparky233 on March 28, 2025, 10:58:47 pm
-
Hello,
I have had issues with the Leonardo Maddog in FS2024 in reference to GSX. The aircraft exterior model worked fine before adding seated passengers to the aircraft via the FSDT Installer with no bugs or issues. After adding the seated passengers via the FSDT Installer, the aircraft has had extensive exterior model issues with the MD-88 and MD-83 models. This includes there being no exterior skin, as well as the exterior model being frozen in the state pictured below. I have looked for all remedies to this however, none work. Here is also the livery used in this particular case, but as noted, it happens with all models and textures, even the base ones for the MD-88 and MD-83.
https://flightsim.to/file/32223/delta-air-lines-n917dl-2020-md-88-8k is the livery
https://i.gyazo.com/221238c37ea37e2eb5b4be6712b2736f.png (https://i.gyazo.com/221238c37ea37e2eb5b4be6712b2736f.png)
https://i.gyazo.com/8ef4b304f186066d6069a498f22551e7.png (https://i.gyazo.com/8ef4b304f186066d6069a498f22551e7.png)
https://i.gyazo.com/57882b20705d4d47a97139753d41ebd3.png (https://i.gyazo.com/57882b20705d4d47a97139753d41ebd3.png)
-
I will say I believe this problem stems from somewhere within the model file that the FSDT Installer places into the aircraft folder when adding seated passengers
-
Hello, I know there is a backlog right now but I wanted to see if this was seen at all yet?
-
This has been an issue with Seated Passengers and the Maddog almost for a year and Umberto refuses to acknowledge it. "Doesn't happen here" as he always.
https://www.fsdreamteam.com/forum/index.php/topic,31967.0.html
Better to just not use Seated Passengers for the Maddog.
-
This has been an issue with Seated Passengers and the Maddog almost for a year and Umberto refuses to acknowledge it. "Doesn't happen here" as he always.
I don't JUST say "he doesn't happen here", I asked specific question to understand why it might happen to some users, you said it happens with "the MD80" and all liveries, that is assuming with "MD80" you mant all 3 variants (MD82-83-88), which clearly can't be, otherwise I should be able to replicate it easily.
So, again, please provide precise reproduction steps, clearly specifying which variant you tested, and exactly which livery. Do not reply "all of them", that's not what I'm asking, I'm asking for just a simple example I can reproduce.
-
In that case try my livery I have made:
https://flightsim.to/file/31823/md-82-qantaslink-vh-yqy
Install into the MD-88. Turn on GSX, load the simulator and the external model is missing.
Works without enabling Seated Passengers, as soon as you enable it, it breaks the aircraft. As soon as you disable it, it is fixed. Correlation = causation?
-
In that case try my livery I have made:
Does this mean:
- It's just an example of something that doesn't work, but it doesn't work on default liveries as well
OR
- It happens only with that livery, but not with official ones or not with all of them, or you haven't tried ?
Of course I'll try your livery. And please clarify which simulator you are using it, if you use both 2024 and 2020, clarify if the problem happens in one of them (which one) or both.
-
It happens with all liveries I have come across. I have given you the steps to replicate as requested, now replicate and find out what you are doing to break the aircraft.
-
Works without enabling Seated Passengers, as soon as you enable it, it breaks the aircraft. As soon as you disable it, it is fixed. Correlation = causation?
Nice livery you made. Now, I think SOMETHING strange is happening because:
- When I first loaded the airplane directly to the airport, the cabin didn't appeared.
- When I went to the Hangar screen and selected the Livery, it worked and from then on, it started working in the sim as well.
I looked at the changes made by GSX, and the all looks correct to me, except for a very minor thing, which shouldn't be an issue on Windows, and it's the upper/lower case, here's how the model.cfg for the MD-88 looks like:
[models]
exterior=..\..\MaddogX\Model\MaddogX_exterior.xml
interior=..\..\MaddogX\Model\MaddogX_interior.xml
However, the airplane model is installed into "model" folder all lower case, it shouldn't make any difference on a case-insensitive filesystem like Windows but maybe this is causing it: maybe some parts in the sim do case-sensitive comparisons during the initial loading, but the Hangar doesn't so, as long you enter the hangar, the full airplane loads.
-
Thank you for the compliment.
That isn't what I get, the plane doesn't load in the hangar view nor does it load when spawning in. Are you configuring the livery to the MD-88 and not using the base MD-82?
-
the plane doesn't load in the hangar view
Have you tried to click on the bottom images that scroll between various liveries, and maybe load the base one before ?
Are you configuring the livery to the MD-88 and not using the base MD-82?
I'm not configuring anything, I just copied the package in the Community, selected an MD-88 and found your livery in addition to the stock ones.
-
I’ll try this next time, but in all the previous attempts selecting liveries and see which ones work and which ones don’t is that they are all broken including the base one (in 2020).
Have spent very little time in 2024 trying to figure it out because 10 months ago couldn’t get it to work at all in 2020.
-
Have spent very little time in 2024 trying to figure it out because 10 months ago couldn’t get it to work at all in 2020.
I tried only MSFS 2020.
-
As I said in the other post and responding to the users questions in here who is referencing 2024 and along with the instructions and screenshot taken from 2024, I’ve only ever been talking about 2024. I haven’t opened 2020 for 3 months.
-
As I said in the other post and responding to the users questions in here who is referencing 2024 and along with the instructions and screenshot taken from 2024, I’ve only ever been talking about 2024. I haven’t opened 2020 for 3 months.
For real ? I tried it 2020 precisely because what you just wrote!
in all the previous attempts selecting liveries and see which ones work and which ones don’t is that they are all broken including the base one (in 2020). Have spent very little time in 2024 trying to figure it out because 10 months ago couldn’t get it to work at all in 2020.
That's why I tried 2020, because you said it never worked there. You said it has been more than a year and I "refuse to acknowledge it", that could only have been 2020, since a year ago 2024 wasn't even out!
-
Don't lie now, I didn't mention 2020 at all until after you tested it... This post is about 2024 and since when does 2020 look like this?
-
Don't lie now, I didn't mention 2020 at all until after you tested it... This post is about 2024 and since when does 2020 look like this?
How you dare to call me liar! You don't even understand your own logic? You said it NEVER worked for you in 2020, what this has anything to do you also posted it about it in 2024 ? That's why I tried it in 2020, because you you said it never worked and it has been broken there for over a year, and I "refused to acknowledge it" so, I first start there, to check that. We'll get to 2024.
-
You quoted statements about me mentioning 2020 after you already had tested it so unless you can time travel, those statements could not have influenced your past assumption. I said at the beginning responding to this thread that it has been an issue with GSX for almost a year which I left a link to that thread which in that thread says the problem is also in 2024.
Can you please now test in 2024.
-
You quoted statements about me mentioning 2020 after you already had tested it so unless you can time travel, those statements could not have influenced your past assumption
What the past has anything to do with it ? You said it never worked, and I was never able to replicate it back then, You said NOW "it never worked" in 2020, so I tested AGAIN!
Can you please now test in 2024.
Sure I will, but that doesn't change the fact you were wrong saying I "refused to acknowledge it", because I obviously wasn't then and I'm not now. There's something weird happening, for sure, but the livery works.
-
You said NOW "it never worked" in 2020, so I tested AGAIN!
I never said that until after you tested it again just now... So that couldn't have been the reason why you tried it in 2020 rather than realising this entire thread is about 2024.
With the thread 10 months ago, you kept saying that you don't experience the issue and never tested with any other liveries and just did the default and that thread was never resolved so I just never turned it back on. I then decided to do my first flight tonight in 2024 in the MD80 and surprise, the GSX problem that existed in 2020, exists in 2024.
-
I never said that until after you tested it again just now... So that couldn't have been the reason why you tried it in 2020 rather than realising this entire thread is about 2024.
Why this even matters ? You said it never worked in 2020, you said I "refused" to acknowledge", both of which were not true back then and are even more untrue now that I repeated the test exactly with the livery you suggested to test.
-
Why does it matter? Because you lied and I called you out on it. You justified testing on 2020 quoting me as the reason even though those quotes were said after you tested it.
-
Why does it matter? Because you lied and I called you out on it. You justified testing on 2020 quoting me as the reason even though that quotes were said after you tested it.
Your "called me out" ? You called my liar because you hate being proven wrong, back then and even now, when I repeated the test again, because you said "it never worked in 2020" and when you tried to imply I refused to acknowledge it.
Here's your livery happily working in MSFS 2024 SU3 current Beta (no, I'm not switching out of it just to try it in SU2). I'm NOT calling you a liar for having said it doesn't work, I'm sure there must be something that is escaping us but, at least, use the same benefit of the doubt towards me, when I spend my time TRYING to replicate your issue.
In 2024 it was even easier: I didn't had to play with the livery switching like I had to do in 2020, I clicked the livery, and it worked at the first try.
-
I called you a liar because you lied, it's that simple. Anyone can look at the order of the posts and see that I mentioned 2020 after you tested it yet you said that was the reason why you tested 2020.
A > B > C is reality, you claim it happened B > A > C.
Well I'm using SU2 so that must be the problem. You'll need to go back to SU2 to figure out the error. And as shown in the previous thread and this, I'm not the only one with the issue. Maybe you could send the livery to me and I could try on my system without changing any files and see if those exact files work in SU2.
-
I called you a liar because you lied, it's that simple.
But it's wrong, and repeating it doesn't make it anymore trye.
Anyone can look at the order of the posts and see that I mentioned 2020 after you tested it yet you said that was the reason why you tested 2020.
The issue is, it doesn't matter,
Well I'm using SU2 so that must be the problem. You'll need to go back to SU2 to figure out the error.
No, I don't.
Because if THIS is really the case, your entire argument of "GSX corrupting the livery" falls down entirely, if it's something that might been improved thanks to SU3.
Assuming it WAS the upper/lower case issue I suspect it might be in 2020, MAYBE somebody at Asobo realized that, on a case-insensitive filesystem like Windows, is not really needed to process config that will end up in loading stuff from disk in a case-sensitive way, maybe because it might have happened on other airplanes too, unrelated to GSX ?
-
But it's wrong, and repeating it doesn't make it anymore trye.
Yes, it is wrong to lie. It's perfectly ok to say "Sorry I presumed you were talking about 2020, so I tested 2020" compared to "For real ? I tried it 2020 precisely because what you just wrote!" and quoted me saying "Have spent very little time in 2024 trying to figure it out because 10 months ago couldn’t get it to work at all in 2020." as the reason why you tested 2020 which was after you tested it, not before. Have a re-read, its very black and white and see there was no mention of 2020 in that thread before you tested it.
I haven't opened 2020 for 3 months, and haven't used Seated Passengers in 2020 on the MD80 for 10 months. I'm not sure if it works now or not, but I'm now using 2024 and it currently has the same issue I experience in 2024 and the user who created this thread has exactly the same problem. So it must be either SU2 and SU3 or I suspect a referencing issue. I will package up my livery after enabling seated passengers in 2024 and send it to you for diagnosis to see if GSX making the changes correctly. I'm on Windows 11 and use the Xbox app version of the game, not Steam.
-
Yes, it is wrong to lie.
It's even more wrong to tell somebody is lying, when it's not the case. We might disagree on this, but NOT on inappropriate usage of the term. I never called YOU "a liar", even if I'm fully convinced (just like you are), you are wrong in almost everything you say. Saying somebody is wrong is not offensive, calling somebody a liar is, because saying somebody is wrong means accepting HE is honestly convinced to be in the right, I'm sure you are and I accept it, even if I disagree. Calling somebody a liar is offensive, because it implies malice and willingness to deceive, and that is NOT acceptable.
I haven't opened 2020 for 3 months, and haven't used Seated Passengers in 2020 on the MD80 for 10 months
Again, completely irrelevant. You wrongly accusing me of not taking this seriously back then, and while you might had had some kind of point, because then I said I only tested with default liveries, but your wrong accusation sounds even more wrong today, when I tested:
- the livery you said it "never worked" in 2020
- the livery you said it doesn't work now, in 2024.
In any case, I made ANOTHER test and guess what, it was as I suspected: it's the casing issue. I manually changed all involved files to match precisely the actual file/folders in disk, and by doing that, MSFS 2020 opens the airplane directly at the first try, without even having to enter the Hangar before. 2024 worked straight away, so maybe this is exactly something they might have fixed, because I can imagine something must have happened in other cases: it's very easy for any developer to miss a small detail like that, on Windows, shouldn't even matter, so perhaps there might have been some obscure bug report airplanes or liveries not loading, so they made the loading process more robust in 2024 SU3. We can only rejoice about that.
I'll try to investigate further to understand what is exactly the part that is case-sensitive: it might be the model.cfg or the exterior.xml, or both, and it might be just the path portion, or just the filename, or both and if it's found, we might come up with a fix.
-
Calling somebody a liar is offensive, because it implies malice and willingness to deceive, and that is NOT acceptable.
Except you did imply malice and willingness to deceive by lying by quoting something as the reason you did it even though that quote was after those events rather than simply admitting that you made a mistake by assuming I was talking about 2020 when the entire thread was only ever about 2024.
-
Except you did imply malice and willingness to deceive by lying
Except this isn't what really happened and repeating it won't make it true. I'm closing this thread now, will be reopened only if there are news to communicate.