OnCourse Software

Absolutely not - Dave uploaded it earlier today, so please give it a spin.

Martin

I spotted this problem late yesterday afternoon and confirmed the fix late evening - hopefully Dave will upload 3.22.18 (or later) soon.
It was down to a change I made in the taxi routing code that didn't get transferred cleanly into the main PF3 build - sorry

Martin

Is this the screen that you saw? 2024-04-26 08_03_53-PF3 Core Updates.png We've added a new feature to the PF3 Updater which allows us (Dave) to send out minor updates to core PF3 components without a new release. In this case, it was an update to PF3 Displayer to fix a connection problem with the 3...

Web Display can be used from a browser on the same PC as PF3 with a single monitor (but you would need to switch windows between FS and the browser), on a second monitor on the same PC or from a browser on another PC or other device, such as a mobile or tablet - it is very flexible. It can also be a...

Alternatively you may wish to take a look at Web Display, which will give you what you need in a browser window. You can arrange for it to be autostarted by PF3 in Options#2, Advanced Options: 2024-04-13 18_25_53-Advanced Options and INI File Tweaks.png Then you simply open 'localhost:7339' in your ...

PF3 is a complete substitute for the MSFS default ATC, so you need to switch off the MSFS ATC assist completely, otherwise it will interfere with PF3. You can find the place to do this under 'Assistance Options' in MSFS: 2024-04-13 17_25_47-Microsoft Flight Simulator - 1.36.2.0.png I'm pretty sure t...

You may want to try changing the following option in your PF3.ini file: Change CalibratedAltitude=1 to CalibratedAltitude=0 Dave spent many hours looking at altitude mismatches in MSFS prior to releasing 3.22.0, and there were a number of internal changes to PF3; it looks as if he removed the option...

We're not ignoring you
Dave will need to take a look at this when he's back online.

Martin

This isn't the recent FSUIPC issue, it's caused by a PF3 configuration option. Looking at your log the hotkey was being accepted, and you should have seen a message from PF3: 11/04/2024 14:24:28: 160 - ****** HotKey #0 detected! 11/04/2024 14:24:29: 180 - FS Screen : Please tune to ATIS on 130.87 be...

Hi John, This log is indeed for a flight from KSLC to KTUS, but it may not be the one you wanted to show us - you never leave KSLC. Anyway, I can see in this log that you pressed Ctrl/Shift/R while at KSLC to request a change of runway and received an initial response: 09/04/2024 07:07:51: 590 - ***...