OnCourse Software

I guess I didn't leave the SIM and PF3 alone as long as I thought. I tried KATL again and, this time, waiting for about 15 minutes. I finally received the following route to runway 27:

Please let me see the debug log for that flight... if you've done another flight since then I'll need the OLD debug log... or just include them both to be sure

gilyoder wrote: *

Sun Sep 26, 2021 2:23 pm

I guess I didn't leave the SIM and PF3 alone as long as I thought. I tried KATL again and, this time, waiting for about 15 minutes. I finally received the following route to runway 27:

The fact you only received a 'to taxiway' response means PF3 couldn't find a connected route for some reason, which is why it took so long searching. It certainly seems like there must be an issue with the MSFS KATL AFCAD... but I 'may' know more once I've seen the debug logs

Here are my log files. I hope you see something in them.

Thanks again.

Unable to replicate it here yet... using your exact coordinates for the taxi route call... but I have a few other things to try tomorrow.

Incidentally, it didn't take 15 minutes... only 5... Long enough though!

9/26/2021 6:34:20 AM: 260 - Transcript: 'Ground November Sierra 785 Ready to taxi. '
9/26/2021 6:34:26 AM: 580 - #1 Start: 6:34:26 AM
9/26/2021 6:34:26 AM: 580 - Get Taxi instructions #1 for Runway 27 Right
9/26/2021 6:34:26 AM: 580 - Call Route:
9/26/2021 6:39:27 AM: 450 - Route Found:
9/26/2021 6:39:27 AM: 460 - Checking Taxiway Names...
9/26/2021 6:39:27 AM: 460 - Taxiway Name checks complete...
9/26/2021 6:39:27 AM: 690 - #1 End: 6:39:27 AM
9/26/2021 6:39:27 AM: 700 - Transcript: ' November Sierra 785 taxi to runway and hold runway 27 Right using taxiway

dmarch wrote: *

Sun Sep 26, 2021 8:07 pm

Incidentally, it didn't take 15 minutes... only 5... Long enough though!

Wow! My timer must be off.

I wonder, though, could it be logging the response and then delaying the actual response? I'm going to put a stopwatch on it to be sure of what I'm seeing.

Gil

Hi Gil,

Please find attached an interim version of PF3 for you to try... version 3.12.15

This doesn't 'fix' the issue you're experiencing, it just gives some feedback from ATC, telling you to expect your taxi instructions shortly. At least then you'll know PF3 hasn't given up!

We're only able to do this by using an external thread to calculate the taxi instructions. This was something I was going to implement some time ago but a few of the beta testers were experiencing some issues with it so I shelved it for now. However, I've been running it here all day and it's proved to be working just fine. Incidentally, I get a 5 minute delay in receiving taxi instructions at KATL every time.

I would suggest you make a copy of your current PF3.exe file then drop the attached into your main PF3 folder.

Next you need to open the PF3.INI file with Notepad (or similar) and search for the entry UsePF3Thread=0 and change it to UsePF3Thread=1. Obviously if you did experience any untoward problems just change it back to UsePF3Thread=0 to deactivate the external threading.

Now you can try PF3 at KATL again.

Finally, if this works better for you and you continue using it please bear in mind it will not detect a new version of PF3 when one becomes available. You will need to keep an eye out on this forum so you know when the next release is available. At that time I would suggest you simply download and install the latest cumulative updates package to ensure you are fully up top date.

Definitely better. Thanks!