• 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 v3 Multiple Aircraft Folders

Messages
10,163
Country
us-arizona
Hey all,

So... I am trying to get 3 versions of my latest plane to show up in the sim. I have one plane, 4 models. 2 Models are 'single pilots' (male and female). 1 Model is a Couple. 1 Model is a Group of 4 people. The idea is to break the planes into separate folders so that I have 3 versions of weight load-outs; 1 person, 2 people, 4 people. Easy enough. Second, I linked everything via Alias in the configs of the second two folder systems, so that Panel, Sound, and Textures are all brought over or directed to the primary aircraft folder.

Folder one (single pilot) works fine.

Folder two and folder three cause the entire plane selection library to lock up. (Searching). It doesnt actually lock up the sim, it just sits there looking for planes in the library. So my second two folders must have thrown it a 'wobbly'.

* I changed all that I knew to change in the Aircraft configs.
* I have Alias Panel, Sound, Texture(s) configs, all linked back to the primary 1st folder.

What on Earth could be wrecking it? I have looked it over and looked it over. Its all in order... This system worked on P3D V2. I wonder if V3 does not support this? Anyone see the issue that I might be missing?

Sound Alias;
[FLTSIM]
alias=LHC_Trinidad_TB21GT\sound

Panel Alias;
[FLTSIM]
alias=LHC_Trinidad_TB21GT\panel

Texture Alias;
[fltsim]
alias=LHC_Trinidad_TB21GT\texture
fallback.1=..\texture
fallback.2=..\..\..\..\Scenery\Global\texture
fallback.3=..\..\..\..\..\..\Scenery\Global\texture
fallback.4=LHC_Trinidad_TB21GT\texture

Specific Texture Alias;
[fltsim]
alias=LHC_Trinidad_TB21GT\texture.N221MA
fallback.1=..\LHC_Trinidad_TB21GT\texture.N221MA
fallback.2=..\LHC_Trinidad_TB21GT\texture
fallback.3=..\texture
fallback.4=..\..\..\..\Scenery\Global\texture
fallback.5=..\..\..\..\..\..\Scenery\Global\texture


Primary AIR file name: LHC_Trinidad_TB21GT.air
Primary Registry Block; (main)

[fltsim.0]
title=Trinidad 0
sim=LHC_Trinidad_TB21GT
model=
panel=
sound=
texture=N887TB
kb_checklists=TB_Checklist
kb_reference=TB_Reference
atc_id=N887TB
prop_anim_ratio=1.03
ui_manufacturer=Socata Aerospace
ui_type=Trinidad TB21 GT Turbo
ui_variation="N887TB"
ui_createdby="Lionheart Creations"
ui_typerole="Single Engine Prop"


Secondary AIR file name: LHC_Trinidad_TB21GT_Couple.air
Secondary Typical Registry Block (2nd folder set)

[fltsim.0]
title=Trinidad Two Passenger 0
sim=LHC_Trinidad_TB21GT_Couple
model=Couple
panel=
sound=
texture=N887TB
kb_checklists=TB_Checklist
kb_reference=TB_Reference
atc_id=N887TB
prop_anim_ratio=1.03
ui_manufacturer=Socata Aerospace
ui_type=Trinidad TB21 GT Turbo Couple
ui_variation="N887TB Couple"
ui_createdby="Lionheart Creations"
ui_typerole="Single Engine Prop"



Bill
LHC
 
This is what I would do. Grab paper and pencil (remember those things :rolleyes:) and write out the folder and file hierarchy for reference, sometimes you can get a clue by doing this.
Remove all the models and install only the primary model, test. If all is well install the second model with its alias links and test. Continue until you find the problem. I'm sure it's something simple you overlooked.
 
Bill, I suspect that your fallback.x paths aren't going back far enough. The Milviz B55/E55 release is set up in a similar fashion to that you are wanting to use.

\SimObjects
..\Airplanes
..\..\Beech_Baron_B55 Milviz
..\..\Beech_Baron_E55 Milviz

The E55's ..\texture texture.cfg alias is:
Code:
[fltsim]

fallback.1=..\..\Beech_Baron_B55 Milviz\texture
fallback.2=..\..\..\..\Texture
fallback.3=..\..\..\..\Scenery\Global\texture
Note that fallback.1 redirects back down two levels all the way to ..\SimObjects

The individual ..\texture.xxx fallback.x entries follow the same pattern:
Code:
[fltsim]

fallback.1=..\..\Beech_Baron_B55 Milviz\texture
fallback.2=..\..\Beech_Baron_B55 Milviz\Texture.4062
fallback.3=..\..\..\..\Texture
fallback.4=..\..\..\..\Scenery\Global\texture
 
Texture Alias;
[fltsim]
alias=LHC_Trinidad_TB21GT\texture
fallback.1=..\texture
fallback.2=..\..\..\..\Scenery\Global\texture
fallback.3=..\..\..\..\..\..\Scenery\Global\texture
fallback.4=LHC_Trinidad_TB21GT\texture
BTW, "alias=" has no meaning in a texture.cfg file, and may also be contributing to the problem you're having. In any case, delete that line entirely!

Also, the fallback.3 path does not exist on any of our machines. It was used by ACES when developing this scheme to point to ..\texture folders on their own remote server! They should have removed it from the sim prior to burning the disks for delivery! :)
 
Ok, edited my work, two notches back. Plane finally showed up! I found I cannot have the ..\..\ on Panel and Sound configs and they rely on Alias=.

However, my textures still wouldnt work. I tried adding in Alias= and they worked! For some reason, yours works without and mine requires the Alias= string.

Bill, are you testing in FSX? I wonder if that is the difference. I am testing in V3.

This is a typical functioning Alias for a texture folder in another plane;

[fltsim]
alias=LHC_Trinidad_TB21GT\texture.N887TB
fallback.1=..\..\LHC_Trinidad_TB21GT\texture.N887TB
fallback.2=..\..\LHC_Trinidad_TB21GT\texture
fallback.3=..\..\..\..\texture
fallback.4=..\..\..\..\Scenery\Global\texture


Thanks again Bill for setting me correct on the ..\..\
 
I'm using this exact scheme on FSX, FSX:SE, and P3D v1, v2, and v3. I've also found that changes to these various .cfg files will not be recognized unless the sim is shut completely down and re-launched.

I worked out this system several years ago in an effort to keep the B55/E55 project installer down to a reasonable size, and also make file maintenance easier. In fact, the only "unique" files are the aircraft.cfg and xxx.air files for the two versions. ;)
 
You can also make the aircraft.cfg search for an .air file in another folder, so that's yet another file that can be shared across models.
 
Back
Top