I've been using Little Navmap 2.2.4 and while it worked well for a long time I had many discrepancies between the flight plans it created and the ones I programmed in aircraft such as PMDG, etc.

Today I purchased Navigraph subscription and fsAerodata subscription. I followed all instructions and updated everything so all would be in sync with AIRAC cycle 1905. I tried Loading the Scenery Library in LNM and it barely gets going and then crashes. The crash says was in Qt5Core.dll.

Here is a link to the log generated. I can't determine what caused the crash.

http://galactichub.com/abarthel-little_navmap.zip

Much thanks in advance for help.

Jim

Note: ALL my flight sim apps are installed outside of protected directories with FULL permissions for "everyone", so not a permissions issue.

 

 

UPDATE:

I just spent two hours analyzing the log and determined that the following files, which were updated by fsAerodata were causing Little Navmap to crash. I reverted to the backups of just these files and it now works. I had to rerun the scenery database library builder for each fail. Whew! 

Note the following:
I lost nearly all the VOR's, half my ILS's, 80% of NDB's, and 75% of waypoints since my last Little Navmap build prior to using fs Aerodata. Here is a comparison of when I ran it against the default P3D v4.5 data vs. the "updated" fsAerodata .

default P3D v4.5 data Last Update: Mon May 6 15:30:52 2019. Database Version: 14.13. Program Version: 14.13.
Currently Loaded:
Files:     14,778
VOR:        4,326
Markers:    4,721
Airports:  25,920
ILS:        3,558
Waypoints:104,438
NDB:        7,698
Airspaces: 21,258

fsAerodata Last Update: Tue May 14 15:36:50 2019. Database Version: 14.13. Program Version: 14.13.
Currently Loaded:
Files:        14,629
VOR:             116
Markers:       4,721
Airports:     26,135
ILS:           1,609
Waypoints:    25,370
NDB:           1,277
Airspaces:     5,481

 

It sure would be great if LNM and fsAerodata could sort out the reason for the crash and avoid it so I can do next month's update.

 

Again, here are the offending fsAerodata files:

Scenery path "C:\\Games\\Prepar3D v4\\Scenery\\0001"
APX03130.bgl
Scenery path "C:\\Games\\Prepar3D v4\\Scenery\\0004"
APX02320.bgl
C:\Games\Prepar3D v4\Scenery\0104
APX10390.bgl
C:\Games\Prepar3D v4\Scenery\0200\scenery
APX16040.bgl
C:\Games\Prepar3D v4\Scenery\0203\scenery
APX18250.bgl
C:\Games\Prepar3D v4\Scenery\0303\scenery
APX30300.bgl
C:\Games\Prepar3D v4\Scenery\0305\scenery
APX26410.bgl
APX31400.bgl
C:\Games\Prepar3D v4\Scenery\0306\scenery
APX30510.bgl
APX30550.bgl
C:\Games\Prepar3D v4\Scenery\0404\scenery
APX32350.bgl
C:\Games\Prepar3D v4\Scenery\0406\scenery
APX33540.bgl
C:\Games\Prepar3D v4\Scenery\0502\scenery
APX47210.bgl
C:\Games\Prepar3D v4\Scenery\0602\scenery
APX52220.bgl
APX52230.bgl
APX54220.bgl
C:\Games\Prepar3D v4\Scenery\0603\scenery
APX50260.bgl
APX53240.bgl
APX53260.bgl
APX55250.bgl
C:\Games\Prepar3D v4\Scenery\0604\scenery
APX54320.bgl
C:\Games\Prepar3D v4\Scenery\0702\scenery
APX58220.bgl
C:\Games\Prepar3D v4\Scenery\0703\scenery
APX60290.bgl
APX61290.bgl
C:\Games\Prepar3D v4\Scenery\0704\scenery
APX60350.bgl
APX61350.bgl
APX63340.bgl
C:\Games\Prepar3D v4\Scenery\0801\scenery
APX65140.bgl
APX66130.bgl
APX71110.bgl
C:\Games\Prepar3D v4\Scenery\0802\scenery
APX69200.bgl
C:\Games\Prepar3D v4\Scenery\0901\scenery
APX73120.bgl
APX73140.bgl
C:\Games\Prepar3D v4\Scenery\0902\scenery
APX76160.bgl
APX77160.bgl
C:\Games\Prepar3D v4\Scenery\0903\scenery
APX77260.bgl
APX79240.bgl
C:\Games\Prepar3D v4\Scenery\1002\scenery
APX85220.bgl
C:\Games\Prepar3D v4\Scenery\1005\scenery
APX84400.bgl
C:\Games\Prepar3D v4\Scenery\1104\scenery
APX88340.bgl

Edited May 14, 20197 yr by ArJunaBug

Hi Jim,

update the LNM database with the Navigraph FMS Data Manager. To work around the LNM crash you can exclude the fsAerodata folder from LNM loading.

That way you can ignore the P3D navdata because Navigraph delivers are fully compiled navdatabase for LNM.

I'll check the latest fsAerodata update.

Edit: I can see the crash here too. No idea what stuff has sneaked into the BGLs again. Have to see. This will take a while.

Alex

Edited May 14, 20197 yr by albar965
Can see crash as well

Thanks Alex,

Can you clarify. I already used Navigraph to update LNM. I did it twice actually, a second  time after I had issues. The crashes were occurring it seems from the fsAerodata replaced files in the P3D scenery folders.

I have now excluded the entire fsAerodata program and data folder in LNM, which I installed completely in C:/games/fsAeroData, including subdirectories for  "fsAerodata Files" and "backup".

Does this mean there is no reason to run the Scenery Library updater anymore? Because I just did as you said and I returned one of the files I listed above that caused the crash and the scenery library updater still crashes until I again revert that one file back to the original P3D version. Again, does this mean there is no need to run the Scenery Library updater anymore? It seems I would need this to pickup third party add-ons.

 

I'm afraid the next time I run FsAerodata I will end up with issues and I am still seemingly missing nearly all the VOR's, half my ILS's, 80% of NDB's, and 75% of waypoints since my last Little Navmap build prior to using Navigraph and fsAerodata.

Thanks so much for your help.

Jim

BTW, I posted this issue over on the fsAerodata Forum as well.

I just sent another donation to you for your help and fine program.

Edited May 14, 20197 yr by ArJunaBug

2 minutes ago, ArJunaBug said:

Can you clarify. I already used Navigraph to update LNM. I did it twice actually, a second  time after I had issues. The crashes were occurring it seems from the fsAerodata replaced files in the P3D scenery folders.

The FMS Data Manager sometimes fails to find the correct LNM installation path: https://albar965.github.io/littlenavmap_navigraph.html

5 minutes ago, ArJunaBug said:

The crashes were occurring it seems from the fsAerodata replaced files in the P3D scenery folders. 

That is an issue now. These files cannot be excluded since they contain the updated airport information.

8 minutes ago, ArJunaBug said:

Does this mean there is no reason to run the Scenery Library updater anymore? Because I just did as you said and I returned one of the files I listed above that caused the crash and the scenery library updater still crashes until I again revert that one file back to the original P3D version. Again, does this mean there is no need to run the Scenery Library updater anymore?

Yes and no. You have to run it to get the airports. Everything else comes from the Navigraph database. See here for information about what data sources are used:
https://www.littlenavmap.org/manuals/littlenavmap/release/2.2/en/NAVDATA.html

I have no idea when I can fix this. Have to see.

Alex

I read your links and I am sure I did everything correctly. I just double-checked it all. It does seem there is an issue with those specific files I listed and they are obviously critical.

Until it gets resolved I think I will restore fsAerodata back to original P3D files and rerun the Scenery Library loader, then I will rerun fsAerodata to revert to the backed up original P3D v4.5 scenery files. I will also rerun the Navigraph FMS manager on LNM although it's probably not necessary. I expect this will get me running for now as best it can be.

I will keep an eye out here and on fsAerodata forum for any updates. i will cross post any solution that comes up.

Ah! A typical flight sim day, hours and hours of tweaking and when finally ready almost to tired to fly.  🙂

Thanks again,

Jim

58 minutes ago, albar965 said:

Edit: I can see the crash here too. No idea what stuff has sneaked into the BGLs again. Have to see. This will take a while.

Alex,

No issues on my end with FSX and I use both Navigraph and fsAerodata with 1905.

Just realized that there is an update to fsAerodata, which I haven't done, so perhaps it's in FSX also.  Going to wait until I hear from your end..

Ernie

Edited May 14, 20197 yr by airernie

I just followed the procedure I outlined two posts up and it seems I got pretty much what I was hoping.

I have a boat load of data in LNM now.

Compare the following three LNM scenery library reports. The first from before I installed Navigraph and faAerodata, the next with the corrupted/crashing fsAerodata files removed, and finally the one using original P3D v4.5 scenery with fsAerodata removed, but Navigraph database in LNM updated.

Navigraph added a LOT of nav data. With all my FMS aircraft and other add-ons updated with latest AIRAC cycle I have confidence this will be an improvement already. It will be nice to have the P3D navdata up to date when this gets fixed.

Jim

 

Last Update: Mon May 6 15:30:52 2019. Database Version: 14.13. Program Version: 14.13.
Currently Loaded:
Files:     14,778
VOR:        4,326
Markers:    4,721
Airports:  25,920
ILS:        3,558
Waypoints:104,438
NDB:        7,698
Airspaces: 21,258

Last Update: Tue May 14 15:36:50 2019. Database Version: 14.13. Program Version: 14.13.
Currently Loaded:
Files:        14,629
VOR:             116
Markers:       4,721
Airports:     26,135
ILS:           1,609
Waypoints:    25,370
NDB:           1,277
Airspaces:     5,481

Last Update: Tue May 14 17:15:32 2019. Database Version: 14.13. Program Version: 14.13.
Currently Loaded:
Files:        21,765
VOR:           5,732
Markers:       4,721
Airports:     27,739
ILS:           4,512
Waypoints:   265,382
NDB:           8,505
Airspaces:    54,660

12 hours ago, ArJunaBug said:

Ah! A typical flight sim day, hours and hours of tweaking and when finally ready almost to tired to fly.

LOL. I know that. For me also in combination with programming stuff.

12 hours ago, airernie said:

No issues on my end with FSX and I use both Navigraph and fsAerodata with 1905.

Just realized that there is an update to fsAerodata, which I haven't done, so perhaps it's in FSX also.  Going to wait until I hear from your end.. 

Yup. Don't update to 1905r1 for now if 1905 is fine.

You can choose to use the fsAerodata updated data or the Navigraph database in LNM. Use the latter one. fsAerodata is for updating the simulator navdata but the Navigraph database for LNM contains much more information like speed restrictions for approaches.

I'll post here once I have something.

Alex

Alex,

Check out the fix over at fsAerodata. I had posted the issue there and they said it's now resolved. I will test in a few minutes.

Cheers,
Jim

https://www.fsaerodata.com/forum/viewtopic.php?f=4&t=387

I can confirm that they (Jose) just released fsArodata config tool version 1.02.13 did resolve the issue.
Jim

Edited May 16, 20197 yr by ArJunaBug

4 hours ago, ArJunaBug said:

I can confirm that they (Jose) just released fsArodata config tool version 1.02.13 did resolve the issue.
Jim

Hi Jim,

thanks plenty for testing but I can still reproduce the crash. Already posted in the fsAerodata forum.

Alex

3 minutes ago, albar965 said:

Hi Jim,

thanks plenty for testing but I can still reproduce the crash. Already posted in the fsAerodata forum.

Alex

I followed Jose's instructions on the other thread and reran the LNM scenery library rebuild and it worked perfectly. I did end up with a considerably different report from LNM scenery library since my temporary fix yesterday. I did not, however, re-download and install the AIRAC cycle in fsAerodata.  I did check to ensure some of the offending files I listed in my OP were replaced this morning with the fsAerodata update. They were replaced with new files and no longer crashed LNM. It is curious that you are still having  issues.

Last Update: Tue May 14 17:15:32 2019. Database Version: 14.13. Program Version: 14.13.
Files:        21,765
VOR:           5,732
Markers:       4,721
Airports:     27,739
ILS:           4,512
Waypoints:   265,382
NDB:           8,505
Airspaces:    54,660

Last Update: Thu May 16 05:53:49 2019. Database Version: 14.13. Program Version: 14.13.
Files:       21,615
VOR:          4,707
Markers:      4,721
Airports:    27,531
ILS:          4,279
Waypoints:  230,278
NDB:          5,343
Airspaces:   37,603

 

I will leave mine as is and let you follow up. I will keep an eye here to find out what happens.

Let me know if you'd like me to try anything on my end to help out.

Jim

I'll hold the update back if there are no big issues. Let me know if something blows up somehow, somewhere...

Alex