Do you have any add-ons in your Community folder? If yes, please remove and retest before posting.
Done.
Are you using Developer Mode or made changes in it?
No.
Brief description of the issue:
See attached. Some mod airplanes have no livery. Does someone have the same problem? It never happened before to me. Probably it might have something to do with the Update. I never would suspect any MSFS 2020 update to cause any trouble…
Provide Screenshot(s)/video(s) of the issue encountered:
Detail steps to reproduce the issue encountered:
PC specs for those who want to assist (if not entered in your profile)
Did you submit this to Zendesk? If so, what is your ticket #?
Not yet.
Are you using megapack? My best guess would be there’s some mapping inconsistencies between different liveries. Some that were structured correctly is loaded. While others that are structured using an outdated format doesn’t.
I don’t have the issues myself because of all the liveries I downloaded, I completely reworked it with my own standardised structure, so it wasn’t affected by the latest update to the changes how the liveries are read.
I’m using megapacks, but never had this issue before.
Yeah, but there’s a new update from the Sim Update that I think changes the way the texture mapping behaves. If some liveries are already have these taken into account, they should be fine. But those liveries that are not compatible, then it might look like this.
What you say is out of question and I already had the same idea before asking. BUT: Originally MSFS2020 was designed especially for the use of mods and open source content. One would expect that the updates are compatible with the mods after following the instructions when installing the update.
Well yes, but actually no. One shouldn’t expect the updates are compatible with the mods. But one should expect that the mods are compatible with the updates.
How can this be possible? If you release a mod today according to the current standards, how will you be able to be up to date with an update to be released in 3 months which is incompatible with older mods?
However, I removed the community folder once more, started the sim, noted that the new liveries from the update which were NOT displayed in the beginning were there, put the content of the community folder back where it was, restarted and haven’t had this issue again.
There you go, you solved your issue. It’s usually a habit of mine already to clear everything from community folder before a major update. So that’s also probably why I never had any issues myself.
Then you keep updating your mod to make it compatible for the updates in 3 months time. That’s the risk we all take as modders and people who use mods. There’s something called support period, usually an active modder keeps supporting the mods through any updates that makes it incompatible. We keep updating to make it work. But there will come a time where it’s at the last life of the support period, where the modders are no longer supporting it, if there’s another updates that makes it incompatible and the modder no longer supports it, then it’s broken forever. That’s just how it is.
I made a lot of mods in my past, and while it was working at the time, sometimes the game updates up to a point that I can’t even keep up with it. Then I made a decision, I close the support, and I leave it to die. Who knows, perhaps someone else will take charge and make another mod based on my work. And that’s okay.
Nothing is everlasting. You can’t expect the same thing to always works forever, things change, they evolve. Either we keep up with it, or be left behind.
