ok...here's an issue I've had occur a few times - it's not the end of the world but I figured I'd details it here and see what you think.
Flight from KABQ - KGTR - IFR, FL210, nothing out of the ordinary. Everything was normal-normal until on decent into the arrival airfield I pulled up ATIS manually (about 40-50 miles out) ... the ATIS played as it did on departure (but with a lot of expected static given the distance). When I switched back the approach frequency I never got a sound out of PF3 again. I manually dialed up tower and tried to check in - nothing. Back to approach - nothing. No biggie - I landed and shut down like normal. Now after shutting down I exited PF3 and asked it to disconnect from MSFS - and it just sits there saying "Waiting for 'disconnect' to complete and the release of PF3 services". Even now it's still there and and I've exited MSFS completely. When I go into Windows Task Manager I see that tgs.exe (32 bit) is still running and consuming about 7-8% CPU and 1.2mb of memory. I assume that this process hung up causing the interaction issues after going to ATIS - I had to manually end the task to get PF3 to fully shut down.
Now one thing that I did on this flight that I haven't done (or even tried) previously is manually pulling up arrival ATIS - normally I do the ACARS ATIS request from center and that works just fine. I honestly didn't know that PF3 provide full arrival ATIS.
I've attached a .zip with all the log files from the Logs folder.
From what you can see, did I do something wrong or did a PF3 process just have a bad day?
Cheers, mike
PS - here's a screenshot showing the problem