Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

MTL AI Models

Featured Replies

On 7/9/2026 at 10:38 AM, icrookham said:

Nico/Dave

Thanks for the input. Still having a couple of problems with amending the aircraft.cfg files to reflect the correct ICAO airline codes suggested. I change the title to a valid ICAO code using the correct syntax, save the changes but find that on running the sim subsequently some of the changes revert back to the original entries. Do you know if some of the IVAO models are write protected or am I doing something wrong by missing a step?

By the way the support offered is first class-many thanks.

Ian

It is indeed easier what Dave said, define your own regcode file as desribed in the Manual Appendix (then you do not need to edit aircrfat.cfg files):

In the input\my_regcodes folder, you may put one or more text files. The name is not relevant, but it must be unique, with extension .txt.

In the file one should specify the (exact) title of the livery followed by a semicolon, followed by a list of registration codes separated by commas. A livery title may not appear on more than one line.

Liveries that have just one registration code in an offline file, will be treated as being special, they will only show up as live aircraft, not as static parked aircraft.

 If you add ;# to a line, all registration codes will be treated as special, for example:

AIGAIM_easyJet Europe Airbus A320-200SL - Europcar;OE-IVC,OE-IVT;#

If you specify only a livery title, with no registration codes, PSXT will treat it as a “don’t use” livery.

Edited by kiek

  • Replies 46
  • Views 609
  • Created
  • Last Reply

Top Posters In This Topic

  • Author

Hi Nico

Thanks-I have created several regcode files so I will see how they perform.

Ian

  • Author

Hi Nico

Had a chance to see what is happening but not sure I am getting the expected results. Here is an extract of my log:

17275 airports read

6269 liveries read from output\LiveriesScanned.xml

6269 livery titles

254 in-line regcode clashes, see 'output\errors\InlineRegcodes.txt'

6389 liveries read from AIG-regcodes.xml

1 livery read from input\my_regcodes\100ARS.txt

2 liveries read from input\my_regcodes\67SOS.txt

3 liveries read from input\my_regcodes\C5MGalaxy.txt

4 liveries read from input\my_regcodes\CC130J.txt

5 liveries read from input\my_regcodes\CV22B.txt

6 liveries read from input\my_regcodes\Ramstein.txt

Offline regcode files processed, results can be found in 'output\info\OfflineRegcodes.txt'

1946 special liveries

1900 unique liveries

23994 registration codes

759 airlines, 142 pax aircraft models and 43 cargo aircraft models

330 similar model definitions

I can see that the the myregcodes files that I have created have been read but taking Ramstein.txt(based C130's) as an example (but several other of my created my regcodes files are the same) I have 15 individual regcodes specified but only 6 have been read. Have I done something wrong or are the other regcodes being picked up elsewhere? Also I have had to specify the livery as IVAO_C130H as there isn't a C130J available through IVAO and is this where there may be a problem?

Ian

Normally PSXT will show in the log if there's an error in a regcode file. If they aren't showing up in the log at all, that is pretty weird. Can you post the contents and title of one of the regcode files that isn't working?

Using the C130H in place of the J isn't an issue. I have dozens of examples where I have subbed in retro liveries and types and they all work fine. AIG has converted the C130E, H and J's but there are limited packages available from them at the moment but you can add in your own custom ones.

i7-13700KF, 64gb DDR5 6000,  RTX 4080, Win 11, MSFS 2024

  • Author

Hi Dave

Thanks for replying. Here is the regcode file I created titled 100ARS:

IVAO_K35R;57-2605,58-0095,58-0100,58-0125,59-1464,59-1470,59-1475,59-1511,60-0324,60-0333,60-0335,60-0353,60-0355,61-0315,62-3540,63-8008,63-887

In this case the log shows only one livery having been read but just noted that the final code is missing an 8 at the end but presumably this should not make a difference.

Ian

14 minutes ago, icrookham said:

In this case the log shows only one livery having been read but just noted that the final code is missing an 8 at the end but presumably this should not make a difference.

The regcodes in your \input\my_regcodes\100ARS.txt are all mapped to the livery with title IVAO_K35R. Hence, if such a regcode is detected in RT data, PSXT will match that aircraft with that livery.

EDIT:

In the Log you must see something like this (example):
Processing regcodes file 'input\my_regcodes\test.txt'

2 liveries read from input\my_regcodes\test.txt


Edited by kiek

  • Author

Hi Nico

So what I'm seeing in the log is that RT recognised, for example, that one code out of the 15 include in the 100ARS regcode file was active at the time, and not that the file was not read properly?

Ian

Edited by icrookham
clarification

14 minutes ago, icrookham said:

You can see in \output\OfflineRecodes.txt what he has done with your file. Look at the end:
Processing files in input\my_regcodes.

EDIT: it should say 15 new regcodes added ... or something like that

Edited by kiek

  • Author

Hi Nico

Yes I am seeing those sort of results but weirdly I tracked 4x KC45A aircraft into RAF Mildenhall a little earlier but despite having the exact regcodes for these aircraft, they displayed as an AIGAIM 757 model in USAF markings which I had previously downloaded through the aig-aitragfic-oci rather than the IVAO_B762 model within the regcodes file I had created.

Ian

You are meaning the KC46 (B762). Have you seen any other of the IVAO B762's working in the sim through PSXT? I know quite a few of the models don't work in 2024 for whatever reason. I can't say for the KC46 as I use an FAIB B762 painted to look like the KC46. It doesn't have the drogues or boom, but the model is sound and looks good. Same with the P-8, I use a newer MGAI model and it looks quite good!

i7-13700KF, 64gb DDR5 6000,  RTX 4080, Win 11, MSFS 2024

  • Author

Hi Dave

Thanks for the reply.Yes KC46-finger trouble! Can't say re any other IVAO B762's as I only have the MTL KC46 repaint. Interesting to hear that some of the models don't work in 2024 but the fact PSXT substituted the 757 might indicate it is not recognised. The only other thing I could think might affect it is the matching level which is set at 3 although why that should be the case I'm not clear.

Ian

So I added the MTL B762 and ironically it too is the FAIB just converted differently than how AIG did theirs. I'd still prefer to use the AIG version as I trust their quality more than any other AI dev. Matching at 3, you will see some different assignments. 2 is by far my preference.

As for why you aren't seeing them, again it could be something to do with modifying the MTL variants (I've had mixed success). The C17 for instance, is the same one used from MAIW and has EVERY operational serial, same with the E3A Sentry, T-6 Texan II as well as the T-38 Talon for starters.

I did notice for a few KC46's in my setup that PSX in the log said that the reg was unknown or something similar so maybe I'll forward on the regcode that I have on them so far and see if that helps.

i7-13700KF, 64gb DDR5 6000,  RTX 4080, Win 11, MSFS 2024

10 hours ago, icrookham said:

Hi Nico

Yes I am seeing those sort of results but weirdly I tracked 4x KC45A aircraft into RAF Mildenhall a little earlier but despite having the exact regcodes for these aircraft, they displayed as an AIGAIM 757 model in USAF markings which I had previously downloaded through the aig-aitragfic-oci rather than the IVAO_B762 model within the regcodes file I had created.

Ian

The Log shows the matchings, post it here then I can have a look.

  • Author

Log as requested.

Log

12 Jul 2026 14:27Z PSXT version 15.7.1 for MSFS 2020/2024

********************************** parameters **********************************

from 'C:\Users\icroo\AppData\Roaming\PSXT\parameters.xml'

SCAN_AIRPORTS=false

SCAN_LIVERIES=false

PSX_SERVER_HERE=true

COLLAPSED=false

ALWAYS_SCAN_AIRPORTS=false

LIG_PRIORITIZE=true

LIG_AUTOMATIC=true

COLLISION_USER_GND=false

COLLISION_USER_AIR=false

COLLISION_LIVE_PARKED_GND=true

RANDOM=true

ALWAYS_ON_TOP=false

AEROWINX=false

GUID_CHANGES=true

OBJECTID_LIST=false

NAV_LIGHTS_WHILE_PARKED=true

AUTO_RANGE=false

LIGHT_AIRCRAFT=true

HELICOPTERS=true

HIGH_PERF_AIRCRAFT=true

SIM_TIME=false

KEEP_SIM_TIME_PAR=false

WEEK=false

PARK_SOFT=false

RT_PARKTRAFFIC_ONLY=false

AUTO_PARK=true

MAIN_WINDOW_X=2246

MAIN_WINDOW_Y=407

PARKING_INTERVAL_MINUTES=20

LAST_EPOCH_TIME:=0

BLOCK_HEXIDDEC=0

TCAS_FL=180

AIRP_HEIGHT=18000

MAX_FIT=47

RANGE_GROUND=10

RANGE_1=20

RANGE_2=40

RANGE_3=50

RANGE_ABOVE=60

FLIGHT_LEVEL_1=100

FLIGHT_LEVEL_2=200

FLIGHT_LEVEL_3=300

RANGE=50

HOLDING_THRESHOLD_METERS=250

MAX_HOLDING_MINUTES=20

TIME_SHIFT_DAYS=0

TIME_SHIFT_HOURS=0

MATCHING_DEPTH=3

TCAS_FL=180

TIME_SHIFT_MINS=0

MAX_PARK_SEL=500

MAX_LIVE_SEL=500

AIRP_RANGE=30

AIRP_HEIGHT=18000

parking_percentage=100

PROGRAM_VERSION="15.7.1"

MSFS_INSTALL_PATH="C:\Users\icroo\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages"

MSFS_2024_INSTALL_PATH="C:\Users\icroo\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages"

AI_PACKAGE_SELECTOR="AIG, FSLTL, JF, MTL"

AIG_VERSION="14.0.8"

ARCHIVES_VERSION="15.0.98"

DBASE_VERSION="15.0.153"

WEEKLY_TRAFFIC_AIRPORTS_VERSION="17.0.11"

AIRPORTS_VERSION="15.0.41"

LIV_SCAN_VERSION="0.0.3"

ADDONS_SCAN_VERSION="14.5.1"

PORT_NUMBER="10747"

lfolder0=""

lfolder1=""

lfolder2=""

lfolder3=""

lfolder4=""

lfolder5=""

lfolder6=""

lfolder7=""

lfolder8=""

lfolder9=""

BLOCK_AIRCRAFT=""

BLOCK_CALLSIGN=""

BLOCK_REGCODE=""

DESTINATION=""

ALL_AIR_GND_SELECTOR="All traffic"

SIM_CHOICE="MSFS 2024"

RT_CHOISE="RT Direct"

********************************************************************************

Radius parameters okay

No license found in 'C:\Users\icroo\AppData\Roaming\InsideSystems\RealTraffic.lic'. Problem: [json.exception.parse_error.101] parse error at line 1, column 71: syntax error while parsing value - invalid literal; last read: '"[email protected]"}no'; expected end of input

Your RealTraffic license was taken from 'RealTraffic.lic'

msfs program version at web = 15.7.1

msfs version up-to-date

maintenance version up-to-date

airports version up-to-date

aig version up-to-date

archives version up-to-date

liveries version up-to-date

addons version up-to-date

Downloaded 'https://www.lekseecon.nl/downloads/15/dbase.enc' to 'input\dbase.enc'

DBASE_VERSION="15.0.154"

dbase updated to 15.0.154

weekly version up-to-date

2636 ICAO model codes

7 prefixes

6980 ICAO airline codes

93 cargo operators

148 fixes

69840 dbase records read

17275 airports read

6268 liveries read from output\LiveriesScanned.xml

6268 livery titles

254 in-line regcode clashes, see 'output\errors\InlineRegcodes.txt'

6389 liveries read from AIG-regcodes.xml

1 livery read from input\my_regcodes\100ARS.txt

2 liveries read from input\my_regcodes\67SOS.txt

4 liveries read from input\my_regcodes\Brize.txt

5 liveries read from input\my_regcodes\C5MGalaxy.txt

6 liveries read from input\my_regcodes\CC130J.txt

7 liveries read from input\my_regcodes\CV22B.txt

8 liveries read from input\my_regcodes\KC35R.txt

9 liveries read from input\my_regcodes\KC46A.txt

10 liveries read from input\my_regcodes\RAF A330.txt

11 liveries read from input\my_regcodes\Ramstein.txt

Offline regcode files processed, results can be found in 'output\info\OfflineRegcodes.txt'

1946 special liveries

1900 unique liveries

23993 registration codes

760 airlines, 142 pax aircraft models and 43 cargo aircraft models

330 similar model definitions

Category Heavy: 1116 pax liveries and 487 cargo liveries

A306,A310,A332,A333,A338,A339,A343,A346,A359,A35K,A388,A3ST,A400,B742,B744,B748,B752,B753,B762,B763

B764,B772,B773,B77L,B77W,B788,B789,B78X,C130,C17,C30J,K35R

Category Large: 3632 pax liveries and 301 cargo liveries

A19N,A20N,A21N,A318,A319,A320,A321,AJ27,AT43,AT44,AT45,AT46,AT72,AT73,AT75,AT76,B190,B38M,B39M,B712

B732,B733,B734,B735,B736,B737,B738,B739,BCS1,BCS3,CRJ1,CRJ7,CRJ9,CRJX,D328,DC91,DC93,DH8A,DH8B,DH8C

DH8D,DHC6,E120,E170,E190,E195,E295,E35L,E75L,E75S,F100,F50,F70,FA7X,J328,JS41,MD81,MD82,MD83,P8

SB20,SF34,SH36

Category Buzjets: 765 pax liveries and 28 cargo liveries

B350,BE20,BE99,BE9L,BN2P,BN2T,C402,C441,C56X,CL30,CL35,CL60,CRJ2,E135,E145,E45X,E50P,E55P,GL5T,GLEX

GLF4,GLF5,GLF6,H25B,LJ31,LJ35,LJ45,LJ60,PC12

Category Light: 228 pax liveries and 37 cargo liveries

C172,C177,C182,C206,C208,C210,C414,C72R,C82R,F406,G115,P210,P28A,SR22,SW3,SW4,TEX2

Category Rotorcraft: 5 pax liveries

EC35,EC45,H47,H64

Category HighPerf: 5 pax liveries

EUFI,F35

No generic liveries

173 park airports read from 'my_park_airports.txt'

Waiting for MSFS 2024 ...

MATCHING_DEPTH=2

14:27:54 Exiting: USER CLOSED SIM

12 Jul 2026 14:27Z

Edited by icrookham
Title

Hi Ian,

The complete Log.txt please with the matchig lines...
Nico

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.