I have found in my new MSFS2024 that when I have to do a VFR flight, generally loaded with points created by me in LittleNavMap or by the creator of a tour that sends us a route along a river, for example , the Garmin does not recognize these points and therefore the flight plan is worthless and it is not possible the use of the A.P. .....  and in fact if there are only those types of points, the flight plan only has departure and arrival.

After creating the flight plan in LNM, I use the Multiexport Flight Plan Options / Category: Simulator / Microsoft FlightSimulator 2020 option.

 

Is there any other way to export the flight plan so that the Garmin recognizes all the points in it?

 

Thank you very much.

J J Gómez

Can you post a flight plan example (https://www.avsim.com/forums/topic/605519-how-to-post-a-screenshot-or-files)?

There was an issue with custom waypoints in the past, but as far as I know this has been fixed already.

This is probably also affected by the flight plan type. Do not use IFR but export it as a VFR plan.

Alex

 

Here you are 2 images ... the first one is part of the FP in LNM with 2 of the points of it  ( BOROG and IMSUT ) with a user WP1 created by me between them.

.... in the second one you can see how it has been received by MSFS2024 Garmin 1000 without the WP1.

 

Please tell me if you need another thing

Thabks

J J Gómez 

Thanks. Will check tomorrow but to me this looks like the typical MSFS issue.
If the flight plan shows ok on the opening screen its often the avionics.

Alex

Your screenshot shows a MSFS 2020 database using a Navigraph navdata update (not the latest) in LNM.

MSFS 2024 without navdata update does not have the waypoint ASNED. So I suppose something is wrong with your configuration and you see warnings about using the wrong scenery library from '20 when connecting to MSFS 2024. 

First switch to a MSFS 2024 database and reload the scenery library just to be sure. This might be one reason for breaking plans.

Loading the plan into a MSFS 2024 without Navigraph update here simply drops ASNED as expected. WP1 is added as FPL000. I tested with the stock DA-62. All working as expected.

Alex

Indeed, I was having configuration issues with MSFS2020 instead of MSFS2024 and with the Navigraph Navdata update.

I've already corrected both issues, as you can see from the first screenshot, which shows the ASNED point replaced by the KASAB point.

Next, I exported the flight plan, as you can see in the second screenshot.

However, as you can see in the third screenshot, WP1 appears correctly in the EFB between the BOROG and IMSUT points, but the same doesn't happen on the Garmin 1000.

It seems like everything is as you said, like the typical MSFS issue, but what surprised me was that in the test you did with the stock DA-62, WP1 is added as FPL000 and everything is working as expected. I've studied the reasons, and it turns out I was using the DA62X (not standard in FS2024), and you were using the DA62 (standard in FS2024).

As a result, and after investigating this matter a little further, I've found that the error I'm seeing always occurs in all non-standard FS2024 aircraft... DA62X, C208, G36, etc., etc., and never happens with standard FS2024 aircraft... DA62, C172, TBM930, Baron58, etc., etc.

All of this confirms your comment that it looks like the typical MSFS issue.

We'll have to wait for MSFS2024 development to continue and for this and many other bugs to be fixed.

Thank you very much, Alex, for your help. I'd like to take this opportunity to congratulate you on your excellent program, which is so helpful to all flight simulation enthusiasts.

Regards

JJ Gómez Prieto

Do the aircraft you use for testing have a custom, non standard GPS? Maybe it would make sense to contact the add-on developer since the flight plan is valid and shows ok in the flight planner and EFB.

Alex

Edited May 6, 20251 yr by albar965

Yes, in the tests I've done with different aircraft, all of them are equipped with standard Garmin, but as I mentioned earlier, as a result, and after investigating this matter a little further, I've found that the error I'm seeing always occurs in all non-standard FS2024 aircraft... DA62X, C208, G36, etc., etc., and never happens with standard FS2024 aircraft... DA62, C172, TBM930, Baron58, etc., etc.
Thank you very much, Alex, for your help.
Regards
JJ Gómez Prieto

The plans already show ok in the opening screen and other aircraft. I'm afraid I cannot help much with this.

Alex

You've helped me a lot, and I'm grateful, Alex.

Thank you very much.
J J Gómez