BMS 4.35 on Linux / WINE
-
Quick question does anybody experience ocasional 2-5s freezes? Here it’s quite random: might happen once +10 minutes then two - three times in a row within 2 minutes.
Now i’m using Fedora 33 with GnomeShell/Wayland+Mesa+DXVK +Wine 6.0, my previous setup was KDE with Xorg, mesa/DXVK and wine 5.xx and I don’t remember such issues.
But so many things changed, different desktop environment and display server and wine version. -
Quick question does anybody experience ocasional 2-5s freezes? Here it’s quite random: might happen once +10 minutes then two - three times in a row within 2 minutes.
Now i’m using Fedora 33 with GnomeShell/Wayland+Mesa+DXVK +Wine 6.0, my previous setup was KDE with Xorg, mesa/DXVK and wine 5.xx and I don’t remember such issues.
But so many things changed, different desktop environment and display server and wine version.I don’t have freezes, but I haven’t started a campaign yet, so not fully tested the game. Does this happen no matter where are you flying? Maybe is a system issue and not game related.
-
Hi folks,
my BMS has stopped working on Mint 20 / wine 6.3 all of a sudden. It’s not related to U1, so I’m a bit short on ideas what could have caused this.
I’ve tried
o integrated desktop / no desktop
o emulating win7 and win10
o disabling the movie stuff (-nomovie is passed to the launcher anyway)but nothing has helped.
The launcher comes up fine, but as soon as I try to start the game I get this message:
0150:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0xf69e2
and BMS just quits. No “this program has stopped working”, no dumps, nothing.
Has anybody else seen this behaviour?
Thanks & all the best,
Uwe
-
Hi all,
I managed to fix the issue by downgrading to wine-5.5 as provided by the mint / ubuntu repos, then re-installing dxvk into the appropriate WINEPREFIX.
All the best,
Uwe
-
Could wine update break settings on BMS prefix? I’ve just tried wine 6.3 and had no problem with app launch. I did a quick dogfight/furball as a test, all worked fine, no crashes.
-
Can’t get BMS to launch on WINE 6.3 at all (see backtrace). I even tried with a clean prefix.
WINE seems to be the only Linux program that actually gets worse with every release. Opentrack output in IL-2 1946 is also broken, Dotnetfx can’t be installed unless forced, etc.
- Edit: 4.33 U1 also does not start.
-
Hmm, might be worth taking a look at distros patches applied to their respective wine packages.
-
I’ve now rolled Wine back as far as 5.22 step by step, but still can’t get BMS 4.35 and 4.33 to work. (At least WINE 6.2 has Opentrack output not being broken in IL-2 1946, so that’s what I’m using now.)
Could be some Windows components that are acting up, but I just don’t know which. This is what my WINE prefix has installed (using the names from winetricks):
dotnet48 (for the alternative launcher; requires forced installation, i.e. “winetricks –force dotnet48”)
dxvk
vcrun2003
vcrun2005
vcrun2008
vcrun2012
vcrun2013
vcrun2015
vcrun6sp6Not sure what elese could be relevant. Codecs maybe?
-
Just throwing it out there, its a bit harsh to blame wine for not working properly when you are trying to install real dotnet into it. Its not at all a supported configuration - stuff may work, but windows components suddenly not working is AFAIK not even considered a regression.
Normally when getting support for a wine crash, you’d start with providing the required information. There are instructions here: https://wiki.winehq.org/Wine_Developer%27s_Guide/Debugging_Wine#Crashes
The part that jumps out is where the backtrace is basically empty. Page fault on execute access… so its tried to go looking for the exe at memory location 0, and couldnt find it.
-
For the last few times I tried (and started messing with dxvk which results in a nice fps boost if it works), I didn’t have to install any addtional stuff in a clean WINEPREFIX to get BMS to work.
wine itself would download mono & gecko when installing Falcon 4.0 into the prefix (compact installation option), then running BMS setup and all was good to go. I’m using
“-window -nomovie”
as args for the launcher, I don’t know if this might help (also disabled the “play intro movie” in BMS’ setup I think). All the DX11 / 9 / 7 (for Falcon 4 :)) should be installed automatically.
Good news to hear that IL-2 is working, I enjoyed “Cliffs of Dover” for a while in win10 so it’d be nice to be able to run it natively on Linux, too, but I’m having issues with opentrack at the moment (it tracks in WINE when emulating a virtual desktop, but BMS doesn’t recognise it for some reason).
All the best,
Uwe
-
Just throwing it out there, its a bit harsh to blame wine for not working properly when you are trying to install real dotnet into it. Its not at all a supported configuration - stuff may work, but windows components suddenly not working is AFAIK not even considered a regression.
DotNet is not required by BMS itself, only by the alternative launcher. I wouldn’t even install it either if Mono supported whatever classesthe launcher uses, but it doesn’t (yet).
Having to force-install DotNet is still marked as a bug in WINE’s bug tracker. If the WINE devs really do not want to have users install proprietary Windows runtimes, they should explicitly state so.
Normally when getting support for a wine crash, you’d start with providing the required information. There are instructions here: https://wiki.winehq.org/Wine_Developer%27s_Guide/Debugging_Wine#Crashes
The part that jumps out is where the backtrace is basically empty. Page fault on execute access… so its tried to go looking for the exe at memory location 0, and couldnt find it.
I have too little information for a comprehensive bug report. As you said, that backtrace is pointing nowhere and I don’t have enough usage history of 4.35 in WINE (this was my first attempt to use it) to provide more than “Doesn’t work, but I don’t know how and when it broke”.
Somebody who is a frequent BMS user and ideally has the knowledge and time to bisect recent WINE builds would be much better suited to report it and provide a constant information feed.
Maybe it also isn’t cause by WINE in the first place, but by some GPU driver or DXVK bug (unlkely though as not even the main menu runs).Funnily enough, the original F4 launches just fine (albeit without the intro movie).
Good news to hear that IL-2 is working, I enjoyed “Cliffs of Dover” for a while in win10 so it’d be nice to be able to run it natively on Linux, too, but I’m having issues with opentrack at the moment (it tracks in WINE when emulating a virtual desktop, but BMS doesn’t recognise it for some reason).
Opentrack occasionally needs to be recompiled after major WINE or OpenCV releases, but in IL-2’s case, that did not help.
-
My BMS prefix is quite plain and clean. There are just few extra libs added via Winetricks:
- d3dcompiler_43
- d3dx9
- DXVK (although I’ve recently symlinked dlls to ones installed systemwide from official Fedora repos)
Things that are Installed in this prefix are: Falcon4 and FalconBMS, both on separate folder mapped as drive E:
Nothing else, no opentrack (yet), no other programs, stock settings with exception of adding extra drives.packages:
wine 6.3-1
wine-dxvk 1.8.1I had similar issue with wine5 and IL21946, as it turned out there was an nondefault option checked from winecfg/staging that caused crashes.
I know you guys most likely tried this, but try with clean new prefix, without any extra configuration added, just to be sure. -
DotNet is not required by BMS itself, only by the alternative launcher. I wouldn’t even install it either if Mono supported whatever classesthe launcher uses, but it doesn’t (yet).
Having to force-install DotNet is still marked as a bug in WINE’s bug tracker. If the WINE devs really do not want to have users install proprietary Windows runtimes, they should explicitly state so.
You may like to refresh on the FAQs where they highlight that there is no support for 64 bit programs on native dotnet: https://wiki.winehq.org/FAQ#Does_Wine_support_.NET.3F_Should_I_install_native_.NET_in_Wine.3F
Strictly speaking, https://bugs.winehq.org/show_bug.cgi?id=49897 relates to winetricks hanging on the install process. You should be able to install dotnet - its not advisable and programs relying on it are not supported, but you should be able to install it and if the installer fails, its a regression and needs to be fixed.
I would recommend filing a bug report at winehq against the alternative launcher not working on mono. The sooner its known about, the sooner it could be fixed.
I have too little information for a comprehensive bug report. As you said, that backtrace is pointing nowhere and I don’t have enough usage history of 4.35 in WINE (this was my first attempt to use it) to provide more than “Doesn’t work, but I don’t know how and when it broke”.
Id suggest that the next stage would be gathering more information for a comprehensive bug report. I quote from the link I sent you:
rerun Wine with the WINEDEBUG=+relay environment variable set
Backtraces dont point nowhere for no reason.
Still, if you dont have the time, thats fair enough. Perhaps just dont be surprised if no one else has the time to fix it for you, either.
-
Just gave U2 a quick spin on Linux Mint 20 and wine-5.5, apparently it’s working just fine. FPS are great, sound & controller settings work nicely as well.
All the best,
Uwe
-
Same here with Ubuntu 20.04 and Lutris.
Performance has clearly improved and now I can have shadows activated having almost the same FPS than with U1 without them. -
Just wondering: are you running the vulkan wrappers? They do a tremendous job of improving the FPS on Linux.
Cheers, Uwe
-
Yes, I’m using it. Haven’t tried without it, though. Will do next time.
-
Really curious to see how this is compared to windows… did any of you do this A/B test?
-
I did testing on same hardware, Linux vs Windows with 4.35.1 a while back. I think I posted the results somewhere on here, but from what I remember it was roughly 20fps higher under Linux with dxvk. Not tried 4.35.2 yet.
-
Hi folks,
is it somehow possible on Linux / WINE to reorder the hardware devices so they get picked up by BMS running under WINE exactly how they appear on Windows? I know about devicesorting.txt, but I’d love to have the DirectX button numbers match the ones I’m seeing on Windows so that keyfiles become compatible between operating systems.
For instance on win10 the Warthog HOTAS starts at button Zero (I’m seeing “1” in BMS’ setup screen when pressing the trigger), however on Linux this turns into button “33”. In fact I’m not seeing any button number below 33 on any device connected to the gaming machine.
Thanks in advance & all the best,
Uwe