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

MSFS Re-using MSFS Textures

rhumbaflappy

rhumbaflappy

Administrator
Staff member
Resource contributor
Messages
5,779
Country
us-wisconsin
MSFS has a lot of nice textures used in their models. We can re-use these textures in our own models via Blender. But one of the advantages of re-using textures is that we can reference these textures without including them in our packages, saving potential gigabytes of project size. The key is the use of texture.cfg
XML: 
[fltsim]
fallback.1=scenery\outskerries\TEXTURE
Here, I decided to use textures from the Asobo outskerries package. Knowing which textures I want, I copied them to a SourceTextures folder, where I convert them from DDS to PNG, for use in Blender. I use Paint.net for this, as it easily converts the DDS to 32-bit PNG.

sourcetextures.png


Now I just use these PNG textures in Blender. When I export my object, I don't need to save these textures to my project, as my texture.cfg handles them.

blender.png


You can load the project into the DevMode, and MSFS will display the objects properly, even though you include no textures in the project. Here is an example: ReferencingTextures.zip
 
rhumbaflappy

rhumbaflappy

Administrator
Staff member
Resource contributor
Messages
5,779
Country
us-wisconsin
Arno has made a change in the way textures are initially loaded into MCX, and now it is trivial to load a model from a library, convert the textures to PNG, export the object, and the gltf output accurately uses the model's UVs. This lets us examine default models with the textures showing correctly oriented by using only a texture.cfg, rather than a texture folder loaded with converted textures.
 
rhumbaflappy

rhumbaflappy

Administrator
Staff member
Resource contributor
Messages
5,779
Country
us-wisconsin
I made a new test of referencing textures in your models. ReferringTexturesTest.zip on Google Drive

It has a !rhumba-modellib-texture package to go into Community. That is an example texture library, much like asobo-modellib-texture. The manifest.json gives a clue as to how to configure that.
Also there is a project that experiments with referring textures via texture.cfg. It contains some models that in turn uses textures from an Asobo package, a Microsoft package, my texture package, and a local modelLib texture.

This is the result of a discussion at https://devsupport.flightsimulator.com/t/modellib-texture-fallbacks/6260/1
 
D

degorap

Messages
74
Country
argentina
Once you understand how the sim's VFS works, you can use any asset with the fallback metod.
 
You must log in or register to reply here.
Top