[Response....] FCDU not selecting aircraft according atc-id

[mjl1966]

PMDG J41 -- three liveries.

One of them has this in flightsim.3:
atc_id=N14382

Aircraft config:
Created a new TYPE (not override) that specifically calls out this atc-id in the Reg field. (N14382)

Checked OFF Passenger seats.

Left Cargo Jumpseats checked.

It is my understanding this says, "I am a cargo aircraft."

When I open FCDU, the first page correctly identifies the aircraft loaded as JS41 N412GA

Click Select DEST -- enter my destination.

Click Make CARGO so RSK 4 says "Type is Cargo"

Click PROCEED and see that I have 28 pax.

So - this is iteration 5 of trying to get FCDU to discern between different liveries in aircraft.cfg.  This one last iteration at least saw it by N number - but still doesn't cooperate.

I want one livery to be pax, another to be cargo.  Creating new type file using either atc-type defined in [fltsim.x] section or referencing explicit atc-id in [fltsim.x] section do not seem to work.

What am I missing?

------------------------------

To be clear:  I have tried to reference atc-id as shown below in the Reg field in Aircraft Characteristics.  I have also tried setting the atc-type to JS41-C and putting that in Type field in Aircraft Characteristics.


[fltsim.3]
title=PMDG Jetstream 41 US
sim=pmdg_j41
model=
panel=
sound=
texture=LCC
kb_checklists=
atc_id_color=0xffffffffff
atc_id=N412GA
atc_airline=US
atc_flight_number=4100
atc_type=BRITISHAEROSPACE
atc_model=JS41-C
ui_manufacturer="British Aerospace (BAe)"
ui_type="JetStream 4100"
ui_variation="US Airways Express"
ui_typerole="JetStream 4100"
ui_createdby="PMDG"
description=PMDG BAe JetStream 4100\nPrecision Manuals Development Group \nwww.precisionmanuals.com\nPMDG Developer and Customer Forum available at our website. \nSounds Developed by PMDG \nThank you for supporting PMDG!\n
atc_parking_types=GATE,RAMP
visual_damage=0
atc_heavy=0
airline_name=US
galley=fore


[Travis]

Well... it ought to work.

I do know that using an Override (PAX) file for my default 738, and having several Override (PAX) atc_id files... and one Override (Cargo) atc_id file... works for me.

But I haven't used a Type config file for many years, so I'll give this a test next week depending on how my new PC gets sorted out.

Since you're referencing loading in the FCDU, please shoot me one or two FCDU log files from your most recent attempts, and include at least one of your most recent ADMIN log file(s).

Also please include your two Type config files so I can try to replicate this on my (old or new) system.

Best,

[mjl1966]

Well, I tried an override... so let's start with that.

I notice the admin log says this:

FCDU.EXE:: 21:14:17 No reg-specific config found (-1). Checking for general types.
FCDU.EXE:: 21:14:17 Loaded Aircraft (4): C:\PROGRAM FILES (X86)\STEAM\STEAMAPPS\COMMON\FSX\FSCaptain\Aircraft\J41.cfg

My attached override is intended to be reg-specific.

I'm missing a step that's required to make FSC read reg-specific stuff.  Just can't figure out what.



JS41-N412GA.cfg (2.1 KB)

FCDU_20220301_211417.log (396.66 KB)

[Travis]

To be an Override file, the file's name must first match the SimObject folder name. Looking at your FCDU log file, I see this:

FCDU.EXE:: 21:14:17 AirFile from SimConnect: C:\Program Files (x86)\Steam\steamapps\common\FSX\SimObjects\Airplanes\PMDG_JS4100\pmdg_j41.air

So I would recommend that you start by naming your default Override file as "PMDG_JS4100.cfg"

Then for your reg-specific Override file, use an underscore character followed by the tail number.

So I would recommend that your reg-specific override file be named "PMDG_JS4100_N412GA.cfg".

The details in your configuration file look fine.

------

I always strongly suggest that Override files be used for your go-to aircraft.  Because Override files can account for "different models in different folders," and Override files work seamlessly with Load Maps, they're my preferred configuration source.

When I first started using FSCaptain in FSX, I had three Cessna Caravan models - the FSX default 208, the ported-from-FS9 208 Amphibian, and a third party 208.  They had slightly different speeds and burn rates, so I needed Override files as soon as Dutch added them to the mix!

However if a Captain only has one aircraft of a certain type, and if that Captain doesn't care about Load Maps, then Type configuration files should work fine.

------

I'm still a few days away from having my PC properly configured for general simming and for FSCaptain debugging, so I hope this helps for now.

Best,

[Travis]

MJL,

Did my suggestion work for you or are you still having the problem as you described?

Best regards,