Jump to content

Recommended Posts

Posted

Hey everyone,

 

The error message when launching Little Navmaps 2.8.12:

"Could not find a simulator installation on this computer. Also, no scenery library databases were found".

Tools > Connect to a flight simulator only shows 2 tabs: Xplane, and Remote/Network

 

I have the Steam version of MSFS installed on a Linux computer (Ubuntu 22.04).

The Steam install is located at /media/[user]/[drive]/SteamLibrary/steamapps/common/MicrosoftFlightSimulator

The Community folder is located at /media/[user]/[drive]/SteamLibrary/steamapps/compatdata/1250410/pfx/drive_c/users/steamuser/AppData/Roaming/Microsoft Flight Simulator/Packages

 

Is there a way to point Little Navmaps to the right folder locations?

 

Thanks!

Posted (edited)
Quote

I have the Steam version of MSFS installed on a Linux computer (Ubuntu 22.04).

BTW - does MSFS2020 Steam edition already natively work under SteamOS/Linux? 
Linux user here 🙂

Regards,
Piotr

Edited by ppgas

Never give up ...  - here are details of the whip-round: https://zrzutka.pl/en/pewr2d  -> to help my younger son fights against Acute Lymphoblastic Leukemia (blood cancer).

Posted

Thanks Alex, I feel I'm making some progress. Here's where I am now:

  • Little Navconnect is running.
  • Little Navmap status is "Connected to remote flight simulator"

Navconnect logs:

[2024-01-02 13:02:09] Little Navconnect

[2024-01-02 13:02:09] Version 2.8.8 (revision d8a0eb5).

[2024-01-02 13:02:09] Data Version 11. Reply Version 5.

[2024-01-02 13:02:09] Connecting to X-Plane using the Little Xpconnect plugin.

[2024-01-02 13:02:09] Starting server. This can take some time ...

[2024-01-02 13:02:09] Server is listening on hostname pop-os (IP address 192.168.2.10) port 51968.

[2024-01-02 13:02:09] Server running.

[2024-01-02 13:02:09] Not connected to the simulator. Waiting ...

[2024-01-02 13:05:15] Connection from pop-os (192.168.2.10).

 

At the moment though, when flying, the plane doesn't appear on the map, the flight is not tracked. I don't have the impression that "Connected to remote flight simulator" is accurate.

 

On the navconnect manual it says:

You will see MSFS and X-Plane for for the Windows 64-bit build of Little Navconnect. FSX or Prepar3D and X-Plane are shown for For the 32-bit build of Little Navconnect.

These menu items are not shown on Linux and macOS since the only connection option is X-Plane.

 

Could that explain the connection issue on Linux? Does this mean Navmap is not compatible with MSFS on Linux?

 

 

8 hours ago, ppgas said:

BTW - does MSFS2020 Steam edition already natively work under SteamOS/Linux? 
Linux user here 🙂

Regards,
Piotr

You'll have to go to Steam > Settings > Compatibility, then activate "Enable steam play on all other titles".

Some people have reported issues, see https://www.protondb.com/app/1250410 - personally I'm alright (for now). It runs great, the only downside is that I had to buy it again (originally got it via the MS store).

Posted
3 hours ago, SgtCapybara said:

At the moment though, when flying, the plane doesn't appear on the map, the flight is not tracked. I don't have the impression that "Connected to remote flight simulator" is accurate.

You have to "sit in the cockpit" and Navconnect needs a sim connection to see aircraft updates. Otherwise it says connected without showing the user aircraft.

3 hours ago, SgtCapybara said:

Could that explain the connection issue on Linux? Does this mean Navmap is not compatible with MSFS on Linux?

LNM under Linux does not need to know anything about MSFS, as the connection is simulator-independent. This mMeans that you can mix connections between Windows, Linux and macOS builds.

 

3 hours ago, SgtCapybara said:

[2024-01-02 13:02:09] Not connected to the simulator. Waiting ...

Seems that Navconnect cannot connect to X-Plane.
Did you install Xpconnect and can you see it in the X-Plane plugins menu? Navconnect needs Xpconnect for X-Plane.

Alex

Posted

Hey Alex,

I know that troubleshooting issues remotely can be tricky, and I'd like you to know that I really appreciate your patience.

I decided to clean up everything and start over, in case I made a mistake when playing with some settings. Here's what I have now:

1. MSFS2020 (Steam version) installed on Ubuntu 22.04
2. LNM (LittleNavmap-linux-22.04-2.8.12.tar.gz) located in Documents on the same drive

MSFS2020 is running, I'm in a good old Cessna 152, staring at the cockpit.

I launch LNM, I see the welcome pop-ups when LMN loads up for the first time.

"Tools" -> "Create Directory Structure" is complete, the directory is created under /home/[user]/Documents/Little Navmap Files. It contains 7 folders, all empty.

"Scenery Library" -> "Load Scenery Library" is greyed out (no simulator)

"Tools" -> "Connect to Flight Simulator" brings up a pop-up window with only 2 tabs: "Xplane" and "Remote/Network". The "FSX, Prepar3D or MSFS" tab is missing.

The status messages at the bottom of the LNM window are:
- Not connected
- Database is empty

And that's where I am now.

Have I missed anything?

Posted

MSFS runs in the Wine Windows emulation layer if installed from Steam AFAIK.  LNM cannot see/detect MSFS if running on Linux in this case.

You'd have to run the LNM Windows version in the same Wine instance to see MSFS. Then you should be able to load the scenery library and connect to MSFS. Never tried this but quite a brave approach.🙂 Keep me posted how it's going.

I'm using here Linux (Kubuntu) for development and all other serious work and Windows for flying.

Alex

  • 7 months later...
Posted
1 hour ago, celtikred said:

Hi there, did you find a solution ? same issue here. Any way to have LNM detecting MSFS2020 running from steam on linux proton ? thx

Run LNM Windows in the same Windows emulation layer (Wine) as the simulator and LNM might find MSFS. I did not try it but theoretically it should work.
LNM just scans a bunch of paths and files to find MSFS. Here is how LNM find MSFS from the FAQ:

Quote

 

How does Little Navmap find the MSFS scenery library, or MSFS installation not found  🔗

Click Reset Paths in the scenery library load dialog if you’ve moved your simulator.

Little Navmap looks into fixed installation folders for the various MSFS installation options (MS Online, MS Boxed or Steam). There are no Windows registry entries used. Installation on a removable drive is usually no problem.

Little Navmap first looks for a file UserCfg.opt at the following fixed locations:

  1. MS online installation: C:\Users\USER\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt
  2. Steam installation: C:\Users\USER\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt
  3. MS Boxed installation: C:\Users\USER\AppData\Local\MSFSPackages\UserCfg.opt

Replace USER with your login name.

The text file UserCfg.opt contains a last line InstalledPackagesPath which points to the MSFS scenery library.

From there Little Navmap looks up ...\Official\Steam\fs-base\layout.json or ...\Official\OneStore\fs-base\layout.json to check if the installation path is really valid or if it consists only of remains from previous installations.

Detection problems can usually caused by file permission issues, missing files or folders or remaining files from previous installations.

 

Alex

Posted

Hi Alex, I managed to install LNM in the same wineprefix as FS2020 and he found my MSFS setup, fetching scenery libraries. He also found MSFS2020 in the connect dialog box but still can't connect to it. Connection seem to hang ... I've launch MSFS first then LNM from protontricks explorer in the same wineprefix... Any hint ?

Posted
3 hours ago, celtikred said:

Hi Alex, I managed to install LNM in the same wineprefix as FS2020 and he found my MSFS setup, fetching scenery libraries. He also found MSFS2020 in the connect dialog box but still can't connect to it. Connection seem to hang ... I've launch MSFS first then LNM from protontricks explorer in the same wineprefix... Any hint ?

Sorry, no idea what's going on there. LNM 64-bit uses the latest SimConnect.dll which is included in the LNM download. So nothing to update there.
The 64-bit installer also installs the required MSVC redistributable packages. I'd recommend to use the installer instead of the Zip packages. Otherwise you have to add the redist packages manually. I collected all here: https://www.littlenavmap.org/downloads/Windows Redistributable Packages/

You can search for "SimConnect" in the FAQ: https://albar965.github.io/littlenavmap-faq.html
There are a few topics with hints regarding SimConnect issues.

You can also try to run Little Navconnect in Wine and then use the Linux LNM to connect remotely through the local network to it.

Alex

Posted
On 8/19/2024 at 4:34 PM, albar965 said:

Sorry, no idea what's going on there. LNM 64-bit uses the latest SimConnect.dll which is included in the LNM download. So nothing to update there.
The 64-bit installer also installs the required MSVC redistributable packages. I'd recommend to use the installer instead of the Zip packages. Otherwise you have to add the redist packages manually. I collected all here: https://www.littlenavmap.org/downloads/Windows Redistributable Packages/

You can search for "SimConnect" in the FAQ: https://albar965.github.io/littlenavmap-faq.html
There are a few topics with hints regarding SimConnect issues.

You can also try to run Little Navconnect in Wine and then use the Linux LNM to connect remotely through the local network to it.

Alex

Hi Alex,

I've tried many ways including using Window version LNconnect in the same Wine environment as MSFS. Launching LNM in native linux mode then connecting to 'wine' LNConnect works but unfortunately, (wine) LNConnect detects MSFS (same proton prefix) but hangs while trying to connect to it... Also installed both Windows Redistributable packages had no effect.

Is there any way to troubleshoot Navconnect/simconnect connection from tools or config file ? thx

Posted
10 hours ago, celtikred said:

Is there any way to troubleshoot Navconnect/simconnect connection from tools or config file ?

I'm sorry but I have no idea what can cause this.

No idea what to add if you're through the FAQ and all SimConnect issues there.🤷‍♂️

Alex

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...