[UNOFFICIAL] Running BMS on Linux/WINE with opentrack HOWTO
-
@tank2 I’m still using wine 7.22 because after so many years I’ve finally decided to not touch something that works… hehehe.
But yes, aside of the checkmark buttons not showing up in the launcher. Everything else seems working well for me.
-
@Ferde
I don’t want to jinx it, but just to be safe, I’d advice to stay with Wine 7
I’ve installed fresh Fedora 37 and Wine 7.22. So far (about 10 runs) problem didn’t occur.
I’ll test it for few more days, just to be sure, before I’ll call it success.
Still some input from would be helpful to do proper bug report on wine bugzilla. -
@Xeno Good to know! Thanks for this.
Good to know also my laziness brought the solution.
-
A bit of cross-posting, for me last known safe Wine release is 8.14, Next version that has Fedora packages is 8.17 and this one failed at first run. That’s good news, because bug occurred so it’s not something releated to other system packages but just wine, and I could narrow it down so solid bug report can be made.
Another good news at least for Fedora users, there are wine 8.14 packages for latest Fedora 39, which is also nice because 39 is first release witn onnx runtime rpms, becasue it makes much easier to package opentrack the right way.
BTW If somebody is interested, I have rough Fedora 39 opentrack 2023.3.0 x86_64 rpms with NN tracker, wine and fgfs output protocols and naturalmovement filter made. So far no X-Plane plugin (that should be easy) and Aruco and Tobii trackers, the latter is new one in 2023.3.0. It won’t build with default config, co I have to find out how to configure the build. -
I’ve added BMS 4.37u3 to the wine database, so guys plz add your test data. Also there are two bug reports related, one about BMS failing to load 3D models win wine 8.17 and later and other about always empty checkboxes in AL. If anybody is able to reproduce those, plz add you comment, to let devs know it’s not just my system that is wonky.
-
This weekend I was trying to find out if/how much choice of DE/window systems affects BMS performance. For improvised test suite I’ve picked up Training mission 13 Maverick basic spawned taxi, raining mission 14 Maverick advanced, in the air on the route to Stp 4, then 5 and finally Benchmark TE also spawning on taxi slot.
For each mission, I compared same (or very close) view/position, with both TGP stdby and on, also in TE #14 with both TGP and Mav camera on.
Test setup involved KDE Plasma 5.27 and Gnome 4 running in both Wayland and X11 sessions.
Basic conclusion is, it really doesn’t matter that much. If FPS on my rig was below 200FPS results were at best 5 FPS apart, usually around 1-2 FPS. I’m not sure what was more of a surprise: the fact that Gnome X11 session seem to be slowest one, althoug a tiny bit or Gnome Wayland being fastest in situations where FPS were already above 200FPS. At the beginning of training TE 14 in Gnome Wayland session sim hit ~270 fps where other sessions were closer to 230-240 range.[EDIT]
So after further observations, FPS reaching +300FPS in the beginning of TE 14 is not exclusive to Gnome Wayland sessions, it happens on Plasma Wayland too, fps there oscillate there in 190-310 fps range, with 210-240 most of the time. -
Any of BMS Linux/Wine users dipped toe into VR waters?
I’ve made a bit impulsive decisio to buy Pico 4 once I found iot on Amazon for sub 400$ (VAT included).
So my plan is to make it work with Wine -> SteamVR -> ALVR -> Pico 4 stack. -
Does anyone have experience with running FalconBMS in Proton? So far I cannot even make 4.0 to work let alone BMS and VR.
Regular wine seem to be missing a shim app that sends OpenVR calls to linux native SteamVR. -
I bit the bullet and reported feature request type of bufg on wine bugzilla.
https://bugs.winehq.org/show_bug.cgi?id=56145
Guys plz bump it up with some comments to show some interest in Wine providing support for VR so we can enjoy our sim in VR on our preferred OS. -
Tomorrow when I get off work, I will be creating a new Guide on how to get Falcon BMS completely working less steps, open track as well couple clicks to get that running.
also DCS world is working, Mariana has weird texture glitches but Persian Gulf and Syria and Caucasus work great!
p.s will end up making a youtube tutorial to help us linux guys ( Im new to linux ) so I am quite proud to share what has been achieved with the seed planted by alot of you guys
-
@Kevstosmart said in [UNOFFICIAL] Running BMS on Linux/WINE with opentrack HOWTO:
Tomorrow when I get off work, I will be creating a new Guide on how to get Falcon BMS completely working less steps, open track as well couple clicks to get that running.
also DCS world is working, Mariana has weird texture glitches but Persian Gulf and Syria and Caucasus work great!
p.s will end up making a youtube tutorial to help us linux guys ( Im new to linux ) so I am quite proud to share what has been achieved with the seed planted by alot of you guys
painful but here it is, would happen to slit my index finger on some copper metal roofing panels today
https://forum.falcon-bms.com/topic/26604/how-i-got-falcon-bms-on-linux
-
Small update on BMS/VR on Linux project:
First Valve fixed Falcon 4.0 not installing properly in Proton 8.05. It seem all the ddls needed for VR are already there.
I’ve made it to the point where BMS starts in VR, I can see UI in the headset, once commited to 3D world BMS recognizes headtracking just fine, picture on 2D display shows proper rendering if display mirroring is enabled, but no picture is sent to headset. Actual bitrate of the video stream, it falls from +100MBps to around 10MBps or less.
AL also cannot detect SteamVR runtime, so VR mode has to be enabled manually in config file.On a sidenote Proton 8.05 fixed invisible tickmarks in checkboxes, but for some reason AL is unable to find BMS key files.
-
@Xeno case sensitive?
-
@MaxWaldorf Unlikely, I did a short test and copied ./BMS*Full.key files to lowercase and AL still didn’t pick’em up, it complained about being unable to obtain ProductID or something like that.
Also iirc AL worked fine in regular wine (albeit without visible tickmarks). I’m suspecting some of the Valves changes broke it. TBF it’s kind of schizophrenic company, the things they do in Linux graphics stack are absolutely top notch, OTOH Linux ports of Steam, SteamVR and Proton to some extend provide less than stellar experience. and Anyways it’s less of a matter for me right now. I’d love to know whos’ to blame for no picture in VR headset. -
@Xeno said in [UNOFFICIAL] Running BMS on Linux/WINE with opentrack HOWTO:
short test and copied ./BMS*Full.key files to lowercase and AL still didn’t pick’em up
Can you explain, what are you expecting to happen – when and why?
In normal course of day to day usage, AL doesn’t look for or load BMS-Full.key.
Only upon initial run … if there is no BMS-Auto.key yet, if starts off by making a copy of BMS-Full.key.
I can’t promise a fix for any given linix/wine/proton stack, but if you share the AL log file, I’ll certainly take a look… maybe something trivial.
Maybe non-trivial… the Microsoft.DirextX wrappers that it uses are ancient… 32-bit, from .NET v1 era. They barely work on modern 64-bit Windows.
(Recent bug reports on GH from someone having problems with it on Linux… but it self-resolved after some OS or Wine update. Your problem with ProductID sounds maybe similar)
-
@airtex2019
Thanks for all of the responses. First let me retest it with plain wine. Last time I had similar problem was where I tested beta of 4.37 AL you provided with 4.36, it complained a bit about missing F-15 key file, once I copied BMF Full key as one for Eagle AL launched with no errors.
With proton situation sem to be a bit different, in spare moment need to investigate what they broke. Is it some of their library override rules or it’s caused by change in wine Valve did.
For now, my focus is on get VR working.
And as you’ve chimed in, if/once you’ll find spare moment (I agree any issues related to running BMS under Wine are low priority) can you tell me how AL detects SteamVR presence? In proton prefix there are some reg entries and steam binaries (i dno’t know real or fake) in program files dir, yet AL didn’t show VR switch. -
@Xeno not my area unfortunately – all I can say is “it’s complicated” but you can read through the SteamVR detection code and maybe make heads or tails of it.
-
@airtex2019 said in [UNOFFICIAL] Running BMS on Linux/WINE with opentrack HOWTO:
@Xeno said in [UNOFFICIAL] Running BMS on Linux/WINE with opentrack HOWTO:
short test and copied ./BMS*Full.key files to lowercase and AL still didn’t pick’em up
Can you explain, what are you expecting to happen – when and why?
In normal course of day to day usage, AL doesn’t look for or load BMS-Full.key.
Only upon initial run … if there is no BMS-Auto.key yet, if starts off by making a copy of BMS-Full.key.
I can’t promise a fix for any given linix/wine/proton stack, but if you share the AL log file, I’ll certainly take a look… maybe something trivial.
Maybe non-trivial… the Microsoft.DirextX wrappers that it uses are ancient… 32-bit, from .NET v1 era. They barely work on modern 64-bit Windows.
(Recent bug reports on GH from someone having problems with it on Linux… but it self-resolved after some OS or Wine update. Your problem with ProductID sounds maybe similar)
I’ve retested AL with regular Wine + .Net 4.* (4.0 to 4.8) installed. It works fine. In Proton prefix there’s only .Net 4.8 installed so I’m assuming Proton is trying to use wine-mono as .Net 4.6.2 runtime.
In spare moment I’ll try Proton with .Net 4.6.2 installed and report back. -
@Xeno There’s a program called protontricks that is basically winetricks for proton and detects all your steam installs, including the ones added manually. Maybe that can help you with the proton prefix.
-
Today I was able to get brief moment when I got proper pit view in the headset when flying Training mission #2. I have no idea, why for a moment it worked, how to replicate and why it worked in this mission but not others but still.
SO guys, if any of you has headset working under Linux give it a try and post results. Maybe with more data points we’ll be able to come to any conclusion.[edit]
Reports form somebody using PCVR headset (Reverb G2 or similar) would be super valuable. At this point I’m not sure if it’s matter of streaming part not being able to keep up or just Linux port of SteamVR doing something stupid. ‘tho’ I’m rather leaning for the latter.BTW ALVR on Windows works fine, but Windows AMD encoders sucks in terms of quality.