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.