vidha

I think the performance issue is that many of the AIG models have really huge texture-files and no-LOD. When at EGLL there is always a lot of ground and air traffic, simply because it's one of the busiest airspaces in the world. I use to set the parking % to a sweet spot on any given megaairport so I can have acceptable frame-rates. This sweet-spot will vary from airport to airport, and from user system to user system, so I think the option of setting the % from airport to airport in the airport-files is the best overall solution. ANd btw I prefer real traffic, so I can sacrifice some static aircraft and still keep the live ones.

Agree, but I think it's about how many users of FSPXAI vs the freeware FAIB one. Myself was using only the freeware-models for a long time, not seeing any reasons to buy the FSPXAI models. But I was wrong, after buying some of the FSPXAI-models I realized what I had been missing. They are really good looking and easy on the frames too, and a step forward from many of the freeware models I used before. I hope he will continue to make new models.

I have both the PMDG 737 and the Fenix A320, both great addons for MSFS, but still find myself loading P3D to fly the PMDG aircraft I have there with lots of payware sceneries and good AI-models. What keeps me back from using MSFS full time is the UI, which I never get used to, Also the insanely long loading times is another turnoff, especially with lot's of add-ons and AIG-models installed. MSFS camereas is another thing I don't like.

I'll take anything to save CPU and don't need the from/to the way I use it as I use FR24 to get data on flights, but maybe default it to on instead so users can disable it?

I'm aware SAS Connect is missing, I plan to add them

I'm in the same situation on my P3D setup (even though I mostly use AIG and MSFS nowadays), where I literally had thousands of manually assigned reg-codes. I found it very laborsome to edit the cfg-files, and also prone to errors. Now, you don't need AIG setup to use regcode-files, as a matter of fact I think it's so much easier to edit when everything is done in one file, or one file per airline, instead of manually editing hundreds of aircraft-cfg files. (Also, the first time regcode-files was introduced in PSXT, did it not generate a regcodefile from all your atc_id fields, to get you going?)

Yes, I see the exact same in my setup - and I think everyone do actually.

You are correct about that, but it really does not take that long to get a representative snapshot of an airport like EGLL, especially if you let the Learner program run for a few hours.

I always have the "real only" option checked, because I want only actual parked aircraft at that particular gate to show up, not the predefined ones from the AFCAD which is often way off.

I think Nico has earlier said it's not possible at the current state of MSFS to avoid stutters. I agree people have different tolerance/perception, but on my setup there is definitly lot's of stuttering of the aircraft driven by PSXT. But, it's a compromise I'm more than willing to neglect, because of the realism of having real traffic in the simulator. There are no other options coming even close to that level of immersion I think.

I had the same problem as OP, and reinstalling then uninstalling works. Very cumbersome, so MK-Studios should check their installers

I understand the compromise, but a little sad to see the crab-effect on takeoff gone. I loved watching aircraft takeoff, and crabbing against the wind once airborne.

That's a good idea, at least when we have the option to use regcode-files to master the livery assignments.

Probably because in the AIG package, they use the the icao_airline=SAS, and not icao_airline=SZS. You could solve this by using the SAS regcode-file for AIG-models.

Reading the manual section 4.1: "The lower the last digit of the parameter name, the higher its priority. If the same livery appears in two folders, the livery of the lower priority folder will be skipped." I have two folders now, one with AIGM and another with manually added textures. lfolder0 - AIGAIM_Qatar Airways Airbus A350-900 lfolder1 - UTT_Qatar Airways Airbus A350-900 Oneworld Regcode-file: UTT_Qatar Airways Airbus A350-900 Oneworld;A7-ALZ Still in the sim I get the livery AIGAIM_Qatar Airways Airbus A350-900, even if I have a regcode-file entry calling for the UTT_Qatar Airways Airbus A350-900 Oneworld;A7-ALZ. The LiveriesSkippedOnPriority.txt shows: folder 2: QTR A359 "UTT_Qatar Airways Airbus A350-900 Oneworld" <no regcode(-s)>, skipped for folder: 1 QTR A359 "AIGAIM_Qatar Airways Airbus A350-900" <no regcode(-s)> I think the regcode-file should have priority in this case and hope this can be implemented

OK, maybe I misunderstood your first post about static/live percentage on the airport. But I have found that I have to delete the snapshot-file after changing the percentage to make the changes appear, but as Nico already aknowledged there is a bug, that is probably som other issue going on here

I have also noticed that PSXT-traffic is missing from the Fenix A320 TCAS, ans it's showing up on the PMDG TCAS. Sound like Fenix also has to change their code a bit to make PSXT-traffic show up. I have also raised the concern on their Discord and hope they will prioritize to fix this. BTW all these recent releases of great in-depth aircraft for MSFS makes simming a joy these days.

Are you sure you remembered to delete your snapshot-file before restarting PSXT? If not, you might get the same ac showing from earlier sessions even if changes have been done to other parameters?

I have studied many of the default MSFS airports (including bespoke ones), and the gate/stand headings are often way off.

Well, some of the AIG packages are already several years old. Many airlines change special liveries for anniversaries and special events, and therefore only representative for maybe 1-2 year. The solution with another file with a simple list of titles of the liveries not to be used anymore should be a good solution to this I think, and will propably only be used by those users (such as myself) who really cares to have it as real as it gets 🙂

Hi again I was noticing when using the special regcode-id files that even if I do a complete fleet assignment, older and no longer in use in the real world liveries still show up in the sim both as static and live aircraft. This happens even if I have assigned the historic special livery to a standard livery in the regcode id-file. It is not so realistic when they still show up in the simulator. I guess the reason is the matching logic, and finding the particular reg-code in the fltsim-section. With manually editing, this was easy to fix. Now with the use of AIGM, manually removing or editing ftsim entries should be avoided. Is it possible to fix this somehow? A suggestion would simply be another data .txt file where you could add the titles of the AIGM-liveries you don't want to use anymore. Another approach would be to give the assignment of the regcode-file priority over the regcode entry in the fltsim-section.

With a little knowledge, it is possible to create a secondary "shadow-copy" of the AIGM OCI folder (which should never be touched itself). Then you can delete all the content, but not the models and essential .cfg files. This approach has been suggested by the developer of AIGM himself, and it does work. It can be useful if some liveries are missing because the package from AIG is not yet updated for that particular airline. I have done this myself for a couple of the MAX variants for MSFS, and it works great. If you do this on MSFS you have to be very careful about a few things: 1) file naming 2) generate JSON files for every texture in texture-folders 3) generate JSON file for the whole package (there are free tools available which does this for you) 4) for the MSFS AIG 737-max (AIA-model), it seems that you also have to flip the texture horizontally or else it will not show correctly. The easiest is of course to wait until AIG themself add the model and texture, but the above does indeed work if you are a little impatient 🙂

You could try the new function "Auto correct" for the affected airports. Sometimes the radius of the stand/gate is simply to small. The said function is great at adjusting this in the background, hence more aircraft stay parked even when they switch of the transponder.

Exactly my thoughts, as all AIGM-users should have the same names. That means it would allow for sharing this information between users per airline. I will post AAL.txt in a new thread to inspire others to follow 🙂

I have now tested the new function Auto Correct, and I just wanted to say thank you so much for adding that. It's been something I have wanted for so long, and it works great. I like to visit new airports all the time, and many of the default airports (including bespoke) has wrong radiuses. But this is no longer a problem, and it saves a ton of time not having to manually correct it.