Everything posted by SgtCapybara
-
Little Navmap does not detect MSFS install on Ubuntu 22.04
SgtCapybara replied to SgtCapybara's topic in Little Navmap | Little Navconnect | Little Logbook Support ForumThanks Alex, I'll try your suggestions.
-
Little Navmap does not detect MSFS install on Ubuntu 22.04
SgtCapybara replied to SgtCapybara's topic in Little Navmap | Little Navconnect | Little Logbook Support ForumHey 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?
-
Little Navmap does not detect MSFS install on Ubuntu 22.04
SgtCapybara replied to SgtCapybara's topic in Little Navmap | Little Navconnect | Little Logbook Support ForumThanks 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? 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).
-
Little Navmap does not detect MSFS install on Ubuntu 22.04
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!