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

P3D v1 Maximum Number of ..\..\..\ ?

Messages
10,163
Country
us-arizona
Hey guys,

Is there a maximum number of ..\..\..\ links we can go to link into a file from an aircraft?
 
I think not. You should, however, rarely need more than four or five anyway.
 
Why, Bill?

Assuming you have texture.cfg and start off in a texture folder, you need four to be in FSX root. If you specify more (as ACES do ... six) you are GKW - God Knows Where. May actually work on your (and their) computers but because you naturally forget that you did that you'll distribute those errant pointers world-wide in your uploads. And possibly slow up loading times.
 
I know. I needed it though.

My rig couldn't go over 4 units of ..\ oddly. I wish it could have done 6. At 5 units, they weren't seen for some reason.


Oddly, at 4 folders out, some folders only required 2 ..\ units.


crazy.
 
This is possibly the most "misunderstood" area of FS configuration. ACES did not help one bit by not sanitizing their own default texture.cfg file(s):
[fltsim]

fallback.1=..\texture
fallback.2=..\..\..\..\Scenery\Global\texture
fallback.3=..\..\..\..\..\..\Scenery\Global\texture
Note carefully that fallback.3 is a totally useless path for us. It "backtracks" so far that it actually leaves the FSX root folder entirely, and in actual fact points to a completely separate computer in their network, one where common files were stored so that everyone in the office was using the same textures.

So, ignoring fallback.3 entirely, it is clear that the furthest back in the default FSX heirarchy one should ever need to go is FOUR folder levels, as shown by the fallback.2 entry.

However, I have found that there are a few textures in the ..\FSX\Texture folder that are sometimes useful to include in the search paths, so I use this standard texture.cfg file in all of my projects:
Code:
[fltsim]

fallback.1=..\texture
fallback.2=..\..\..\..\Texture
fallback.3=..\..\..\..\Scenery\Global\texture
Consider the default default hierarchy of FSX:
Code:
FSX
    SimObjects
          Airplanes
               C172
                    Texture
                    Texture.1
                         Texture.cfg
     Texture
     Scenery
          Global
               Texture
fallback.1 in the texture.cfg file takes us back one level to the ..\C172 folder, then looks in the ..\Texture folder for our search path.

fallback.2 in the texture.cfg file takes us back four levels to the ..\FSX folder, then looks forward to the main ..\Texture folder for our search path.

fallback.3 in the texture.cfg file takes us back four levels to the ..\FSX folder, then looks forward to the main ..\Scenery\Global\Texture folder for our search path.

So the question I have Bill, is just why you would ever need more than four fallback levels? Give me an example and I'll tell you how to get there! :D
 
Well that explains it, lol... I was counting forward (total number of folders forward). I didn't know they were backsteps.

I had 4 to 5 and at one point 6 folder places 'forward' from the main FSX/P3D folder.

That's why the panel only needed 2. I couldn't figure that out.

Many thanks Bill for the tutorial.


I really torture myself with these 'variant' packages that have all versions of the aircraft model, like Pacer original classic; Pacer bush model; Pacer with newer panel; Pacer with floats for bush, classic, newer; and Tri Pacer new panel, Tri Pacer old panel. whewww... Getting myself stressed talking about it and its been finished for months.


Manfred,

Do you think that this can bog down frame rates? All of my textures are in the original locations. Only other 'system' folders are re-routed.


Bill
 
Last edited:
I really torture myself with these 'variant' packages that have all versions of the aircraft model, like Pacer original classic; Pacer bush model; Pacer with newer panel; Pacer with floats for bush, classic, newer; and Tri Pacer new panel, Tri Pacer old panel. whewww... Getting myself stressed talking about it and its been finished for months.

Manfred,
Do you think that this can bog down frame rates? All of my textures are in the original locations. Only other 'system' folders are re-routed.

Depends on how many texture files not present in the main livery set have to be hunted down by FSX searching all fallback folders. Typical example GlobalEnv_AC_Chrome etc. Probably won't make that much of a difference.

One route I have been following lately (with mixed success) is to address VC or other variants by specifying for one livery

fallback.1=..\texture.modernVC

and for another

fallback.1=..\texture.oldVC

In other words, it's one and the same model using different VC colors.
 
Last edited by a moderator:
Odd, I'd have thought "fallback..." was pretty much self-explanatory, but then I'm often given to think too much... :D
 
Texture.cfgs are a wonderful thing. With their help, you can cut the size of a model folder by a whopping 60% in some cases.
 
I am not using this for textures, but other systems in the package.

I can see how this would be radically hard on a computer with 30 or 40 textures, some being 2048 in size. I see your point there. This is only for panel and models, etc. Just a few files.


Odd, I'd have thought "fallback..." was pretty much self-explanatory, but then I'm often given to think too much...

N4gix


I didn't even know that's what one called them. sigh....

Good to know. Always learning.
 
Texture.cfgs are a wonderful thing. With their help, you can cut the size of a model folder by a whopping 60% in some cases.


Amen to that. Its so nice to be able to have a common main texture folder for the base textures and then have separate super small folders for the paint scheme variants.

Remember the FS9 days and before? eeks..... :eek:
 
In FS9 some kind of "fallbacks" can be easily implemented in the MDL file by inserting "..\" in the definition of texture names in the asm file.

Luka


I had heard about that.

Man, did we try all the tricks in expanding FS9 or what...!?

550,000 polygons in an FS9 model, lol... Loved it.
 
Man, did we try all the tricks in expanding FS9 or what...!?
Of course not. You can always edit something in FS9 asm files in order to make more efficient mdl. In FSX, I really miss this possibility. :stirthepo
 
Back
Top