• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSX A feature request

lordofwings

lordofwings

Messages
639
Country
panama
When we create libraries we tell the library creator the MDL file we want to include. After compilation we place the library BGL file in the scenery folder but we must manually copy the textures.

As objects change over time the textures (or collection of textures) of a given object may vary.

My feature request would be that the library creator keep in a metafile the textures that an object included in the library requires. So it in addition to creating a GUID listing, it could also list the textures required by a given library object.

The feature is *not* for copying the textures to the texture folder, just to keep track of them so that the user is more aware of what he has to deploy when there are many objects in the library.

Anyway, just a suggestion. This tool has also been a life saver for me :)
 
Modelconverter X can provide an object report which includes the textures required.

Usually, I export the textures at the same time as testing in the sim, so the build is cumulative.

All you need then is to package up your Scenery / Texture folder pair.
 
I do the same but that works as long as you constantly do it. Leave it for a month or two and you no longer know much about the details, specially if working on multiple projects simultaneously.

I also try to use source/version control with my scenery since recent weeks to keep track of changes.
 
Hi,

This feature is already on the wishlist for LibraryCreator XML. Let's see if I can include it in the next update.
 
Hi Arno,

At one time you talked about integrating ModelConverterX and Library Creator XML. Is this still under consideration, or did you decide to permanently keep the two tools separate?
 
Hi Mike,

That is still in my mind :). Not sure how to do it, but in the ideal world I would also include an updated ObPlacer XML in the combined application.
 
You must log in or register to reply here.
Back
Top