Dave_YVR

No not at all. It is very common at the smaller slower Canadian airports. "Cleared to the Sydney Airport for an approach" would mean that you as the pilot can conduct ANY published IFR approach.

I would imagine IRL there that you would probably just get "cleared to the Sydney Airport for an approach".

I believe FSDT installer is the correct way, but it tough to tell these days.

They don't care?? Do you have ANY idea on how much work gets put into each livery let alone the flight planning, programming, the costs of hosting the many gigabytes of data etc? All done on their own time and $ for everyone to use for FREE. It's that the files are hosted on a site that they have ZERO access to and that they don't have permission to host the files elsewhere. It's pretty simple. Mole hill more than anything.

4 engines for reduced performance! Can't wait.

FSLTL mostly uses 4k textures which will definitely chew more into your fps than using AIG models and liveries for instance. You can also just reduce your percentage at busier airports to minimize the impact.

The 747 models were all updated a few months ago. The new ones are the AIG 787's.

Fake liveries on fake aircraft types operating to/from unrealistic destinations? Better than default maybe I suppose, but why pay for something so substandard when FSLTL is just as easy to install and free when you want proper simple traffic. ST shouldn't even be in the same category.

When was the last time you ran AI Manager? I say that only because if it has been a while, there may be model updates as well as numerous livery updates etc.

While I have used DDU when changing between AMD and Nvidia graphics cards, I have never seen a need to use it for driver updates or even swapping between Nvidia cards.

The only model that FSLTL adds that isn't included with AIG is the MD11.

FSLTL is easy and simple to install but AIG will bring more a lot models and about 8-10x the liveries. Performance wise is the same for the most part as it's more relative to how many aircraft you are getting at any particular session. That being said, AIG will generally inject ALOT more aircraft especially as the injection ring in MSFS is much larger than it was in P3d so every user should adjust their traffic % based on their system capabilities. As for the install process for AIG, some find it easy albeit a very long process and others find it more difficult. Like many things in life, you go the simple route, you get the simple results or put more work into it and get the better product. Similar to learning the default MSFS A320, there's nothing wrong with it, but when you invest the time to learn the Fenix A320 you get a better overall experience.

Like every other version of P3d, with BGL based ai traffic you need to let it run for about 20-30 mins for the AI to settle down. Stick with AIG if you already have it installed, it has by far the most models and liveries (8-10x). Also keep in mind that the number of parked aircraft on the ground comes down to how much proper parking is available at every airport in the sim.

Keep in mind as well that most airports worldwide even many of the larger ones don't use transponder on the ground ops or that those feeds aren't available to the public. Then there are also those smaller airports that don't have radar or any surveillance to the ground.

Ok, so then is PSXT changing the codes that I had used which are correct to the old ones which are no longer current? How much difference does it make and what weight does it hold over using the correct reg from the atc_id=? When I look through my AirlineTypeConversions I find many of the aircraft listed are correct and shouldn't be adjusted at all.

Hi Nico, Looking in my liveriesScanned file, I am noticing operator codes for many bizjets that don't match to what I have them set to in the aircraft.cfg. Which one does PSX use when there is a mismatch? The ones that come to mind mostly are from what used to be XOJ as well as EDG and are now operating as VJA . Another large fleet of them would be AHO which should now use VJH.

It does that when the insertion point isn't set properly, basically reverting to what you told it to do.

That's just it, "can then be placed" means you move and manage them yourself which as we've seen SO MANY times in these forums over the years is that many people don't know how or think they know better and make a mess of it tending to blame ORBX or the scenery dev. You clearly have a very good understanding of it and how it all needs to be setup. If you leave the ORBX regions and airports and the default placement without properly adjusting layers afterwards, it's asking for trouble. By placing it at the recommended placement by ORBX, the chance of errors and issues is much less without user interference. They can still get into trouble for sure, but it's harder to do.

ORBX has always recommended that their FTX Airports and regions be placed way down below ANY of your non ORBX your addon sceneries as they include Mesh, and Landclass etc. I know you mention that you further customize your layers from there, but the OP did not which could lead to further confusion.

Check that your ORBX Library insertion points are set correctly. Most people don't set them at all which causes serious issues. Airports and Regions goes way down below Randolph_AFB and leave the Orbx Global open LC set below Orbx Airports and regions.

That is the current release version.

That's just one of the reasons that I can't get away from PSXT. Even with it's quirks and faults, it's still that much better.

Thankfully with Steam you get to specify where your MSFS install goes so it doesn't get buried by the default location that the MS Store uses.

I got back in to riding in 2018 after a 20+ year break to raise my son. Currently on a Ducati Supersport 950. Comfy enough for a spirited all day ride but without the insane HP of a V4 Panigale (granted I would really love to have one).

Fair enough, where I work it is the tow vehicle that has the transponder on as that is who ATC is talking to. PSXT at YVR also seems to get very mixed up with the various tows. Tow 913 in the example below wouldn't tow any ACA aircraft, just JZA. The SWA I just can't explain at all as they don't operate to YVR but the airport file has many instances. <opt airl="ACA" type="B38M" day="7" hh="39" reg="C-GEHV" cs="TOW 913" /> <opt airl="ACA" type="B789" day="7" hh="39" reg="C-FGEI" cs="TOW 913" /> <opt airl="ACA" type="A333" day="7" hh="39" reg="C-GFAH" cs="TOW 913" /> <opt airl="SWA" type="B38M" day="7" hh="44" reg="N8710M" cs="TOW 914" />