Hi Dave,
Please find attached logs a my last flight where a number of recurring issues came up again. I think I know what is going on but just not sure if its something I am doing wrong and in any case this may be more of request for enhancements rather than a bug report.
With PF3 in MSFS I have found that it does not seem to completely trap key combinations. For example months ago I found if I responded to PF3 with key combination cntrl+shift+y it would register in PF3 as it should (Affirm), but also triggered the Y key command in MSFS and put MSFS in Slew mode. Removing the keyboard Y command in MSFS resolved this issue.
I now believe I am running into a similar problem within PF3 when I find myself higher than I want to be during descent phase a flight and I request lower by entering something like “l+9” Now I get the descent clearance to requested altitude but it is it also triggering the HotKey 9 request as well so “Report Position” is triggered. Because of this requesting a lower/higher altitude is fraught with danger. Requesting lower can result in you also requesting higher because of clouds or even worse it can trigger “request cleared to final” or “Divert to Alternate airport” effectively ruining the flight.
During my last flight, PF3 stopped communicating with me after I was instructed to continue with STAR. This may have been a HotKey was triggered when I was trying to get lower quickly. It may also have been because I had to change arrival runway although PF3 did not issue me with what runway to expect and I guess it would be nice to begiven arrival runway when passed onto approach.
Now to the changes which to a large extent resolve these issues. Despite the problems I am having I much prefer the HotKey window way communicating with PF3 in MSFS rather than the Context sensitive commands I would just like the HotKeys available in the windows to be a bit more context sensitive.
For example during taxi from stand to departure runway having HotKey to request another runway rather than having to press a HotKey to turn off TGS and then Cntrl+Shift+W to request different runway.
During cruise there are 4 HotKeys concerning altitude. Request Higher/Lower because of clouds and Request Higher/Lower because of turbulence. Why not just have 2 HotKeys Request Lower & Request Higher. I have found using the currently available HotKeys related to altitude frequently result in an Unable response from PF3 whereas using l+n is pretty much always granted.
Another suggestion I would like to make would be for a neater way of telling PF3 you want vectors to final. Currently you have to go into the Airport page and enter a STAR possibly for several runways and then make sure the use STAR check box on the SID/STAR page is unchecked. Why not have another checkbox to tell PF3 you want vectors to final. Or even better would be to be able use the request vectors hotkey when tuned to approach as a way of telling PF3 to vector you to finals
I look forward to hearing your views on this or if the log files show up anything
Thanks in advance