[UNOFFICIAL] Running BMS on Linux/WINE with opentrack HOWTO
-
WINESYNC=1 - that’s not something I have enabled, open track works fine. I’ve tried setting it, no observable difference.
Also, emacs-nox? Is that really a build dep? (No one should have to install emacs! )
Sent from my iPhone using Tapatalk
-
It’s WINEESYNC not WINESYNC, another flag is WINEFSYNC. It corresponds with settings in opentrack wine plugin. In my case that was the key to get headtracking working, without this flag BMS nor IL2 couldn’t detect opentrack. If it wasn’t nessesary for you, I guess it might be something to do with how WINE is configured/compiled in different distros.
Some more info here:
https://github.com/ValveSoftware/Proton/issues/1722#issuecomment-749061952 -
Sorry, yes, mobile phone fingers mis-typing it on here.
I’ve tested with winehq builds and Ubuntu releases, I don’t seem to need any extra env variables for opentrack to work.
Sent from my iPhone using Tapatalk
-
Also, emacs-nox? Is that really a build dep? (No one should have to install emacs! )
How could you want to live without an emacs installation on your Unix system? The mind, it is boggled
All the best,
Uwe
-
This post is deleted! -
Excuse me while I go load my supersoaker…
You can always do
M-x vi-mode
in emacs if you must
All the best, Uwe
-
This post is deleted! -
Guys, friendly banter is nice, but keep this thread informative. Let it be good source of info for those who struggle to run our beloved sim on the OS of their choice.
BTW It seems recommended wine version might be bumped to 6.0 maybe a bit higher. I need to upgrade it release by release and retest if opentrack wine wrapper is still working.
Hopefully it also enable AlternateLauncher as .NET 4.8 was broken under WINE 5.18-5.22.P.S.
Would somebody using Ubuntu or other distro, test this procedure to make sure it works for anybody else than me?
Once proven we might ask to make it sticky. -
Has anyone else encountered this from opentrack:
[ WARN:0] global ../modules/videoio/src/cap_v4l.cpp (998) tryIoctl VIDEOIO(V4L2:/dev/video0): select() timeout. ```Appears to have started only today, since a package upgrade (incl. kernel), and occurs when opentrack tries to open the camera at anything other than 30Hz. My headtracking knowledge is extremely limited, but running at 30Hz does work, in some sense of the word, but it's patchy at best, and rarely returns to the centre. It's the same build of opentrack as I've using for several weeks - hoover's build, in fact - and also affects my own build. Very strange! (I appreciate this isn't a general Linux support thread, but as this is about headtracking on Linux, if you experienced/wise folk have a solution it might be something that ends up in the FAQ - I can delete these comments later)
-
Here I’m running 5.11.10, cam is PS3 EYE
1415:2000 Nam Tai E&E Products Ltd. or OmniVision Technologies, Inc. Sony Playstation EyeOpentrack running @75FPS no problem. My first guess would kernel update. Could you boot older one and see if problem persists?
BTW confirmed, it’s WINE 6.3 that breaks opentrack, so if there are no reports of issues with v6.2, then i think it might be considered last known good version of wine for BMS and other sims.
-
Sounds like we’re on the same hardware. Pretty sure it’s the kernel update too; I hate Ubuntu!
-
Unfortunatelly .NET 4.8 is still broken with 6.2 so no AL for now.
-
I can get it to 50Hz with a newer kernel, but not beyond. This still leaves quite stuttery headtracking Random changes like this are normal for Windows, not Linux!
-
50FPS should be enough, is it connected directly to the m/b port or trough hub? I suspect there might be something fishy about port bandwidth. Maybe bad hub or low voltage? IIRC even 30FPS should give relatively smooth tracking. It’s more about fps being stable.
Anyways, maybe it’s time to fill a bug? -
Thanks for this - headtracking on linux is something I have yet to tackle.
I didn’t see anything about hardware in this thread. What hardware has been tested? Is this something that works with a webcam alone? Can I use a TrackIR5? What hardware is recommended?
-
NaturalPoint does not support Linux. IIRC opentrack does not support trackir. There’s another project for it, but I have no experience with it. TBH I just started this headtracking adventure.
For me classic PS3 Eye + 3 IR diodes freetrack clip (selfmade, Delan or other clones) combo does the job good enough. -
Another small update, I’ve tried Wine 6.6 (Fedora rpms), opentrack crash is fixed, but somehow mouse doesn’t work in a pit at all, ie no cursor unable to click anything I guess we have to wait a lil’ bit longer for Wine releasse good for BMS.
As usual, pls post your experience with Wine releases available for your distro. It might help others to decide if they wanna stick with what wine they have or upgrade. -
Some maybe-FAQs… for someone who doesn’t live and breathe linux everyday (except maybe to manage headless virts in the cloud) but is willing to try dual-booting his desktop
-
is there a specific distro to recommend? (or, any specific distros known not to work?)
-
any perf comparisons vs Windows 10, on same hardware?
-
any known issues or pitfalls with video drivers (nvidia or amd)?
-
what about joystick drivers … or do they all just-work via HID class drivers?
is there a recommended tool for calibration/mapping similar to vJoy+Gremlin?
-
-
Some maybe-FAQs… for someone who doesn’t live and breathe linux everyday (except maybe to manage headless virts in the cloud) but is willing to try dual-booting his desktop
-
is there a specific distro to recommend? (or, any specific distros known not to work?)
-
any perf comparisons vs Windows 10, on same hardware?
-
any known issues or pitfalls with video drivers (nvidia or amd)?
-
what about joystick drivers … or do they all just-work via HID class drivers?
is there a recommended tool for calibration/mapping similar to vJoy+Gremlin?
Ubuntu 20.04 is working well for me - I wouldn’t normally choose Ubuntu, but it’s what was on the laptop.
Performance. With dxvk, at 3440x1440 on Linux for the Landing TE, I get roughly 110fps showing as the overall fps but with the occasional millisecond blip/stutter. Under Windows 10, same hardware, same resolution, same TE, 78fps.
Nvidia drivers seem solid but without the same options easily accessible as under Windows. I’ve done some fiddling here and there, but found it best to just leave it alone.
Joystick - not had any issues with device detection or with setting bindings, but do have calibration issues because I can’t get the CH software to work under Linux (yet)
The biggest reason I still use Windows (off an external drive) is that I haven’t invested the time in making kungfoo’s ICP and MFD app send the right keybindings under Linux - there’s something strange there.
-
-
WRT Distros, I think any of mainstream ones (*buntu/Mint, SUSE, Fedora) should be fine, Arch/Gentoo as long ans properly configured, I see no reason to be bad, just more troublesome because those two come not preconfigured.
My experience is limited to AMD/Intel GPUs, I stick to those because of Linux, Mostly it’s all plug and play, no need to install anything. With this spring/autumn releases all the AMD GPUs should work out of the box with good performance.
I haven’t tried BMS 4.35 under Windows, but 4.34 was about on par or maybe slightly faster when used with nine (D3D9 native linux implementation), DXVK should give close to native or better FPS too.I’m not sure about cougar (it maight need to load firmware under win), most of the other joysticks should be fine using js or evdev.
In most cases no need to fiddle with drivers etc… Basic axis remapping can be done with calibration tool for js driver (see Joystick section of HOWTO), but for BMS there’s little need to remap axis in the driver as all the mapping can be done in BMS UI, who cares what is the name of axis or button number, as long as it does what you want it to do.
If there’s some kind of exotic hardware xbox360 pad driver can be handy, 'tho I have never had a need to try it.I guess major hurdle right now would be display extraction, 'tho there was some app prototype written in python, also AL and voice command apps might be problematic.