Hi,
I’ve searched and seen that this issue has been reported a couple of times during the past years, but I’m experiencing it with the latest version of Charts Desktop (8.38). After some time of use the map just disappears and I haven’t found a way to get it back other than just restarting the Charts Desktop app.
When the blanking (map disappearing) happens everything else is still working like the aircraft position icon, but nothing is otherwise shown in the canvas. It doesn’t matter if I use the app on another computer or on the same computer as MSFS 2024.
How to debug this further?
Hello! Welcome back to our forum!
Thank you for the feedback! As of writing this, the latest version of the Charts desktop app is 8.38.1 - not 8.38. Please confirm that you are using the latest version!
I have added some additional logging to your account in order to look into this further. Please try again and let me know when you see this issue again! Also include screenshots if possible.
Also, please send us the logs from the Navigraph Charts app by following these steps:
- Press Win + R
- Type
%appdata%/Navigraph Charts/logs and press enter
- In the Explorer window that opens, locate the
main.log file
- Upload this file to your next post
Kind Regards,
Malte
Hi Malte,
Thanks!
The version was my bad. I’ve been running 8.38.1 indeed. I’m starting to fly again. After the issue surfaces I will send you the exact time and log, and a screen shot.
Alright, didn’t have to fly for a long time. It happened again at 17:48 UTC (19:48 local).
Please find attached a screenshot and the main.log.
main.log (93.8 KB)
Thank you for the log and screenshot! I do not recognize this issue. We shall investigate, I’ll get back to you!
Thanks. And please don’t hesitate to ask if you need more info or want me to try something out.
One more point to add, maybe relevant, maybe not. I have used the Chart App on two different machines (the other one is remote, the other is the same as where MSFS 2024 is running). I see the issue on both (but I haven’t had the App open on both at the same time so don’t know if it would happen simultaneously).
Both machines are running on Windows 11, but the other is a regular PC (RTX 3080Ti) and the other is a laptop (some Intel integrated GPU).
Thank you for the additional information! That should not matter, but all details are welcome.
When you get this issue, can you try zooming out? Is it possible that it is showing your position somewhere out at sea?
You can see the current map scale in the bottom right corner of the map.
Kind Regards,
Malte
Started flying again, and it took about 10 minutes for the Charts to go “blue”. I zoomed out gradually to the max zoom out (= 1000 km) and I see nothing than the blue.
When the “blue” thing happens I can see that the map flashes one time before it changes to blue.
I tried each and every option everywhere in the charts and the only ones that have any effect are the chart layers. If I turn them off and back on one by one I can see stuff as in the pictures, but the actual map is gone. No VFR, IFR, satellite or any map comes back unless I restart Charts.
Thanks for the update! That is very odd.
We cannot reproduce this, and there is nothing in your logs that could hint at the issue. Unfortunately, this makes troubleshooting very hard for us.
Have you tried the usual things, like:
- Reinstalling the application
- Testing the browser version (charts.navigraph.com) to see if the same thing occurs
- Testing a different internet connection
- Disabling firewalls/antivirus
- Updating GPU drivers
Hi,
As I have stated I have tried the Charts from two different computers. The other one has a fresh installation of Charts (from about a week ago) and the other one has had a Charts app that has been updated on the way since 2020 or something.
Both PCs have a completely different GPU, the other one RTX 3080Ti and the other has an Intel integrated GPU. Internet connection has been tested with the other PC being in a mobile connection with a completely different subscriber. Different firewall/antiviruses on both. The only common nominator on these machines is Windows 11.
I can try the browser version for sure.
One other common nominator is that I use 4K resolution on both machines.
Thank you for the additional details! And for the ones that I missed too, sorry about that.
Let me know how the browser works for you, or if the issue remains the same!
With the browser version so far so good. I’ll try again sometime today since there’s a new SU2 beta version now available of MSFS 2024. Will keep you posted. In any case the browser version is a good workaround for now.
1 Like
Additional info: There’s no problem as long as I don’t open any of the charts (open or overlay). After I have done that it takes just a few minutes and the map blanks out. This is extremely weird given that it behaves the same on two different PC with completely different HW and also with two different connections (one fixed, one mobile).
I guess there’s no logical reason for this? The map shouldn’t go blank if there’s a SimConnect (or SimLink) issue? Or a brief disconnection between the simulator data and Charts app?
There is no logical reason for this, no. You have the first and so far only case of this issue and we are not able to reproduce the issue.
The team will investigate further as soon as we have resources to do so, we’ll let you know if we find anything!
I am now having this issue. I have been using Navigraph with MSFS for over 1yr and never had this issue until now. Not sure how this is a resource issue. I have an i9-13900 with 64GB and a 4090. This happens even on the desktop app without the sim running. example from desktop image.
1 Like
Hello!
I moved your post here because it was not relevant in the context in which it was initially posted. However, it does seem to match the description of the issue in this topic!
As mentioned in my previous post here, we cannot reproduce this. We shall try to keep digging as soon as we have the resources!
Kind Regards,
Malte
My charts also go blank when i try to make changes, i.e. add a departure change.
main.log (294.3 KB)
