Load Scenery Library greyed out

[betelgeuse]

 

I am running FSX/LNM/LNconnect in W10 on a network with LNM using W7.

 

The flying PC connects with LNM on the networked machine - I checked that the GS changes.

Problem is that I cannot load the scenery library - LNM shows that I am using XP11.

I'd be grateful for advice. 

 

Edited September 23, 2024 by betelgeuse

[albar965]

You have to load the scenery library on the flying computer and then copy the database file(s) over to the remote. These files are read-to-use and no loading required on the remote.

See here for details: https://www.littlenavmap.org/manuals/littlenavmap/release/latest/en/NETWORK.html

Alex

[betelgeuse]

Thank you for your speedy reply.

I followed the instructions as best I could several times. I hope I copied them to the right place on the network computer - the same as their source in the flying PC. 

Each time, I get the exception message below.

This is followed by a Runtime error.

 

 

Edited September 23, 2024 by betelgeuse

[albar965]

1 hour ago, betelgeuse said:

Thank you for your speedy reply.

I followed the instructions as best I could several times. I hope I copied them to the right place on the network computer - the same as their source in the flying PC. 

Each time, I get the exception message below.

This is followed by a Runtime error.

 

The file little_navmap_navigraph.sqlite is outdated and LNM chokes on the old database schema. You can fix this by updating the Navdata on the flying computer using the Navigraph FMS Data Manager with a new cycle and then copy the file to the remote computer again.

Actually this is a LNM bug in 3.0.9 since I try to keep backward compatibility as much as possible. You can also try the 3.0.10.rc1 where this is fixed: https://www.avsim.com/forums/topic/649551-little-navmap-3010rc1-released/

Alex

[betelgeuse]

4 hours ago, albar965 said:

The file little_navmap_navigraph.sqlite is outdated and LNM chokes on the old database schema. You can fix this by updating the Navdata on the flying computer using the Navigraph FMS Data Manager with a new cycle and then copy the file to the remote computer again.

Actually this is a LNM bug in 3.0.9 since I try to keep backward compatibility as much as possible. You can also try the 3.0.10.rc1 where this is fixed: https://www.avsim.com/forums/topic/649551-little-navmap-3010rc1-released/

Alex

Thanks again.  The 3.0.10.rc1 version fixed it.  I would have liked to use the Navigraph FMS but it isn't available for FSXSE afaik.

Like others on this board and elsewhere, I'm amazed by, and grateful for, LNM in equal measure. ⭐

 

Howard

Edited September 23, 2024 by betelgeuse

[albar965]

11 hours ago, betelgeuse said:

Thanks again.  The 3.0.10.rc1 version fixed it.  I would have liked to use the Navigraph FMS but it isn't available for FSXSE afaik.

Like others on this board and elsewhere, I'm amazed by, and grateful for, LNM in equal measure.

Good to hear and thank you for your kind words!

Alex

[elveezle]

Hello there, I am trying to link load global scenery with Msfs 2024 but the option is Greyed out plus there is a prompt at the bottom indicating Database is empty. I was able to connect the sim with Little Navmap and I can track the plane with also altitude. Any help or advice you have for me?

[albar965]

7 hours ago, elveezle said:

Hello there, I am trying to link load global scenery with Msfs 2024 but the option is Greyed out plus there is a prompt at the bottom indicating Database is empty. I was able to connect the sim with Little Navmap and I can track the plane with also altitude. Any help or advice you have for me?

Do you use the beta? 3.0.12 stable does not support MSFS 2024.

The scenery library is loaded via SimConnect now since Asobo removed all the needed files.

Alex

[elveezle]

Thanks mate I have downloaded at it looks better thus far