MSFS20 New objects not showing when selected .

[paul1964]

Hi. hopefully this will be a quick one. I have been creating an airport for some time, been adding my own custom objects etc.. with no real problem. The objects are created converted in model convertx , exported as a gltf into package sources etc.. I start msfs in dev mode , i Load my project, build package come to select the new object and all that is displayed is a white box no object. This has happened for the latest 3 objects I have created. All the previous objects are fine. So the question is there a limit to the amount of objects, or size of objects allowed for one source file ? Can i create a second source file for the same scenery?

Paul

 

[mamu]

Too complicated model, so it take a while load, or Most likely bad geometry

Advice to compile externally with fspackagetool, it will give you (hopefully)some insight about the errors preventing the model to show up

If you need some more help, please zip the whole model files with texture and someone could take a look at it

Inviato dal mio Mi 9 Lite utilizzando Tapatalk

 

[rhumbaflappy]

You can have several modelLibs in a package. I don't know if there is any advantage.

<?xml version="1.0" encoding="utf-8"?>
<AssetPackage Version="0.1.0">
    <ItemSettings>
        <ContentType>SCENERY</ContentType>
        <Title>41WI-Paddock</Title>
        <Manufacturer/>
        <Creator>rhumbaflappy</Creator>
    </ItemSettings>
    <Flags>
        <VisibleInStore>false</VisibleInStore>
        <CanBeReferenced>true</CanBeReferenced>
    </Flags>
    <Dependencies>
        <Dependency Version="0.1.18">
            <Name>rhumbaflappy-rhumbalib</Name>
        </Dependency>
    </Dependencies>
    <AssetGroups>
        <AssetGroup Name="ContentInfo">
            <Type>ContentInfo</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageDefinitions\rhumbaflappy-airport-41wi-elkhorn\ContentInfo\</AssetDir>
            <OutputDir>ContentInfo\rhumbaflappy-airport-41wi-elkhorn\</OutputDir>
        </AssetGroup>
        <AssetGroup Name="ModelLib">
            <Type>ModelLib</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageSources\ModelLib\</AssetDir>
            <OutputDir>Scenery\airport-41wi-elkhorn\scenery\</OutputDir>
        </AssetGroup>
        <AssetGroup Name="AnotherModelLib">
            <Type>ModelLib</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageSources\AnotherModelLib\</AssetDir>
            <OutputDir>Scenery\airport-41wi-elkhorn\scenery\</OutputDir>
        </AssetGroup>
        <AssetGroup Name="scenery">
            <Type>BGL</Type>
            <Flags>
                <FSXCompatibility>false</FSXCompatibility>
            </Flags>
            <AssetDir>PackageSources\Scenery\airport-41wi-elkhorn\scenery\</AssetDir>
            <OutputDir>Scenery\airport-41wi-elkhorn\scenery\</OutputDir>
        </AssetGroup>
    </AssetGroups>
</AssetPackage>

The output in the package:

 

[rhumbaflappy]

Here's an example of using 2 model libraries in one package. Each library has it's own texture, and it's own texture.cfg

 

[paul1964]

Thank you gents, your suggestions lead me to a successful conclusion. While setting up a second modelLib I noticed the output file was to scenery\global\scenery, so I changed that and that I had 2 versions of the same texture . So it now seems to be behaving.

Thanks
Paul