AeroMaster12

Thank you both, @Dave_YVR and @kiek for helping with this! Totally understand not having time for updating data and will happily report and do some data adjusting from my end. Dave - I'll check with you first if I notice any livery issues next time, if you're OK with that? 🙂

The Skywest ones are wrong or way out of date though which is why I'm trying to override these over AIG's; since it's encrypted, I can't cross-check or fix it 😕 Couple of examples of incorrect registries reported from log vs. their actual registration. Bolded registrations are ones I attempted an override referenced in the OP which isn't being honored. Mainly is only happening to Skywest's E75L liveries Actual: SKW3322 N410SY PSC->SEA SKW E75L =2= AIGAIM_United Express Embraer EMB-175 New WL - opb Skywest Airlines OC Expected: SkyWest Airlines N410SY (Embraer 170/175 - MSN 904) | Airfleets aviation Actual: SKW3736 N327SY SJC->SEA SKW E75L =2= AIGAIM_American Eagle Embraer EMB-175 New WL - opb Skywest Airlines Expected: N327SY Delta Connection Embraer ERJ-175 Actual: SKW3414 N407SY BLI->SEA SKW E75L =2= AIGAIM_American Eagle Embraer EMB-175 New WL - opb Skywest Airlines Expected: N407SY Alaska Airlines Embraer ERJ-175 Actual: SKW3186* N179SY SKW E75L =2= AIGAIM_American Eagle Embraer EMB-175 New WL - opb Skywest Airlines Expected: N179SY Alaska Airlines Embraer ERJ-175

For anyone else having a CTD at KSEA or other Pacific Northwest airports, keep your eyes on these threads - looks like an issue with the latest Navigraph nav data cycle. Workaround for now is to disable Navigraph for the time being until they can identify the root cause of the CTDs and roll out a fix Selecting KSEA causes CTD (2501.1) - Navigation Data / General MSFS Data - Navigraph 2501 rev.1 CTD's at default KSFB - Navigation Data / General MSFS Data - Navigraph

Hi Nico, Just reporting a minor file hygiene bug that I believe this started with 10.1.0 - on startup, when PSXT looks at airports for offline learning, it identifies some stock airports where they are not suitable for offline learning. In this process, it generates empty XML files, one for each airport, however it doesn't seem to clean it up afterwards when hitting this condition only. Here's what my directory listing looks like after PSXT starts:

A couple of drawbacks and concerns on losing the local archived airports: Unable to verify if a parking spot exists (depending on AFCAD, gates are numbered differently than what's published on Navigraph or other sources). We have to guess and test parking spot IDs if we want to reserve a parking spot at the destination airport in advance Unable to make adjustments or local changes to XML files to suit parking preferences (+1 to @vonSzuli) Now dependent on internet connection for statics traffic with no fallback in the event of a server or local internet outage For those who have a standard RT subscription, the price to upgrade to professional is prorated at the monthly cost. This is expensive for those who just started a new subscription and pre-paid for a full year of data. What was once available to all users is now being paywalled by a premium tier subscription is concerning. While PSXT's mechanism was built to help traffic history files using RealTraffic data, it opens the question of who is the custodian the data - PSXT or RealTraffic? If PSXT is storing and maintaining parking data, I feel that this shouldn't be paywalled.

Just as a sanity check, when you added the AIG package into your Community folder, did you also have PSXT rescan all of your aircraft liveries? If you had loaded PSXT once where it ran a model scan, but then added AIG models after that, PSXT wouldn't have picked it up

Hi Nico - I was wondering if you are aware of a static parking collision detection bug where aircraft that are too close together are not removed in cases where parked planes are intersecting each other. In cases where there are gates that can handle multiple medium aircraft or a single aircraft, when PSXT spawns two medium planes next to each other, they will intersect when only one should be present. Here's an example at BIKF, where the gates in the AFCAD are g77 and R77 (representing apron spots 77 and 77R) PS: I'm no longer seeing the live stacked planes issue that was brought up earlier. Thank you for all of your efforts on that and improving PSXT as a whole.

I can't pinpoint whether this happened on an update or if it loaded just like this, but there was a case where a Hawaiian airlines plane and American Airlines plane were stacked together. Here are the logs (notice that C3 shows both planes spawned)

I see the same. I think it happens around when there's an update to the parking positions; old ones sometimes aren't getting removed

+1 to this - it's a great way to balance the new solution while still allowing for the old solution to select a destination airport and reserve a gate. Thanks again! So far running great on my end

In my case, I never got an email, but since I already had the Xbox Insider app, I just checked that. Sure enough, it was listed there!

Remembering the departure airport isn't too big of an issue, and actually helps prevent aircraft from spawning at the departure gate in the cases that I did a pushback just before PSXT updated aircraft. Most of the time however, if I were to return to that same airport, I also won't necessarily be parking back at that same gate, so I'd still have to edit the file to change the gate assignment. Thanks for the push button to reload the file! That makes easier

It's been a while since I've flown in MSFS so I'm slowly catching up to the latest updates and releases. Something I thought of as part of the abandonment of destination airport parking fields: When the destination airport feature fields were available, I would typically choose the destination and a specific parking gate where I would want to finish the simulation in (consider cases where an airline only has one assigned gate at an airport that serves as a hub for other airlines). I would set the destination gate to prevent an AI generated aircraft from spawning in that particular spot. With the removal of the DestinationAirport fields, a couple of things got "harder subjectively: We now have to manually open my_park_airports.txt and add the ICAO and gate that we would want to arrive at When adding the parking spot, we now need to look into the corresponding XML file to make sure the parking spot is valid Once the file is edited, a restart of PSXT is required Wondering if it would be possible to restore the interface that would at least take help automate 1 and 2. Having an automated validation of the parking spot was super useful before. Looking forward to trying out the new features nevertheless!

I personally use this from Flightsim.to, because the camera angles that the creator implemented are consistent with every aircraft that I fly. If you download this and follow the installation instructions precisely, you'll have camera angles for what you're probably looking for. Custom views for almost every airplane - A2A, ATR, Fenix, PMDG, JF, SWS, A32NX, MD82, HPG, Aerosoft for Microsoft Flight Simulator | MSFS

Will do separately, thank you! I notice the following airports in my archive folder that have a RT_traffic_week < 30. I don't have any of these airports except for HECA so I can't send you those.