Texture.cfg (FSX)

From FSDeveloper Wiki
Revision as of 14:38, 1 November 2007 by N4gix (talk | contribs) (New page: There is an acknowledged "bug" in FSX's "Texture fallback scheme" (aka: texture.cfg) that will '''sometimes''' cause FSX to lose track of where common textures are located, '''and''' also ...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

There is an acknowledged "bug" in FSX's "Texture fallback scheme" (aka: texture.cfg) that will sometimes cause FSX to lose track of where common textures are located, and also cause the thumbnail.jpg images to become "out of synch."

The "solution" for all new models is to

(a) use the \texture folder only for "common textures" and have dedicated \texture.variation folders for all the unique textures for every livery...

...and...

(b) write a custom texture.cfg file that will provide accurate fallback paths.

For example:

    ..\texture.common
        all common textures.dds
    ..\texture.Livery1
        all unique textures for Livery1.dds
        thumbnail.jpg
        texture.cfg
    ..\texture.Livery2
        all unique textures for Livery2.dds
        thumbnail.jpg
        texture.cfg


texture.cfg

    [fltsim]
    fallback.1=..\texture.common
    fallback.2=..\..\..\..\Scenery\Global\texture
    fallback.3=..\..\..\..\Texture


The reason for fallback.3 is to provide a direct path for the following common textures which may be called for by FSX:

    Fresnel_Ramp.dds
    FresnelTest.bmp
    FresnelWater.bmp
    GENFresnel.dds
    GlobalEnv_AC_Chrome.dds
    GlobalEnv_AC_Chrome_32.dds
    GlobalEnv_AC_Chrome_64.dds
    GlobalEnv_AC_Chrome_128.dds
    GlobalEnvTest.dds