OnCourse Software

Hi all! I have been running into a couple of issues on the last few flights. It started 3 flights ago and has happened on each flight since.


1. My taxi out instructions are very confusing. For example on this last flight, I had to taxi from gate D11 to runway 4. The taxi instructions given were to taxi using A, N, A, M, A, L, A, K, A, J, A, H, A, G, A, F, A, E, B, D, B, C, B. When I get to the assigned runway I have to call the tower to get clearance to takeoff as it no longer seems to detect that I have reached the runway.

2. When landing at my destination PF3 stops giving me instructions. I tried tunning to ground but nothing happens when I attempt to contact them.

3. When trying to shut down PF3 after a flight the message "Waiting for 'disconnect' to complete and the release of PF3 services" does not go away and I have to close PF3 manually by clicking the 'X' in the upper right.


For my part, I have checked to make sure MakeRwys is the latest version and run it again. When that did not work I followed the PF3 manuals directions to delete the csv files F5, G5, R5, T5, and Runways then running Makerwys again. That did not seem to have any effect. I don't suppose I could trouble someone for help with this?

Thanks in advance,
Ed

Hi Ed,

1. We are currently addressing the verbose taxi instruction literally as I write and the fix will hopefully be out soon, once we've concluded some more testing.

2. We would have to see the debug log to ascertain what the problem is here

3. That 'can' happen if you decide to close/disconnect shortly after leaving the runway, as PF3 is looping to check when the runway has been vacated. If you keep moving away from the runway the disconnect should complete. This is also something I've addressed in the next release to ensure PF3 is much better at determining when the runway has been vacated

Hi Dave,

The problem of no communication that I mentioned in bullet #2 in my first post happened with my last two flights. Here is the debug log from that flight.

Edit: Here it is attached now. I had to compress.

You disconnected PF3 from FS when you were 10 miles from KIAH !!

What do you think could be causing that to happen? I have my VR headset on and do not click the button to disconnect until after I have taken it off. I don't take it off until after I have parked at the gate and shut down the plane. I always start cold and dark and finish cold and dark. Also, PF3 is always showing it is still connected. This is what has happened on every flight for the last 4 or 5 flights. I will upload the Debug_Monitor.log from my next flight today. At any rate, I promise that I am not shutting down PF3 until after I have exited VR and I do not exit VR until after I have parked at the gate and shut down the plane.

I've no idea why it should be happening then... but it is. PF3 isn't doing it, that I am sure of. The 'disconnect' button is most certainly being clicked AND the confirmation 'Are you sure you want to disconnect' prompt is also being clicked

Is there a time stamp of when it happened? My PiRep which is based on the Zulu time that I set inside the sim has me landing at 04:15:13. Unfortunately I do not know what that translates into for actual world time. I do not fly real time, I set the time in sim to match the scheduled time of the flight.

Edit: Could FSUIPC have anything to do with this? It was still running when I closed down MSFS though.

Sure, here's the time stamp from the log... it happened immediately after you change to the Tower frequency

Code: Select all 11/5/2022 11:18:28 PM: 110 - Send CLOSE to WX... 11/5/2022 11:18:43 PM: 270 - Connection OFF! #3

That's interesting. I didn't shutdown for about another 15 minutes. It was a bit of a taxi as GSX follow me veered off into the grass and didn't catch up when I went past it. I had to call for another follow me vehicle. GSX has really been annoying more than helpful.