[UNOFFICIAL] Running BMS on Linux/WINE with opentrack HOWTO
-
@Ferde yep, 4.8. I don’t think dotnet would have anything to do with falcon-bms-control, though, I was just mentioning it to describe my setup.
-
@wsy Thanks. Will make some tries.
-
OK, I spent too many hours trying a new install and several ways of installing dependencies with no joy. If I have dotnet 4.8 neither the alternative launcher or the bms control server work.
Out of hope I’ve tried again my working install and run bms control in another way and this time it worked!!! It happened the same to me that some buttons work and others don’t. I guess this has to do with conflicting shortcuts with Linux? I will try rebinding those controls as you suggested to be sure.
Edit: yes, that was it. After rebinding the buttons that weren’t working I have fully working MFDs
-
@Ferde
BTW Next release of wine-mono should make AL work OOB. it already work on Proton-experimental.
The only remaining issue is, it’s unable to detect SteamVR and so there’s no option shown to enable VR.
Aside from that, it’s perfectly functional. -
@Xeno Good to know. My install works already with mono, although not the launcher boxes.
But that improvement will probably help with weapon delivery planner and helios and, as you mentioned earlier, even voice commands! -
@Ferde OK… this is weird… I now have working checkboxes!
My hypothesis is that I briefly tried wine 9.5 and that maybe installed some mono newer version? Because I’m now back to 7.22
-
I still have no joy (Proton 9 from Gentoo repo, latest wine-mono), get this error when launching AL ootb.
-
@wsy
I suppose Gentoo provides wine-mono 9.0, which predates fixes for few non-implemented functions AL needs.
I’m using proton-experimental provided by Valve and AL works just fine as said abovr. I haven’t really had a chance to try Fedora packages, here wine is stuck at 9.1 and wine-mono at 8.1.
See bugreport: https://bugs.winehq.org/show_bug.cgi?id=56324 -
@Xeno nice, thank you! Checkboxes now work, but BMS does not launch, tough choice Will experiment more.
-
@wsy
Both Wine and Proton still need external d3dx11_43 lib installed. Assuming DXVK is installed that’s last issue for having BMS working OOB under Linux. -
@Xeno you are completely right; just for the record (all this info is already in your posts), here are my steps:
- Install clean wineprefix with Gentoo wine-proton 9;
- Install Falcon 4;
- Install BMS;
At this point AL does not launch. - Update wine-mono with .msi file from the above github link;
AL launches with checkboxes visible; Falcon crashes after the initial splash screen. - Install d3dx11_43;
Falcon launches but the main menu is flickering. - Install dxvk;
Now everything seems to work, including opentrack and falcon-bms-control. Everything needs to be launched with WINEESYNC=1.
I will test more, but currently it seems to me that it runs faster than on my old setup through Steam Proton with an older Proton version and dotnet.
-
Hmm I wonder if that guide could help me get it working on my steamdeck…
-
@SOBO-87
In short yes, assuming you have some experience with Wine/Proton and how prefixes work.
I’ll add more detailed steps once I’ll be able to get back to my gaming PC. -
@SOBO-87
Ok here’s more detailed BMS on Steam/Proton how-to.
Note: under Linux ~/ is equal to your current user home directory, ie /home/<username>- Install Falcon 4.0 from Steam.
- Set Proton-experimental as compatibility layer:
- in Steam/Library rightclick on Falcon 4.0, select properities.
- on ‘Compatibility’ tab check ‘Force the use of a specific Steam Play compatibility tool’
- select ‘Proton Experimental’ from dropdown list.
- Run Falcon 4.0 at least once.
- Open file browser and create anywhere in your home directory a dir where you want to install BMS and dir where BMS installation file gonna be located. . Here I’ll use ~/MySims and ~/SimFiles as example.
- Put Falcon BMS installation files in ~/SimFiles dir.
- Prepare Falcon prefix for BMS : add your sims dir as a drive in Proton, install d3dx11_43:
- launch Protontricks, select “Falcon 4.0: 429530”, click “Ok”, click “Ok” button on all warning windows that will pop up.
- from a list pick “Select default Wine prefix” and click “Ok”
- select “Install Windows DLL lib or component” click “Ok”
- select “d3dx11_43” and click ok to install. Once donw, Protontricks should be back to previous list.
- select “Launch winecfg”, click Ok.
- in ‘Drives" tab click add button to add new drive letter, here I’ll be using E: and F:
Highlight first added drive "E:’, click on ‘Browse’ button and point it to ~/MySims and click “Ok” to confirm. Do the same for second drive added “F:” and point it to ~/SimFiles.
Click "Apply’and ‘Ok’ to confirm changes and close wincfg window - select “launch explorer” and click ‘Ok’
- Install BMS: in open explorer window navigate to F: drive and launch BMS installer. Choose target installation path to anywhere on drive 'E: ', prefferably with no spaces in directory name
Here I used ‘E:\Falcon_BMS_4.37’
Procceed as under windows, there’s no need to add BMS dir to exceptions, nor set firewall rules. Let installer look for updates. It should open windows terminal window. Run updater from commandline. - Create BMS launcher file. Open any text editor and paste there lines below:
#!/bin/bash export WINEFSYNC=1 export STEAM_COMPAT_DATA_PATH="/home/$USERNAME/.local/share/Steam/steamapps/compatdata/429530/" export STEAM_COMPAT_CLIENT_INSTALL_PATH="/home/$USERNAME/.local/share/Steam/" export PROTON_PATH="/home/$USERNAME/.local/share/Steam/steamapps/common/Proton - Experimental" "$PROTON_PATH"/proton run /home/$USERNAME/MySims/Falcon_BMS_4.37/Launcher/FalconBMS_Alternative_Launcher.exe 2>&1
Verify all the paths to files are correct and save text file anywhere in your home dir, here ~/MySims/BMS_proton_launcher.sh is used.
In file browser find your file, right-click on it, select ‘Properities’. On ‘Priviledges’ tab, check ‘allow execution’ and click ‘Ok’
9. Create program shortcut for launcher file:- launch file browser, navigate to ~/MySIms, rightclick anywhere in empty space in files window and select ‘Create new…’ / ‘New applicatiopn shortcut’
- in new shortcut dialog window, on ‘General’ tab, put some any name you like, optionally you can click on the icon button to change shortcut icon. I’m not sure if proton add BMS icons to the system, but you can select ‘All category’ and use ‘search’ to filter icons.,
- on 'Priviledges tab, check ‘Allow execution’
- on ‘Application’ tab, put again any name you like, click ‘Browse’ button to point it to your launcher file, here ~/MySims/BMS_proton_launcher.sh and click ‘Open’ to select target file, then ‘Ok’ to create shortcut.
Copy desktop file to ~/.local/share/applications/ you may also drag shortcut file to Desktop and/or Task manager on the bottom panel. (place where all launched apps are visible)
** Note ~/.local is a hidden dir, assuming SteamOS uses Dolphin as default file browser, you can use ‘Left Alt’ + ‘.’ (dot) combo to toggle ‘show hidden files’
Done.
[EDIT]
BTW this setup should be VR ready, only thing needed is working HMD and manually flipping VR enable option in config files as AL under Linux is unable to detect SteamVR.
Easiest HMDs to get working uner Linux are standalone headsets used with ALVR. Just make sure you have hardware video encoding enabled and run precompiled binaries or even compile latest stable release by yourself. It’s not that difficult and ALVR wiki provides all the info you need.
I have no experience with older SteamVR headsets and Monado/OpenHMD may not be a thing until u4 and migration to OpenXR. -
@Xeno Thanks for the guide! Also, amazing that VR now works.
I am running into an issue after I installed Falcon 4.0 (I also added d3dx11_43 via winetricks). I tried Proton9/Experimental in Steam and when I launch Falcon 4.0 it only shows a black screen and a pop-up that reads:
DevCreateSurface; Failed to
Error 593 C:\mpr\ddk\eng\esurface.c Oct 8 1999Any idea how I can fix this issue?
-
I assume it’s failed first run? TBF I’ve never tried to run original 4.0 under Experimental.
If it’s error from Falcon 4.0 itself most likely all the reg entries are there. I’d try to install BMS and see if it works.
If not then yu may try to uninstall Falcon 4.0 via Steam, force lower compatibility layer version (ie 8.0), install Falcon 4.0, run it once. If succeeded, then install BMS using Experimental as described. Newer version of Proton should upgrade prefix on it’s own. -
@Xeno Thanks, I tried that. There seems to be something wrong with my Steam installation. After installing Falcon 4.0 and looking at Properties > Installed files I can see
“Falcon 4.0 is using third party software to update its own files. Content updates and file management by Steam are not available.”
I cannot verify the integrity of game files and I get some weird access issues. Other games run fine, it’s just Falcon 4.0 for some reason.
Edit: I forgot to install lib32-nvidia-utils. Everything works now, incl. VR.
-
@Munster
Hi, I’m glad you’ve sorted it out. Happy flying …
BTW may I ask which HMD you have. -
@Xeno Thank you! I am using the Valve Index.
Also, I am wondering if this the “best” way to get into VR, or if you have a different workflow.
I had to edit both files and set set g_nVRHMD 1
/home/x/.local/share/Steam/steamapps/compatdata/429530/pfx/drive_c/Falcon BMS 4.37/User/Config/Falcon BMS.cfg
/home/x/.local/share/Steam/steamapps/compatdata/429530/pfx/drive_c/Falcon BMS 4.37/User/Config/Falcon BMS User.cfgThen I started the Falcon BMS.exe directly:
STEAM_COMPAT_DATA_PATH=“/home/x/.local/share/Steam/steamapps/compatdata/429530/” STEAM_COMPAT_CLIENT_INSTALL_PATH=“/home/x/.local/share/Steam/” “/home/x/.local/share/Steam/steamapps/common/Proton - Experimental/proton” run “/home/x/Games/FalconBMS/drive_c/Falcon BMS 4.37/Bin/x64/Falcon BMS.exe”Going through the alternative launcher didn’t work for me to get into VR. But I only tried it last night for a bit, so I may have overlooked something.
-
I kinda trick AL, use it to get axis mapping/keybind done, then manually enable VR in user config, then launch via AL with config overide disabled, so VR stays on.
Ahh cool, I’m battling with Pico4/ALVR it works, but there are some issues with image stability under Linux. All the white labels on panels and instruments are flickering in unison, kinda like you’d watch old TV. A bit distracting. Other than that it works fine. A pity, because under Windows image clarity/stability is superb, but still there’s a progress on Linux side so hopefully at some point it’ll catch up.
How it is with PCVR HMDs is there any difference in image quality?