This only applies to sceneries that use models.
Go into the scenery package. go into the “scenery” directory in there. The path you’ll need to follow after that will be different depending on how the developer created the package. Sometimes you’ll go into scenery\global and in there you might find a modellib.bgl.
sometimes it will be in “mycompany” or something stupid like that because for some reason developers don’t have a clue about marketing or haven’t paid attention to all the people screaming “STOP NAMING YOUR FILE MODELLIB.BGL! IT CAUSES CTD’s when you don’t name your package uniquely!!!” You can insert whatever words you want between the words there that for some reason people think we’re all to young to see. Anyway…
The actual fact is, the name of the model bgl supposedly doesn’t actually matter, what super matters is that the path inside the package to that file be unique. Unfortunately, “Billions” of people just use the default names because they have no imagination, and it ends up being scenery\mycompany\global\modellib.bgl, and everyone who uses their package gets a CTD when they have two packages with the same path inside of the scenery directory to their model library file. If you change mycompany to something unique, that should be enough. But, personally, I make the whole package unique. Because, who knows how careful Asobo is in their coding, and I’d rather not allow any way for MSFS to get confused as to what’s what.
After you’ve gone through all of that, you’ll need to update the layout.json to reflect the new file and directory names.
Given I’m ■■■■■■ that nearly a year into it and “professional” development companies are still making the same mistakes (not only that, they leave the image that is supposed to be their business card, they leave it as the “PLACEHOLDER” image… smh), I probably just confused you more with all my blabbing… so it might be easier for you to tell me what’s in the scenery directory of said package…
