OnCourse Software

Welcome to our Product Support Forums

Unintended keyboard interaction + messed up Tower altimeter readback

PLEASE NOTE:

If you are reporting an issue with PF3 please remember to Zip and attach the Debug_Monitor.log file from your PF3\Logs folder. Thank you.

Post Reply   Page 1 of 1  [ 2 posts ]
Author Message
m_j_lyons
Post subject: Unintended keyboard interaction + messed up Tower altimeter readback
Posted: Sun May 02, 2021 5:11 pm
Offline
 
Posts: 96
Joined: Fri Mar 26, 2021 5:26 pm
Location: Southern CA USA
 
Good afternoon - just completed my latest flight bouncing around the SW USA and I've taken note of 2 issues that I'd like you to confirm. Neither is a show stopper for me in any way...but I think both represent small errors in the code.

1) When getting clearance from Tower for landing I've noticed that in every flight I can recall that the altimeter read by Tower is "29" ... no decimal. Yes, I'm using US baro vs QNH. Looks like the script just isn't adding the decimal portion of the baro altimeter in the ATC message.

2) i've started using the view shortcut keys in MSFS more to rapidly jump from the standard cockpit view to the MFD displays (default CTRL1 + CTRL2) - when on with approach and jumping to view 2 (C208b center MFD) the key command is occasionally registered as "2" and the copilot asks approach for an IFR approach. It's never messed anything up (and it never finds an approach in any case even when I'm on the approach). Now this could be an issue on my end where a CTRL+2 depressed unevenly leaves the keyboard with a 2 keypress...I don't know. But if this is reported by others...maybe there's something there.

That's it - logs attached. Fly safe.

PS - oh and I get that 128.2 a lot also...I don't think i got it on this departure...but it's been a very common freq i've seen over the past few weeks.

Attachments
debug_monitor.zip
(933.63 KiB) Downloaded 74 times

_________________

Flying the friendly skies of MSFS
XBox handle: mikejenlyons
Discord: m_j_lyons
A Pilot's Life 2: Michael Lyons

-- mike


Top
Profile Quote
Dave March
Post subject: Re: Unintended keyboard interaction + messed up Tower altimeter readback
Posted: Sun May 02, 2021 5:55 pm
Site Admin
Online
 
Posts: 6095
Joined: Mon May 18, 2009 6:22 pm
Location: Sawtry, Cambridgeshire. UK
Contact: Website
 
1) Yes I've had that myself and each time I get back to me dev rig I've clean forgotten about it so thanks for reporting it here... it will now be correctly logged and I'll look into it as soon as I can

2) I've also experienced this but with Ctrl+1, which resulted in me asking for 'final at pilots discretion'. There's really nothing I can do about it unfortunately and I think it's perhaps a timing issue or finger trouble. PF3 doesn't detect keys at all, that's all handled by FSUIPC. When using additional keys with the main hotkey the FSUIPC SDK states the following:-
Quote:
Bit 3= “expect another keypress”. If this bit is set then when the Hot Key is detected FSUIPC waits
for the KEYUP or another key press first. The virtual keycode for that keypress is then
returned in Byte 3, below.
So if you unknowingly slightly release the main hotkey before hitting the second key FSUIPC will simply continue and process the first key... in your scenario the Ctrl key, which of course is not a hotkey in it's own right within PF3. I'm sure this has been the problem for me as I am now quite focused when hitting Ctrl+1 and ensure the Ctrl is held down until I've firmly hit the '1' key and then release it.

_________________

Cheers

Dave March

Email: dmarch@oncourse-software.co.uk

I don't know if my memory is getting worse as I get older...
...I just can't remember how it used to be!

[ img ]


Top
Profile Quote
Display: Sort by: Direction:
Post Reply   Page 1 of 1  [ 2 posts ]
Return to “PF3-ATC at its best”
Jump to: