• 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.

[Suggestion] Additional function regarding object textures

Messages
226
Country
germany
Clean and tidy scenery object libraries with their proper textures should be a goal for every designer. We have a problem with complex libraries here, though. While we can snoop out most errors like missing textures, it is next to impossible to weed out orphaned textures in a /texture/ directory with say 980 texture files. So the problem is not to find what we need, it's rather finding what we don't need.
Here's my proposal: would it be possible to assign an optional function in the "Save" dialog that copies the textures, which are assigned by the models in an archive to be created, from a user-defined source directory into a new user defined target directory? This also could report if there are any textures missing, and maybe even list attached FX file names that are needed for the objects to work (no copying needed for that).
I see that the library creator can write a "used texture list", so the basic function is there already.

Cheers,
Mark
 
Hi,

I guess something like that should be possible. I'll put it on the wish list.
 
Back
Top