Dave_YVR

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.

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.

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".

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

What I see that is strange is that the log only shows one aircraft in each of those parking spots. Are you certain that your Parked aircraft is disabled in the Sim's settings?

Sort of yes but as the Orbx folders need to stay in a particular order to each other it's meant to maintain that order as well as for in with the users library. If I recall correctly you want the first option (FTX Regions and Airports or something close to that) set to insert just above Bathymetry. The other one stays set to below the FTX Regions and airports. Also if you have FTX England or other regions, they all come with airport ade's aka afcads and technically they will conflict with other airports so you should remove or disable any conflicts. For instance again, you might see 3 files named starting with something like FTX_ENG_EGCC, those will conflict with addon scenery regardless how high above it is in your library order.

It has been years since I used P3d, but did you set your insertion points in ORBX Central? It was vital to do it properly yet most didn't do it at all and ORBX got a bit of a bad rap because of their failure to do so.

Thats pretty much what I was getting at. IF the airport file had the new gates we'd see traffic parking there in real time regardless of if it has been fast learned by Nico or not.

It's 100% because it's using the AI engine of the sim which has no idea what it's supposed to be doing. I just installed it to have a look and I'm only seeing 959 liveries, that is a tiny fraction of what FSLTL includes which is itself a tiny fraction of AIG offers, both of which everyone knows are free. Lighter on the system ONLY because it includes so little!

Fwiw, the AI models and liveries/paints in 2020 and 2024 are the same.

No, it indexes them and only loads when needed.