iamgbs

I'm sure you can handle it Alex! The airport diagrams look fine on the ones I have used and aircraft is located where one would expect it to be!

johnbla: I didn't do anything different! I activated LNM, then MSFS, then once the aircraft was at an airport it showed up on LNM. I also used it for the training sessions from Sedona, and the plane showed up there as well. Together with alt, spd, hdg etc as I had it set for P3D. Good luck, may the sim gods be with you. Vindeballe: Thanks for that info. I will check it out.

Johnbla - I did exactly that, and it works great! Also includes all AI airport traffic!

That's great Alex, I look forward to being able to use LNM with it! MFS2020 got "disconnected" again from Internet (again- a pain in the tail section), so when I calm down and sign back in tomorrow, I will try if LNM will connect with it.

Any chance this fantastic utility is planned for update to handle MS2020?

I posted on PMDG Forum as advised by Pete above. They have responded and the problem is fixed (essentially: disable EF Logging and Debug, ensure your shaders are OK, ALWAYS have the F22 default aircraft on screen before you select NGX). I suggest anyone else visiting this forum for the answer to the problem go to PMDG Forum instead and read the full thread.

Thanks. I will post there today.

Hi Pete, Yup, cycled the EF log ON/OFF several times. Also tried it without EF at all - same problem. Even went so far as to revert to original P3D shaders, but still nogo. I think EF is not the cause, but merely a symptom of something which has been there apparently from PDv3 (which started this thread). This is driving me nuts! Expensive plane, really love it, can't use it. PMDG - are you there...???? Or is there another forum I should be posting on?

Yup, several years old yet still relevant! Update: After jubilantly announcing yesterday that switching OFF EF Auto-logging worked for me: That was yesterday! Today, the problem is back!!!!! I tried all the steps from Darryl as well, but no change. Can this annoying problem be finally fixed? I look forward to feedback from PMDG.

Pete, disabling EF Auto Log did it for me. Did it work for you Darryl?

This is happening to me for P3Dv4.5. I hadn't used the NGX for a while, Wanted to yesterday, black screen exactly as described by Rimax. Reloaded NGX, but problem remains. All drivers and software up to date. Does not happen with any other aircraft. Any ideas???

Thank you Alex. I did as suggested and I see them now! Great product, mate, best on on the market! 👍

Long time user of Little Navmap, and still loving it! Interesting problem turned up on 2.2.4: I have latest Navigraph - 1905, installed on everything I have (as far as possible). However, I note that some Navaids (like STARS) shown in my aircraft are not found on LNM using User Search. An example; Flying into WARJ, I wanted to use a Procedure which was on my FMS (IFly 747) for an ILS approach to RWY 09. It was not on LNM screen ("No Procedures for WARJ"), LNM showed RWY 09R with ILS Feather, but no procedures. So, I searched for the following STARS shown on FMS: ANY1A, GEPA1C, LASE1F. But the search showed no result. I have noticed this at a number of airports since I updated to AIRAC 1904/5 and LNM2.2.4. I can't figure out why. Can anyone shed a bit of light on this please?

Thank you cmpbellsjc for pointing me to the correct forum. However, I found out what I was doing wrong: What I was doing was then pressing the "Run" which prevented the clock from counting. Strange, but true. I guess "Run" meant it was running, NOT that I needed to press "Run" for it to start!

Hi, I cannot seem to get the ET part of the clock in my PMDG 737NGX to work. When I press the ET button (lower right), the display shows a 4-digit digital display (as one would expect), with "RUN" displayed above the ET Button. But, the display does not count, just sits at 00:00 forever. Not a show-stopper, but would be nice if I could get it to work. Apologies if I missed a post about this, but could not find any posts through a search here and in Google which fixes it for me. Perhaps I have a corrupt file?