Daniel,
After some extensive testing, Mike determined that the problem with the 0 being
recognized had to do with the default MS ATC window being opened. If you say
“BVI ATC off,” and possibly hit the grave accent key, to the left of the number
1, things should be much more pleasant. As far as reading the frequencies goes,
you can use NVDA OCR on the electronic kneeboard window, which is what is
actually displayed, or look them up on a resource like AirNav.
THere is apparently a way to get the frequencies displayed in a separate
window, independent of FSX, but I haven’t messed with this as of yet. I believe
Jordan can speak to this ability more fully.
Good luck,
Zack.
On Jan 26, 2017, at 9:28 AM, daniel wolak <danielwolak97@xxxxxxxxxxx> wrote:
Hi all,
I'm attempting to use the demo version of PF3 with FSX, and am running
into a slight snag:
I load a flight plan, and recieve an error that the first waypoint is
too close, which I hit okay on.
Only problem is that the keystroke 0 doesn't seem to do anything when I
connect to FS, and at first it seems that there is something in the way
as when I try to un-pause fsx I hear a ding, as if the window isn't
focused correctly.
Also, is there a way with nvda to see the messages that PF3 puts out
I.E. for tuning radios etc?
I'm hitting 0 after connecting, is that the thing I should do?
I also have the copilot set to mode 2...
Thanks for any help.
Daniel
X§uĐÝV+.jYrjZ·>)hķÉX§XŽķm§ĸðÃëyébēÛ(ŪåËnøĐZ-ą:)ĒËZë,jĒØ^+-ąéÝjgŽąĻķïĨĒÛįĨËlĒļĒéėđŧŪ&ÞąéÝjgŽąĻķïĨĒÛ+zŦēŨëyébēÛ(Ū§vķ°Ē·nËąĘâmč§ķŽđļÞrÚĘŦë,j
Ēš-
ęčĶØĻË.rŽv(ēÛÖĶzËëhnøĐZ-ē·Šđë-~·+-ēājwišÛa{
+vĨĶ)í
ë.n7ķōĒęæzË