How is it currently, is everything working?

Edited April 2Apr 2 by Ricardo Andrada

Did someone find a way update AIRAC data via Navigraph? I can install Navigraph Hub but it won't detect the sim.

On 4/2/2026 at 11:17 AM, Ricardo Andrada said:

How is it currently, is everything working?

Fenix still doesn't work, but I kinda stopped troubleshooting that, waiting for their next update first. they may change stuff around, who knows. Also didn't try ifly since it also runs an external program. 

GSX and BATC also didn't work. 

But everything else (A pilots' life 2, vRaas, fsltl, other addons that don't do complex stuff like GSX, airports, aircrafts, etc) are all working. 

I did get Navigraph working as well. I believe you have to run it in the same proton context. I can look it up later. 

It runs very smooth. Occasionally it crashes, but that's only on startup (1 out of 10 times, maybe), so it doesn't matter; I just restart it and then it works. Once running, I haven't seen any crashes in the middle of the flights. 

Perfectly happy with it so far, and willing to accept the few limitations as I'm sure it will continue to improve. I feel like I could get GSX working, I got close to seeing something, but honestly I'm happy with the sim without needing to do further trouble shooting. 

I created a little guide, I can post that here. 

MSFS 2024 on CachyOS Linux — Complete Setup Guide

A living document covering everything needed to run Microsoft Flight Simulator 2024 and its addons on CachyOS (Arch-based Linux) with KDE Plasma.

System Info

• OS: CachyOS (Arch-based) with KDE Plasma
• GPU: NVIDIA RTX 4080
• MSFS 2024 Steam App ID: 2537590
• Proton: GE-Proton10-32
• Proton prefix: ~/.local/share/Steam/steamapps/compatdata/2537590/pfx
• AUR helper: paru
• Bootloader: Limine

---

0. Desktop Session Setup

Log in under X11 if you experience issues with Wayland. This may not be needed — Wayland is working currently.

---

1. Install MSFS 2024

Install MSFS 2024 through Steam as normal.

---

2. Install GE-Proton

Install GE-Proton10-32 (or latest):

1. Download from: https://github.com/GloriousEggroll/proton-ge-custom/releases
2. Extract to: ~/.steam/root/compatibilitytools.d/
3. Restart Steam
4. Right-click MSFS 2024 → Properties → Compatibility → Force GE-Proton10-32

At this point, MSFS should run normally, but won’t exit fully and the Honeycomb Bravo won’t work.

---

3. Honeycomb Bravo — udev Rules & HID Passthrough

Getting the Honeycomb Bravo to show up in MSFS 2024 on Linux requires two things: ensuring the Linux kernel gives you permission to access the device, and convincing Wine/Proton to see it as a flight controller instead of a generic Xbox gamepad.

Set Permissions (udev Rules)

By default, Linux may restrict raw access to the Bravo’s HID interface, which MSFS needs for the LEDs and full button mapping.

Create a udev rule file:

sudo nano /etc/udev/rules.d/99-honeycomb-bravo.rules

Contents:

KERNEL=="hidraw*", ATTRS{idVendor}=="294b", ATTRS{idProduct}=="1901", MODE="0666", TAG+="uaccess"

Reload rules and replug the Bravo:

sudo udevadm control --reload-rules && sudo udevadm trigger

Steam Launch Options

Right-click MSFS 2024 in Steam → Properties → Launch Options:

PROTON_ENABLE_HIDRAW=0x294b/0x1901 %command%

If you already have other launch options, add this to the beginning followed by a space.

At this point, MSFS is running with all controllers working.

---

4. SimConnect Configuration

SimConnect must be configured for TCP so external tools (vRAAS, FSLTL, FSUIPC7, APLv2, etc.) can connect. The default pipe-based SimConnect does not work reliably under Wine/Proton, so we use a networked IPv4 connection on localhost port 5111.

SimConnect.xml (Server — tells MSFS to expose SimConnect)

Location: ~/.local/share/Steam/steamapps/compatdata/2537590/pfx/drive_c/users/steamuser/AppData/Roaming/Microsoft Flight Simulator 2024/SimConnect.xml

<?xml version="1.0" encoding="UTF-8"?>
<SimBase.Document Type="SimConnect" version="1,0">
  <Descr>SimConnect Server Configuration</Descr>
  <Filename>SimConnect.xml</Filename>
  <SimConnect.Comm>
    <Disabled>False</Disabled>
    <Descr>Static IP4 port</Descr>
    <Protocol>IPv4</Protocol>
    <Scope>global</Scope>
    <Address>127.0.0.1</Address>
    <Port>5111</Port>
    <MaxClients>64</MaxClients>
    <MaxRecvSize>41088</MaxRecvSize>
  </SimConnect.Comm>
</SimBase.Document>

Note: Port 5111 is used because port 500 is often reserved for system services (IKE/IPSec VPNs) and might require root privileges or be blocked by the firewall.

SimConnect.cfg (Client — tells apps how to connect)

[SimConnect]
Protocol=IPv4
Address=127.0.0.1
Port=5111
MaxReceiveSize=41088
DisableNagle=0

Place this file in ALL of the following locations to ensure every SimConnect client finds it regardless of how it’s launched (exe.xml auto-launch, protontricks shell, etc.):

1. User Documents folder (universal fallback for all SimConnect clients): ~/.local/share/Steam/steamapps/compatdata/2537590/pfx/drive_c/users/steamuser/Documents/SimConnect.cfg

2. MSFS config folder (picked up by exe.xml-launched apps whose working directory is MSFS’s folder): ~/.local/share/Steam/steamapps/compatdata/2537590/pfx/drive_c/users/steamuser/AppData/Roaming/Microsoft Flight Simulator 2024/SimConnect.cfg

3. Next to each app’s .exe (guaranteed to be found by that specific app):

   • vRAAS: ...AppData/Local/LAND3.vRAAS/current/SimConnect.cfg
   • FSLTL: ...Microsoft Flight Simulator 2024/Packages/Community/fsltl-traffic-injector/SimConnect.cfg

Quick setup command to place the cfg in all key locations:

PREFIX="$HOME/.local/share/Steam/steamapps/compatdata/2537590/pfx/drive_c/users/steamuser"

# Create the cfg content
CFG_CONTENT="[SimConnect]
Protocol=IPv4
Address=127.0.0.1
Port=5111
MaxReceiveSize=41088
DisableNagle=0"

# Documents folder (universal fallback)
echo "$CFG_CONTENT" > "$PREFIX/Documents/SimConnect.cfg"

# MSFS config folder (for exe.xml launched apps)
echo "$CFG_CONTENT" > "$PREFIX/AppData/Roaming/Microsoft Flight Simulator 2024/SimConnect.cfg"

# vRAAS app directory
echo "$CFG_CONTENT" > "$PREFIX/AppData/Local/LAND3.vRAAS/current/SimConnect.cfg"

# FSLTL injector directory
echo "$CFG_CONTENT" > "$PREFIX/AppData/Roaming/Microsoft Flight Simulator 2024/Packages/Community/fsltl-traffic-injector/SimConnect.cfg"

Verify SimConnect is listening

After MSFS is fully loaded:

ss -tlnp | grep 5111

You should see wineserver listening on port 5111.

At this point, FSLTL is working great, all addons are working, all controllers are working.

---

5. Install protontricks

Required for installing Windows apps into the MSFS Proton prefix:

paru -S protontricks

Important: Never use system wine to launch apps in the Proton prefix — it will give a version mismatch error. Always use protontricks-launch --appid 2537590 to ensure the correct GE-Proton Wine version is used.

---

6. FSUIPC7

Download Install_FSUIPC7.exe from the FSUIPC website.

Install into the MSFS Proton prefix:

protontricks-launch --appid 2537590 ~/Downloads/Install_FSUIPC7.exe

FSUIPC7 installs to C:\FSUIPC7\FSUIPC7.exe inside the prefix.

Verify:

find ~/.local/share/Steam/steamapps/compatdata/2537590/pfx/drive_c -name "FSUIPC7.exe" 2>/dev/null

Nothing special needed — just a normal install.

---

7. A Pilot’s Life v2 (APLv2)

Install APLv2

Download APL_V2_v2.2.1.181.msi from SimBitWorld.

protontricks-launch --appid 2537590 ~/Downloads/APL_V2_v2.2.1.181.msi

Installs to C:\Program Files (x86)\SIMBITWORLD\A PILOT'S LIFE - CHAPTER 2\

Copy System.Device.dll

APLv2 requires System.Device.dll which Wine Mono doesn’t include. Copy it from a Windows 11 installation.

On Windows 11, find it at: C:\Windows\Microsoft.NET\assembly\GAC_MSIL\System.Device\v4.0_4.0.0.0__b77a5c561934e089\System.Device.dll

Copy to the APLv2 directory:

cp ~/Downloads/System.Device.dll "$HOME/.local/share/Steam/steamapps/compatdata/2537590/pfx/drive_c/Program Files (x86)/SIMBITWORLD/A PILOT'S LIFE - CHAPTER 2/"

Known Limitation — Map

The APLv2 in-app map will show a black screen. Wine’s built-in IE/mshtml engine cannot render the modern JavaScript map APIs that APLv2 uses. All other features (career, flight tracking, airline management) work fine. Use Little Navmap (runs natively on Linux) as an alternative moving map.

---

8. Microsoft Edge / WebView2

Installed into the prefix for apps that use WebView2. Note: WebView2 rendering doesn’t fully work under Wine/Proton, but the runtime is available.

Download the Windows 64-bit MSI offline installer from: https://www.microsoft.com/en-us/edge/business/download

protontricks-launch --appid 2537590 ~/Downloads/MicrosoftEdgeEnterpriseX64.msi

winecfg Changes

After installing Edge, you may want to add a compatibility override for WebView2:

protontricks 2537590 winecfg

In the winecfg window:

1. Go to the Applications tab
2. Ensure Default Settings is set to Windows 10
3. Click Add application
4. Browse to: C:\Program Files (x86)\Microsoft\Edge\Application\<version>\msedgewebview2.exe
5. Select it and set the Windows version dropdown to Windows 7 (or Windows 10 — neither fully fixes WebView2 rendering under Wine, but having the override prevents some apps from crashing)
6. Click Apply, then OK

Note: WebView2 rendering does not work under Wine/Proton regardless of this setting. Apps that use WebView2 for maps or embedded web content will show a blank/black screen. However, having Edge installed and this override set prevents crashes in apps that check for WebView2 presence.

---

9. vRAAS (Virtual Runway Awareness and Advisory System)

vRAAS by LAND3 Simulations provides realistic RAAS callouts (runway approach alerts, too high/fast warnings, etc.) with optional PFD/ND text display. It connects to MSFS via SimConnect.

Purchase and Install

vRAAS is sold exclusively through the Contrail store. You need the Contrail app running in the MSFS prefix to purchase, download, and install it.

Install Contrail

1. Download the Contrail installer from https://getcontrail.com/
2. Extract it (the .exe is an NSIS installer that needs manual extraction):

cd ~/Downloads
mkdir contrail-extract && cd contrail-extract
7z x ../ContrailSetup*.exe
7z x ./ContrailApp-*-full.nupkg

3. Move the app files into the prefix:

mkdir -p ~/.local/share/Steam/steamapps/compatdata/2537590/pfx/drive_c/Contrail
mv ./lib/net45/* ~/.local/share/Steam/steamapps/compatdata/2537590/pfx/drive_c/Contrail/

4. Launch Contrail:

protontricks -c "wine C:/Contrail/Contrail.exe" 2537590

Note: First launch may hang on “Installing Dependencies” for several minutes. Be patient or restart if needed.

Install vRAAS via Contrail

1. Log in to your Contrail account
2. Purchase/activate vRAAS
3. Let Contrail install it — it installs to C:\users\steamuser\AppData\Local\LAND3.vRAAS\current\
4. Enter your serial number when prompted

SimConnect.cfg for vRAAS

Place a SimConnect.cfg next to the vRAAS executable (see Section 4 for contents and the quick setup command):

~/.local/share/Steam/steamapps/compatdata/2537590/pfx/drive_c/users/steamuser/AppData/Local/LAND3.vRAAS/current/SimConnect.cfg

Community Folder Plugin

vRAAS installs a community folder plugin (panel-raas) for PFD/ND text display. Verify it’s in place:

ls ~/.local/share/Steam/steamapps/compatdata/2537590/pfx/drive_c/users/steamuser/AppData/Roaming/Microsoft\ Flight\ Simulator\ 2024/Packages/Community/panel-raas/

Key Paths

Item	Path (inside prefix drive_c)
vRAAS executable	users/steamuser/AppData/Local/LAND3.vRAAS/current/vRAAS.exe
vRAAS settings	users/steamuser/AppData/Roaming/vRAAS/
vRAAS community plugin	users/steamuser/AppData/Roaming/Microsoft Flight Simulator 2024/Packages/Community/panel-raas/

---

10. exe.xml — Auto-Launch Apps with MSFS

This tells MSFS to automatically start addons when the sim loads.

Location: ~/.local/share/Steam/steamapps/compatdata/2537590/pfx/drive_c/users/steamuser/AppData/Roaming/Microsoft Flight Simulator 2024/exe.xml

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Auto launch external applications on MSFS start</Descr>
  <Filename>exe.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.Addon>
    <Name>FSUIPC7</Name>
    <Disabled>False</Disabled>
    <Path>C:\FSUIPC7\FSUIPC7.exe</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>A Pilot's Life v2</Name>
    <Disabled>False</Disabled>
    <Path>C:\Program Files (x86)\SIMBITWORLD\A PILOT'S LIFE - CHAPTER 2\SBW_APL_V2.exe</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>vRAAS</Name>
    <Disabled>False</Disabled>
    <Path>C:\users\steamuser\AppData\Local\LAND3.vRAAS\current\vRAAS.exe</Path>
  </Launch.Addon>
</SimBase.Document>

Important: For exe.xml-launched apps to connect via SimConnect, the SimConnect.cfg must be placed in the MSFS config folder and/or the Documents folder — not just next to the app’s exe. When MSFS spawns addons via exe.xml, their working directory is MSFS’s own folder, not the addon’s install directory. See Section 4 for the full placement strategy.

---

Manual Launch Commands

If exe.xml auto-launch doesn’t work, open a protontricks Wine shell and launch from there. This ensures the app shares the same wineserver as MSFS:

protontricks 2537590 shell

Then from the Wine command prompt:

vRAAS:

cd "C:\users\steamuser\AppData\Local\LAND3.vRAAS\current"
vRAAS.exe

FSLTL Traffic Injector:

cd "C:\users\steamuser\AppData\Roaming\Microsoft Flight Simulator 2024\Packages\Community\fsltl-traffic-injector"
fsltl-trafficinjector.exe

FSUIPC7:

C:\FSUIPC7\FSUIPC7.exe

APLv2:

"C:\Program Files (x86)\SIMBITWORLD\A PILOT'S LIFE - CHAPTER 2\SBW_APL_V2.exe"

Note: Using protontricks -c "wine ..." from a separate terminal may spawn a separate wineserver that cannot see MSFS’s SimConnect. The protontricks shell method (protontricks 2537590 shell) shares the existing wineserver and is more reliable.

---

Key Paths Reference

Item	Path (inside prefix drive_c)
MSFS config folder	users/steamuser/AppData/Roaming/Microsoft Flight Simulator 2024/
SimConnect.xml	...Microsoft Flight Simulator 2024/SimConnect.xml
SimConnect.cfg (MSFS folder)	...Microsoft Flight Simulator 2024/SimConnect.cfg
SimConnect.cfg (Documents)	users/steamuser/Documents/SimConnect.cfg
exe.xml	...Microsoft Flight Simulator 2024/exe.xml
FSUIPC7	FSUIPC7/FSUIPC7.exe
APLv2	Program Files (x86)/SIMBITWORLD/A PILOT'S LIFE - CHAPTER 2/SBW_APL_V2.exe
System.Device.dll	Program Files (x86)/SIMBITWORLD/A PILOT'S LIFE - CHAPTER 2/System.Device.dll
Edge/WebView2	Program Files (x86)/Microsoft/Edge/Application/
vRAAS executable	users/steamuser/AppData/Local/LAND3.vRAAS/current/vRAAS.exe
vRAAS settings	users/steamuser/AppData/Roaming/vRAAS/
Contrail app	Contrail/Contrail.exe
FSLTL injector	...Microsoft Flight Simulator 2024/Packages/Community/fsltl-traffic-injector/fsltl-trafficinjector.exe
Community folder	...Microsoft Flight Simulator 2024/Packages/Community/
Proton prefix root	~/.local/share/Steam/steamapps/compatdata/2537590/pfx

---

Important Notes

• Never use system wine to run apps in the Proton prefix. Always use protontricks-launch --appid 2537590 or the protontricks shell.
• Do NOT install dotnet48 in the MSFS prefix — it can break MSFS’s existing Mono setup. APLv2 works with Wine Mono + the System.Device.dll workaround.
• Windows Fast Startup can cause NTFS mounting issues if dual-booting. Use ntfsfix to resolve.
• SimConnect.cfg placement matters. Always place it in Documents, the MSFS folder, AND next to each app’s exe for maximum compatibility.
• protontricks shell vs protontricks -c: The shell method shares the existing wineserver with MSFS. The -c method may create a separate wineserver that can’t connect to SimConnect.

---

Still To Do

•  Fenix [gave up]
•  GSX [gave up]
•  vRAAS
•  iFly [never tried]
•  BATC [starts, but doesn't connect to sim]

Note that the guide above is my way to do it, on Linux there are many ways to do stuff, so don't think this is the ONLY way to do things. 

On 2/26/2026 at 5:40 PM, JonathanC said:

Intro animation has an easy fix. From Claude (and verified working on my system). That was the one  tweak I mentioned. 

-----------

Install ProtonGE

The easiest way on CachyOS is with ProtonPlus or ProtonUp-Qt:
sudo pacman -S protonup-qt

Launch it, make sure it's set to add versions for Steam, then click Add Version → select GE-Proton → pick GE-Proton10-32 → Install.
Set MSFS 2024 to Use It

Open Steam
Right-click MSFS 2024 → Properties
Go to Compatibility tab
Check "Force the use of a specific Steam Play compatibility tool"
Select GE-Proton10-32 from the dropdown

That's it. Launch the game normally after that.

Why GE-Proton?
GE (GloriousEggroll) Proton is a community fork of Valve's Proton with extra patches, codec support, and fixes that haven't made it upstream yet — it often works better for games with launchers or DRM like MSFS 2024.

-------

 

Nope! I simply mounted my Windows drive, then set the community folder location inside MSFS (the usual way, nothing fancy, just using the menus inside MSFS), and loaded up.. and basically all the addons that don't need an executable running just loaded right up. All my sceneries, the PMDG .. everything. 

 

Sitting in PMDG 777 at Ini EGLL right now - 

Now, I need to get the following addons working

 

1. Fenix

2. GSX

3. TDS GTNxi

4. vRAAS

5. fsLTL

6. ? (got some others that I forget right now). 

Obviously no idea if there are breaking bugs or whatever, but everything seems normal so far. 

I'm almost certain you cannot get the TDS to run... but I'm curious 🙂

3 minutes ago, ryanbatc said:

I'm almost certain you cannot get the TDS to run... but I'm curious 🙂

Yeah, I kinda didn't bother. I accept that there are some limitations, knew that going in. For me, it does 98% of what I wanted, and CachyOS is otherwise so amazing (simming is like 20% of what I do on the computer, the other 80% is vastly vastly better for me) that I'm happy. 

And MSFS 2024 is MUCH smoother on Cachy.. no idea why, but it just is. 

Just now, JonathanC said:

Yeah, I kinda didn't bother. I accept that there are some limitations, knew that going in. For me, it does 98% of what I wanted, and CachyOS is otherwise so amazing (simming is like 20% of what I do on the computer, the other 80% is vastly vastly better for me) that I'm happy. 

And MSFS 2024 is MUCH smoother on Cachy.. no idea why, but it just is. 

Less bloatware and background word not allowed that linux for sure.  I dual booted in the early 2000s and generally enjoyed it.

In general, after using it for weeks now, it is a good experience. You have to accept that addons that run external exe's may r may not work (GSX, Fenix, TDS, that kind of thing).

Some do work (FSLTL, vRAAS, APLv2 work), and it depends mostly on whether the external app is just using simconnect/FSUIPC (in which case it will likely work fine once simconnect is setup like in my guide above, FSUIPC just works), or directly manipulating memory or else using a custom method for sim-to-app communication (in which case, who knows if it will work).

But exe's that don't need to talk to the sim (PMDG OC3, Inibuilds, orbx, etc.. all the installer type stuff, navigraph and so on) and just place files work just fine. 

And addons that are in the marketplace (A340, Seaworks Simulations) or just simpler stuff works absolutely fine. No impact whatsoever. the vast majority of my 600 GB+ of addons (sceneries, planes, bijan, aig, etc) work seamlessly and really well. 

Edited April 4Apr 4 by JonathanC

@JonathanCA huge "Thank you" for the tipp to use protontricks-launch command to install apps. I used it to install the Navigraph hub. Now Navigraph can "see" the sim, however if I try to install the AIRAC cycle I get the following message: "Operation failed. System.ComponentModel.Win32Exception (87): Invalid Parameter."

Do you have any idea how to fix that?

 

This is awesome! Please keep it updated with your latest findings @JonathanC.

Times are a changin' and more and more folks are feeling alienated by Microslop. Linux gaming is growing in popularity and new products like the MacBook Neo are going to get even more folks on non-Windows platforms.

@JonathanC Thank you very much for the feedback you are giving us

On 4/5/2026 at 6:18 AM, -Belga- said:

@JonathanCA huge "Thank you" for the tipp to use protontricks-launch command to install apps. I used it to install the Navigraph hub. Now Navigraph can "see" the sim, however if I try to install the AIRAC cycle I get the following message: "Operation failed. System.ComponentModel.Win32Exception (87): Invalid Parameter."

Do you have any idea how to fix that?

 

Hey, I took a different approach for these tools that only need using once in a while for updates, and that only download files from the internet and place them in folders. 

I installed WinBoat (basically runs a Windows VM), and inside Winboat, I shared my home directory. Now, Windows can access my files. 

Next step, I created a "fake" MSFS 2024 install to fool the apps into thinking it's just a standard windows install with MSFS 2024 in the usual directory. For this, all you need to do is place a UserCfg.opt (text file) in this location:

C:\Users\<YOURUSERNAME>\AppData\Roaming\Microsoft Flight Simulator 2024

And then you change the InstalledPackages path to point to the long path that refers to your Linux install. 

The contents of my UserCfg.opt

 

--------

Version 66
{Video
    Adapter "NVIDIA GeForce RTX 4090"
    Monitor 0
----etc all the config details --- no need to touch that --- just copy as it
...

...

--- and here the config ends ---
}

InstalledPackagesPath

"C:Users\USERNAME\Desktop\Shared\.local\share\Steam\steamapps\compatdata\2537590\pfx\drive_c\users\steamuser\AppData\Roaming\Microsoft Flight Simulator 2024\Packages"

------------

 

Once this is done, you can install all the installer apps (Contrail, OrbX, IniManager, Navigraph, OC3.. etc). Any installer that runs on Windows and places files in the Community Folder will work just fine. 

You cannot use this method to run stuff that needs to run WITH the simulator (Fenix, GSX etc) as the sim is not going to actually run in this Windows VM. But it's the simplest way to keep files updated without messing about with Wine and Proton and what not. 

When I need to update anything, I start the Windows VM and use the installer/updater program, it places the files in the Community Folder as normal, then I close the WIndows VM and run MSFS in Linux. 

Also, it doesn't have to be WinBoat - You can use any VM software you like, the key thing is the ability to share the home folder with the Windows VM (which pretty much every VM program allows, AFAIK), and then the UserCfg.opt trick. 

According to AI (and I agree, I know these programs well):

VirtualBox — Probably the easiest for your use case. Free, cross-platform, and shared folders are straightforward: install Guest Additions in the Windows VM, then add a shared folder pointing to your Linux home directory in the VM settings. It'll show up as a network drive in Windows. Good performance for general desktop use, simple GUI.

VMware Workstation Pro — Now free for personal use (since 2024). Generally has better performance than VirtualBox, especially for graphics. Shared folders work via VMware Tools, similar setup. Slightly more polished but heavier.

 

Edited April 6Apr 6 by JonathanC