Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Juanito1

Members
  • Joined

  • Last visited

Everything posted by Juanito1

  1. You've helped me a lot, and I'm grateful, Alex. Thank you very much. J J Gómez
  2. 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
  3. 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
  4. 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
  5. 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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.