OnCourse Software

I notice when I am cruising at a Flight Level (altimeter setting 29.92) above transition level VCP will callout the altitude FL315 vs real altitude of FL310. I fly with Little Nav Map active and the aircraft is showing the correct FL (FL310 in this case) and the AI generated aircraft altitudes are also correct. I'm not sure where the inaccuracy is coming from. PF3 or MSFS2020

I'm using ver 3.21.0

Please see the red message at the top of this forum and include a log file.

Thank you

I've been having the same issue for a while now.

Attached is the log file from my latest flight, EGBB to LSGG at FL290. I use REX's Weather Force for my live weather.

On another issue, is it possible to make the same change to the trigger for altitude changes when descending to smooth out the descent in the same way as you did for the ascent?

Thanks

Thanks for the log. According to what I see your VCP was correct. The following call for instance:

London Control Speedbird 1904 Level at Flight Level 285

You were actually flying at FL287

The altitude is read from FSUIPC which of course grabs it from MSFS. However, there's a dim and distant bell ringing about this issue. I know we had something similar when 3.15.0 was released and that was fixed and the fix is still there in the latest version. I've done some more checking on the FSUIPC support forum and there's a possibility there may be another offset we could use to alleviate this problem, although I'm very surprised no one else has reported it, which makes me dubious as to whether this change will work.

Anyway, attached is an interim version of PF3 for you to try, if you wouldn't mind.

Make a copy of your current PF3.exe so you can revert back if necessary.

Extract the attached into your main PF3 folder.

Open the PF3.INI file with Notepad, or some similar editor.

Under the [Config] section add the following line

TestNewAltitude=1

That's it. Then give it a try and please report back and include your debug log

Warning: I have NOT been able to test this as my MSFS is currently grounded, due to some abysmal internet speed problems... one of the things about living in the back-of-beyond unfortunately. So I would suggest not trying this if you're about to make an important flight.

Thanks for this response. I'll give the fix a try and let you know how I get on.

It's odd that both the aircraft (CJ4) altimeter and Little NavMap were showing the plane at FL290. Not sure how MSFS & FSUIPC have something different.

Cheers,
Bob

bobwad wrote: *

Sun Oct 08, 2023 6:21 pm

Thanks for this response. I'll give the fix a try and let you know how I get on.

It's odd that both the aircraft (CJ4) altimeter and Little NavMap were showing the plane at FL290. Not sure how MSFS & FSUIPC have something different.

Cheers,
Bob

Hopefully they are both using the same data that I want you to try... FSUIPC lists it as Indicated Altitude Calibrated (Indicated Altitude with the altimeter calibrated to current sea level pressure. In feet)

Just completed a flight from LSGG to EGPF at FL300, with your interim version of PF3. All VCP altitude callouts now matching both the altimeter and Little NavMap readings.

I've attached the log file for your information.

Thanks very much for resolving this.

Cheers,
Bob

Excellent news. Thanks for your help. I'll add it to the next beta release and probably make it an option so you won't need to mess with the ini file