Some advice please from anyone using MTL models.

I have downloaded several MTL military models within the IVAO_MTL folder created by the MTL installer in my Community folder in MSFS2024 but am not seeing them within the sim even though they are showing up on the RT radar screen. Case in point was an RAF A400 yesterday at RAF Brize Norton which was clearly visible on the RT radar screen right down to landing and taxi.

I have read Nico's appendix re liveries and checked out the aircraft.cfg files to look for any issues and the only one I could see related to the RAF A400 was in the title line which was title="A400RAF" which if I understand Nico's appendix will not be read properly as "RAF" is not a valid ICAO code. I have changed this to "A400RFR" which is a valid RAF ICAO code but still the same problem. Also checked the PSXT logs and can see A400 in the list of aircraft read and the also RFR livery. Run out of ideas so any help would be greatly appreciated.

Ian

What were the Callsign and Regcode in the RT radar screen of that aircraft?

HI Nico

Believe it was RRR4953 and ZM417.

Ian

23 minutes ago, icrookham said:

Believe it was RRR4953 and ZM417.

Aha, that makes sense. Instead of A400RFR, name your livery A400RRR. Then you will see it in the sim.

FYI:
This is what I have in my dbase about ZM417 (and others): (r=regcode, a=airline, m=model, c= cargo)

<d r="ZM400" a="RRR" m="A400" c="true" />

<d r="ZM401" a="RRR" m="A400" c="true" />

<d r="ZM402" a="RRR" m="A400" c="true" />

<d r="ZM403" a="RRR" m="A400" c="true" />

<d r="ZM404" a="RRR" m="A400" c="true" />

<d r="ZM405" a="RRR" m="A400" c="true" />

<d r="ZM406" a="RRR" m="A400" c="true" />

<d r="ZM407" a="RRR" m="A400" c="true" />

<d r="ZM408" a="RRR" m="A400" c="true" />

<d r="ZM409" a="RRR" m="A400" c="true" />

<d r="ZM410" a="RRR" m="A400" c="true" />

<d r="ZM411" a="RRR" m="A400" c="true" />

<d r="ZM412" a="RRR" m="A400" c="true" />

<d r="ZM413" a="RRR" m="A400" c="true" />

<d r="ZM414" a="RRR" m="A400" c="true" />

<d r="ZM415" a="RFR" m="A400" c="true" />

<d r="ZM416" a="RRR" m="A400" c="true" />

<d r="ZM417" a="RRR" m="A400" c="true" />

<d r="ZM418" a="RRR" m="A400" c="true" />

<d r="ZM419" a="RRR" m="A400" c="true" />

<d r="ZM420" a="RRR" m="A400" c="true" />

<d r="ZM421" a="RRR" m="A400" c="true" />

Edited July 6Jul 6 by kiek

Thanks Nico. Just as an aside, what happens if the aircraft has a callsign eg Centaur, Judgement etc does it default to the registration?

Ian

3 hours ago, icrookham said:

Just as an aside, what happens if the aircraft has a callsign eg Centaur, Judgement etc does it default to the registration?

Yes, the registration is leading (if in my dbase).

Hi Nico

Is it possible to view the database with the details of the regcodes etc (as shown above for the A400) to see what is or is not covered or is that a closed file in your software? I ask because I have a similar problem with the MTL RAF A332 model. As I understand it I can deal with the VIP texture by including its reg code ZZ336 in the atc_id within the aircraft.cfg file but I also have another texture file for the non VIP version.

Ian

You can find the info at the FlightRadar site, just google with the regcode.
But here a few lines:
<d r="ZZ171" a="RRR" m="C17" c="true" />

<d r="ZZ172" a="RRR" m="C17" c="true" />

<d r="ZZ173" a="BCT" m="C17" c="true" />

<d r="ZZ174" a="RRR" m="C17" c="true" />

<d r="ZZ175" a="RRR" m="C17" c="true" />

<d r="ZZ176" a="RFR" m="C17" c="true" />

<d r="ZZ177" a="RRR" m="C17" c="true" />

<d r="ZZ178" a="BCT" m="C17" c="true" />

<d r="ZZ330" a="RFR" m="A332" c="true" />

<d r="ZZ331" a="RFR" m="A332" c="true" />

<d r="ZZ332" a="RRR" m="A332" c="true" />

<d r="ZZ333" a="RRR" m="A332" c="true" />

<d r="ZZ334" a="RRR" m="A332" c="true" />

<d r="ZZ335" a="RRR" m="A332" c="true" />

<d r="ZZ336" a="RRR" m="A332" c="true" />

<d r="ZZ337" a="RRR" m="A332" c="true" />

<d r="ZZ338" a="RRR" m="A332" c="true" />

<d r="ZZ343" a="RRR" m="A332" c="true" />

<d r="ZM300" a="RFR" m="G12T" />

<d r="ZM301" a="RFR" m="G12T" />

<d r="ZM302" a="RFR" m="G12T" />

<d r="ZM303" a="RFR" m="G12T" />

<d r="ZM304" a="RFR" m="G12T" />

<d r="ZM305" a="RFR" m="G12T" />

<d r="ZM306" a="RFR" m="G12T" />

<d r="ZM307" a="RFR" m="G12T" />

<d r="ZM308" a="RFR" m="G12T" />

<d r="ZM310" a="RFR" m="G12T" />

<d r="ZM311" a="RFR" m="G12T" />

<d r="ZM312" a="RFR" m="G12T" />

<d r="ZM313" a="RFR" m="G12T" />

<d r="ZM314" a="RFR" m="G12T" />

<d r="ZM315" a="RFR" m="G12T" />

<d r="ZM317" a="RFR" m="G12T" />

<d r="ZM318" a="RFR" m="G12T" />

<d r="ZM319" a="RFR" m="G12T" />

<d r="ZM320" a="RFR" m="G12T" />

<d r="ZM321" a="RFR" m="G12T" />

<d r="ZM322" a="RFR" m="G12T" />

<d r="ZM323" a="RFR" m="TEX2" />

<d r="ZM324" a="RFR" m="TEX2" />

<d r="ZM325" a="RFR" m="TEX2" />

<d r="ZM326" a="RFR" m="TEX2" />

<d r="ZM327" a="RFR" m="TEX2" />

<d r="ZM328" a="RFR" m="TEX2" />

<d r="ZM329" a="RFR" m="TEX2" />

<d r="ZM330" a="RFR" m="TEX2" />

<d r="ZM331" a="RFR" m="TEX2" />

<d r="ZM332" a="RFR" m="TEX2" />

<d r="ZM333" a="RFR" m="E50P" />

<d r="ZM334" a="RFR" m="E50P" />

<d r="ZM335" a="RFR" m="E50P" />

<d r="ZM336" a="RFR" m="E50P" />

<d r="ZM337" a="RFR" m="E50P" />

<d r="ZM340" a="RFR" m="TEX2" />

<d r="ZM341" a="RFR" m="TEX2" />

<d r="ZM342" a="RFR" m="TEX2" />

<d r="ZM343" a="RFR" m="TEX2" />

Thanks Nico

Last question-I assume those entries go into the input, my regcodes folder and what is the significance of the<d?

Ian

2 hours ago, icrookham said:

Thanks Nico

Last question-I assume those entries go into the input, my regcodes folder and what is the significance of the<d?

Ian

No, that is not necessary. You have all these definitions in /input/dbase.enc. PSXT will use these to match a livery.
That d means dbase record. It is just xml stuff.

A400RFR is NOT an ICAO code. Try icao_airline=RRR and leave the atc_id= blank

37 minutes ago, Dave_YVR said:

A400RFR is NOT an ICAO code. Try icao_airline=RRR and leave the atc_id= blank

? RFR is an ICAO airline code (Royal Air Force), check it here:

The Aviation Codes Web Site - IATA / ICAO Airline Code/Designator / Code Database Search

Edited Wednesday at 05:37 PM5 days by kiek

RFR yes is an ICAO code, but the Transports would use RRR for theirs. The op mentioned "changed this to "A400RFR" which is a valid RAF ICAO code".

Edited Wednesday at 06:11 PM5 days by Dave_YVR

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

Personally, I have left the A400's titles alone and use a regcode file for them as like many Mil flights, they more often don't use an ICAO at all but a Military callsign. It has so far worked every time.

Edited Thursday at 03:11 PM4 days by Dave_YVR