Custom materials not showing after compile

[BrBlazer]

Hi all,

Has anybody had custom materials not showing when placed using aprons? During the edit in the dev mode they show fine, however after compiling they are missing. I've done this before and they showed up normally, there's nothing different from the previous times i've done this other than FS's being updated with the hotfix last week.

I'm doing exactly what's being done here:

Kind Regards,

Blazer

 

[superspud]

Yes. All the time.

If I enter development mode and then exit they show up fine. And sometimes they show up for the first time without doing that.

I've seen screen shots where it clearly has shown up for other people so they are in there but I don't really get why it happens.

 

[BrBlazer]

I'm begining to think it's something about the PNG format.

I replaced the material with another material from another airport I edited previously and that one showed up fine whislt the new ones did not. Same apron, just dragged and dropped the different material (red ground runway ID, so I used a 13-31 from another airport to replace the 11-29 from the current for test only)

 

[BrBlazer]

FIXED

Nothing to do with PNG format, but this:

Scenery creators: please move or rename your modelLib.BGL

I was trying to troubleshoot some scenery conflicts that were causing CTDs yesterday when I noticed something concerning. It seems that a lot of scenery creators are not changing the location of the modelLib.BGL that is output by default for an ArtProj. I wrote a quick python script to scan...

forums.flightsimulator.com

Specifically this part:

Replaced mymaterials on both the "Name" and the "OutputDir" using that same format suggested above using the icao of the airport to identify.

 

[rhumbaflappy]

I use this:

        <AssetGroup Name="mymodellib">
            <Type>ArtProj</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageSources\rhumbaflappy-c59-modelLib\</AssetDir>
            <OutputDir>scenery\rhumbaflappy\LakeLawn\</OutputDir>
        </AssetGroup>

scenery\<your name>\<project name>\... and you could use ICAO instead of project name, or even add it to the end scenery\<your name>\<project name>\<icao>\
In the above example, the modelLib is actually named "rhumbaflappy-c59-modelLib.bg" in the package, in the 'rhumbaflappy-airport-c59-lakelawn\scenery\rhumbaflappy\LakeLawn' folder.

Microsoft uses this format:
\scenery\microsoft\Lands-End-Airport

Which is great, but they still use
<AssetDir>PackageSources\modelLib\</AssetDir>

which yields "modelLib" as the package BGL name ( not a good idea). This confuses everybody (including the sim apparently) as there will be dozens of 'scenery\modelLib' folders.