I am trying to model match the C-21A (military version of LJ35A) to be correctly placed at Scott Field AFB (KBLV). I finally was able to install AIG models to get LJ35 model(s). However, since there is no airline code for Air Mobility Command (ICAO code RCH, short for REACH) in the AIG files (not for LearJets, there are some for AMC B737s), PSXT seems to randomly assign LearJet models, replacing LJ35 (and its distinct tip tanks) with LJ45 (winglets). When it does assign LJ35A model, most of time time it uses red Deutsche Luftrettung red liveries, which looks completely out of place.

I read the manual to try to understand the process which PSXT uses to assign the models and liveries, and then tried to add a line with RCH airline code into one of the AIG LJ35 models so PXST would pick it up correctly from the RealTraffic data, but was not successful. 

I understand that this is rather unique situation, but any help in figuring out how to fine-tune the AIG models to RealTraffic data would be greatly appreciated. 

 I find using PVT as the icao code works very well with military traffic. I also use model matching on 2 and have no issues with C21's.

What you could do if you haven't already is let the sim run at KBLV and see what the psxt log shows you for coverage. It really does provide a lot of good info for the user to figure out what is getting picked up traffic wise.

3 hours ago, Dave_YVR said:

 I find using PVT as the icao code works very well with military traffic. I also use model matching on 2 and have no issues with C21's.

Sorry, what do you mean "use model mathching on 2"?

3 hours ago, Dave_YVR said:

What you could do if you haven't already is let the sim run at KBLV and see what the psxt log shows you for coverage. It really does provide a lot of good info for the user to figure out what is getting picked up traffic wise.

Ah, yes, that is a good idea. I only use PSXT for static traffic, so I did not think about using it this way. If I understand correctly, you suggest setting PSXT traffic from "parked" to "live", spawn at KBLV and then monitor logs to see what RealTraffic picks up and passes along to PSXT? 

One part is missing is that where do I put this info from the logs... Into the AIG model descriptions? There is an AIG civilian LJ35 model that looks almost exactly like C-21, except it has civilian N tail number. Right now PSXT spawns the Luftrettung red liveries which look completely out of place.

Edited July 30, 2025Jul 30 by Hurs_Sokira

So apparently no need to go to live traffic, logs show the planes that are reported by the Real Traffic, as follows:

          TRICK23* 84-0137           RCH LJ35 =5= AIGAIM_DRF Luftrettung Bombardier Learjet 35 - D-CCCB
          AAY3102* N204NV            AAY A320 =2= FSLTL A320 AAY Allegiant Air
          AAY3102* N204NV            AAY A320 =2= FSLTL A320 AAY Allegiant Air
          SPAR164* 84-0071           RCH LJ35 =5= AIGAIM_DRF Luftrettung Bombardier Learjet 35 - D-CDRF
          TRICK18* TRICK18           PVT LJ60 =2= AIGAIM_Fargo Jet Center Learjet 60 - N773SW

The TRICK and SPAR callsigns are US Air Force AMC callsigns, the question is: how PSXT chooses to assign the AIG models to them and why it chooses Luftrettung LJ35 livery for RCH airline code and LJ60 model for PVT airline. In aircraft.cfg file for LJ35 model these planes have "icao_airline=AMB" string and LJ60 model file has no airline code at all...

I inserted the line "icao_airline=RCH" for the Learjet 35A - N93LE livery, but it does not pick it up for some reason.

Edited July 30, 2025Jul 30 by Hurs_Sokira

1 hour ago, Hurs_Sokira said:

I inserted the line "icao_airline=RCH" for the Learjet 35A - N93LE livery, but it does not pick it up for some reason.

You must scan for libraries after you have done that, otherwise PSXT is not aware of your change. 

Do note that it is risky to change an AIG livery definition because it may (will) be overruled later...

Another problem could be that in my dBASE N93LE is defined as PVT, and this dBase value will overrule the livery definition.

You better fix this with a user defined regcode file.

I am on vacation now, will help you further when I am back.

Edited July 30, 2025Jul 30 by kiek

4 hours ago, Hurs_Sokira said:

Sorry, what do you mean "use model mathching on 2"?

Within PSXT itself, the Max aircraft matching depth.

 

4 hours ago, Hurs_Sokira said:

here is an AIG civilian LJ35 model that looks almost exactly like C-21, except it has civilian N tail number.

Ah ok, you haven't added your own custom C21 liveries from MAIW or something yet. They are available from there and work very well.

I was actually spotting at KBLV a few months ago trying to get some of the Lears and from what I recall, the coverage wasn't that great. Mostly from traffic not using their transponders until on the runway and turning them off upon landing. The best thing I saw was a KC135 on a training mission shooting the approach to BLV, going missed and continuing on their route.

 

2 hours ago, Hurs_Sokira said:

TRICK23* 84-0137           RCH

So here, the callsign is TRICK which doesn't work when you use that as your ICAO_airline= and RCH isn't ideal either as it doesn't actually use RCH. This is why I use PVT for nearly all of my US military AI aircraft ( I have about 4000+) and it hasn't gone wrong yet.

 

6 hours ago, Dave_YVR said:

Ah ok, you haven't added your own custom C21 liveries from MAIW or something yet. They are available from there and work very well.

 

Wasn't aware of MAIW, thank you for bringing it up. I can't find the C-21 livery for MSFS2020 though, it looks like there are older ones for FS9. And the matching problem would still be the same, the type code for C-21 is LJ35, so I need to somehow force it to be picked up over the other LJ models.

 Paints for FS9,FSX, P3d and MSFS are all interchangeable. It's just a matter of knowing what to do. It's a steep learning curve but is actually super easy once you get the hang of it. I taught myself using the AIGAIM aircraft as what to do. I have  seen this tutorial which should help a lot.    https://aitraffic.ch/Flightplans/Tutorial/MSFS_AI_Traffic_tutorial.pdf 

The best pack to grab would be this one but it will require some hands on to get it working in MSFS.

https://militaryaiworks.com/download-hangar/file-library/download/109-compiled-for-p3d-compatible-with-p3dv2-p3dv6/1738-maiw-htai-bombardier-learjet-c-21a-conversion.html

 

2 hours ago, Hurs_Sokira said:

And the matching problem would still be the same, the type code for C-21 is LJ35, so I need to somehow force it to be picked up over the other LJ models.

PSXT will pick the liveries based on you adding in the atc_id to your C21's such as atc_id=84-0137  as well as using PVT for the ICAO.