voske

I don't believe you get license codes anymore, but you can create an API token instead. PSXT works with these tokens.

I had the same issue with PSXT in "RT Direct" mode. Switching to "RT App" and using the RealTraffic app solved that for me.

Sorry, I wasn't clear: I'm putting them in a text file for them not to be used (and I compared the LiveriesScanned.xml before and after I put the liveries that I didn't want to be used in the text file, and that worked). Now I only have generic liveries for airline ZZZ.

Perfect, thanks! And now that I think of it, I can improve my chances of getting an actual generic livery by creating a text file in "my regcodes" and putting a lot of the stub liveries in there without a registration code.

Looking through my log file, I noticed something about the matching when it comes to cargo flights where the registration is not showing. Here is part of the log file: I have liveries for these cargo aircraft. Here is a part of the LiveriesScanned.xml (sorted in the same way as the log file): What seems to be happening, is that when the registration is missing, PSXT looks for a non-cargo livery, but can't find one (because these are cargo airilines) and therefore picks a non-cargo ZZZ livery. Is there anything I can do to make it pick a cargo livery?

It's an old topic, but the problem might have returned (in version 14.5.0 it selects MA17 when parked at gate A21). Slewing solved it though.

Now that you mentioned it, I realised that I'm stil running 11.0.1. Looking through the log file, I noticed this entry: "GetDlgItem failed for ID 32853" between my parameters. Just checked it, and it's also in yesterday's log file and the day before yesterday's log file. Parameters section of today's log file:

I don't believe the distance to the TOD is the issue, but the distance to the airport: I've seen this happen with the Fenix on two STARs where the TOD is quite early (LENDY8 into KJFK and ROBUC3 into KBOS).

No issues here with the Anniversary update. Just had to register the 777 again.

The normal cruising speed of the Constellation was about 280 knots, according to what I can find. Also, the planned duration includes taxi times.

According to the legend, flights PA130 and PA131 were flown with the Lockheed Constellation and the others with the DC-4. Also, the times are local times according to page 17 and 18 of the timetable. Time in New York is GMT-5 and time in Bermuda is GMT-4. Keeping that in mind, you get the following result. Planned duration of the direct flight from New York to Bermuda DC-4: 4h05m Constellation: 3h15m Planned duration of the direct flight from Bermuda to New York DC-4: 4h35m Constellation: 3h50m

I think it's IFP/MODESASP. According to the following quote this is automatically added to the flightplan by Eurocontrol's Integrated Initial Flight Plan Processing System: Source: page 18 of https://www.eurocontrol.int/sites/default/files/article/content/documents/nm/flight-planning/icao-2012/icao-2012-fpl-2012-urd-latest.pdf

You're right according to this remark on the Lido chart: Rwy 04L: E arrivals Rwy 04R: A arrivals Rwy 12: B arrivals Rwy 22L: F arrivals Rwy 22R: C arrivals Rwy 30: D arrivals Therefore, the arrival should have been the ALM1F to ULTIS. There is also a remark on the chart though that, traffic permitting, direct routing to ABEGI, ADOVI, LAMOX, and ULTIS for rwy 22L/R may occur. If flying offline or with no ATC on VATSIM, I would probably go from ALM direct to ADOVI, and then LAMOX to intercept the ILS.

www.flightstats.com provides the departure gate (and sometimes also the arrival gate) for a lot of airports, including airports outside the US. I just tried it with flights departing from Amsterdam, Beijing and Hong Kong.