SlabsFly

Thanks for looking into this Alex. I was suspecting MSFS was doing something weird and wonderful. My kludge doesn't look that great but it works so good enough for me for now. To me LNM is still the number 1 app to use with MSFS by far: a wonderful thing you have done for us simmers. Alwyn

OK, I was able to get rid of the error by replacing the aircraft type value in LNM with ATCCOM.ATC_NAME BEAVER.0.text. But that is hokey: something wrong somewhere?

Hi all It would appear I took a bad shortcut somewhere in creating a performance file for the Beaver. Now, when I load a flight with the Beaver with this performance file, LNM comes up with a message that says: User aircraft type "ATCCOM.ATC_NAME BEAVER.0.text" in simulator is not equal to type "DHC2" used in performance file. Load the matching aircraft performance file or adapt the field "Aircraft type" in the currently loaded file. I used the ICAO designation DHC2 for the aircraft type and DHC-2 Beaver for the model. Does anybody know what I should be using? Also for future: where can I find the appropriate MSFS variable value to fix it? Thanks all!

Oh wow, contrary to Alex, I REALLY am stupid: I was never aware of this! To try and make myself look less bad I will say that all my real world flying happened in rather temperate areas, so this kind of aberrant temperature was never a concern. Thanks Bob and Alex for the responses and the enlightenment. Alwyn

Thanks Alex. Just to note that I did have a few mods active when this happened: Bijan's seasons, G36 mod plus a livery. I am tied up for most of the morning but will try again without any mods just in case. Cheers Alwyn

Thanks for the quick reply Alex. Sorry about the image not showing: will try to fix. I just quickly tried the same route again from Portland OR (KPDX) to Seatac (KSEA). ATC gave me a QNH of 29.91, pressed B to set. Here you can see the barometer set correctly, altitude 6000ft Screenshot of LNM. Here you can see the elevation profile correctly says 6008ft, the tag on the aircraft says 5379ft. QNH displays correctly as 29.91 I then manually adjusted the QNH in the aircraft to try and get the altitudes to match. This is what it looked like in the PFD: And in LNM: FWIW: I checked online real ATIS also and 29.91 was the QNH given for KPDX there as well. Hope this is OK? Thanks Alex! Alwyn

Hi there First post here. Not sure if it has been like that for along time/forever, but I just recently noticed a difference in altitude displayed between the display next to the aircraft on the map and on the elevation profile. Discrepancy is marked in red. As far as I can determine, the one in the elevation profile is the INDICATED altitude and the one next to the aircraft is the ACTUAL altitude. One would have hoped that, if you have the QNH set correctly, these two would be pretty much identical. But in the example below and other instances, I have noticed quite substantial differences. I have experimented with adjusting the QNH away from the advised QNH to get the two in synch and the required adjustment is BIG. It is not just a few hPa or like 1/10" HG: it is a lot more. So I am curious: where does the ACTUAL altitude come from and why is it so very different from the indicated altitude? Thanks for a great product! I cannot use MSFS without it. Alwyn