Dave_YVR

Lol.. Finding work arounds for when it doesn't work as planned. ;)

I also prefer to not scan as I have a few airports that still don't get seen by the scan (old marketplace purchases) so I have manually made my own my_thirdparty files for them and they work great, until the next airport scan.

The IVAO MTL models I find are VERY finicky if you mod them. Some work and some do not and I'm not sure why. But you also didn't conform to proper ICAO in the entries. The H300 isn't a Robinson and the H300 isn't an icao type. Try something like this. [GENERAL] atc_type =H269 atc_model =H269 Category = Helicopter performance ="" editable = 1 wip_indicator = 1 icao_type_designator =H269 icao_manufacturer =SCHWEIZER icao_model =300 icao_engine_type =Piston icao_engine_count =1 icao_WTC =L icao_generic=0 Also, did you edit the cfg entry for the actual aircraft under [fltsim.0] as well?

Sure no worries. Take the 737 Max 10 as an example. I take my AIA 737 Max 9, copy it and rename it AIA_B737-MAX10 FAKE. Then in the aircraft.cfg and under the [General] section simply change what is needed to conform to ICAO so that PSXT thinks that it's the type that you want. icao_type_designator=B3XM icao_manufacturer=BOEING icao_model=737 MAX 10

Thanks Nico! It's more appreciated than you know!

I'd love to have the liveriesscanned file back as well. I use it multiple times a day EVERY day. It was an awesome feature to have imo.

I add fake model types to fill in missing gaps by copying a particular model that I think will be a reasonable addition and simply editing the [General] section of the aircraft.cfg to conform with ICAO model, type and Manufacturer etc and it works great! I've probably done this for upwards of 40-60 new types that we don't have models for. Super simple and doesn't get overwritten by a new livery scan.

It's just the log.txt in your main psxt folder.

Nope. That will not be it at all. Steam or Xbox/MS store doesn't make a difference when connecting to the MS servers. Mine is through Steam as well and I'm on the West Coast of N. America and have had ZERO issues starting and running the sim today or yesterday.

https://www.alpha-india.net/2026/05/10/oci-basepack-release/

I'm pretty sure that the conversion team at AIG have looked at everything they can on their end. It also didn't used to be this bad, Asobo reduced the lod distance to improve performance for the console users. They could fix it near instantly if pushed hard enough.

Yeah it's the same for everyone, complain to Asobo as they are the ones able to fix it.

Westjet also has a number of their own RNP approaches into various Canadian airports. The best ones being in the mountains of British Columbia very similar to around PAKT.

With what model?

The GL5T is a valid ICAO icao for the Global 5000 and 5500.

There is no GL6T icao code, it's a GLEX. If you can change it in the aircraft.cfg, then try it and see.

Looking good so far! Thanks Nico! I do notice that I have 2 787's side by side with massive wing overlap at M10 and M11. Can I adjust that in my learned file to reduce one of the sizes?

I've never seen that happen with new airports. PSXT creates a new blank airport file and starts learning it.

It depends on what you think is ok. Let it start learning right off the bat and it'll all fill in very quick being the busiest airport in the world.

Nico, I am seeing some erroneous numbers in my scan. I'm also still unsure why we need to see or want to see how many regs are in each regcode. For instance, my A400 file shows but there MANY of them that show a much higher number of regs in the files than there are in each one. 9 livery titles with 1825 regcodes, read from input/my_regcodes/A400 Atlas Military.txt But the file only has 111 regs specified. Is the scan differentiating them ONLY by a comma or is it also seeing other separators such as . , + or -?

I don't know how much of a role each entry makes or to what extent PSXT is using the ICAO type or model to process your collection just look at any of them and most are incorrect.

Have a look in the General section of the aircraft.cfgs from those IVAO aircraft. Many of them are VERY wrong and could be a reason why some aren't getting seen when scanned.

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.

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!

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.