• 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 Texture.cfg fallback works in P3Dv4 but not in FSX.

RicherSims

Resource contributor
Messages
574
Country
dominica
Using 1.6.5.

The texture fallback to a common folder located in My Documents works perfectly in P3Dv4 but does not work at all in FSX. The models load all black or do not load at all.

The work around is having multiple copies of the same files in both the common folder and the SODE texture folder which is obviously not ideal.

This is what the texture.cfg looks like:
Code:
[fltsim]
fallback.1=..\..\..\..\Scenery\Global\Texture
fallback.2=..\..\..\..\..\..\Scenery\Global\Texture
fallback.3=D:\Documents\Prepar3D v4 Add-ons\Richer Simulations\RS Common\Texture

I've also tried removing the first 2 fallbacks with no luck. The SODE.log reports no errors.
 
I think it is a limitation of FSX and how it handles those fallback paths.
More specifically, I think it does not support absolute paths, only relative. But I haven't found any info on this assumption in the official FS SDK, but when I once tested an absolute path, then the textures didn't show up.
 
Thanks for the reply @12bPilot.
I will have to move ahead with the less elegant solution as sometimes users install my products to completely different drives.
 
Just for the sake of information, the fallback.2 entry only existed on MS/ACES networked system. It is completely useless aside from confusing everyone...

Code:
fallback.1=..\..\..\..\Scenery\Global\Texture
fallback.2=..\..\..\..\..\..\Scenery\Global\Texture
 
... still happily present in most texture.cfg's in P3D V4.5 ....
 
... still happily present in most texture.cfg's in P3D V4.5 ....
Whether it is there or not, makes no real difference since the path doesn't exist and FSX/P3D will simply ignore it... :stirthepo
 
Back
Top