BeamMP/BeamMP-Launcher

[Feature Request] Interact with game files properly on Proton or Linux

Gideon-Felt opened this issue · 9 comments

Is your feature request related to a problem? Please describe.
I may be able to install BeamMP on Proton or Wine. Still, upon launch, the terminal prompt goes into a blipping loop and says something about running on Linux/Proton and unable to find the game files, but says that it patched 100% which is obviously false.

Describe the solution you'd like
Enable at least with proton for the Patcher/Launcher to locate the game files in proton, as an alternative game location.

Describe alternatives you've considered
I wouldn't think a Linux specific launcher would be necessary, but that could be a thing, though is unreasonable, since the game is built for Windows and runs perfectly on Proton, so the alternative game files location would be the better solution since BeamMP installs and runs fine under proton, it's just incapable of finding the files to patch.

Additional context
This would also be a solution for Steam Deck players, where the game runs quite well.

Hi! For the next version of the launcher, we are trying to make linux work out of the box. Right now, the solution is to run the launcher in the wineprefix of the game, that usually works okay. It then needs a few more little registry patches, sometimes.

Im definitely onboard with this request!

Right now it breaks when running with Steam installed in wine.
I have to write a script as a workaound

@echo off
set USER=
/path/to/beammp.exe

Right now it breaks when running with Steam installed in wine. I have to write a script as a workaound

@echo off
set USER=
/path/to/beammp.exe

This workaround will make BeamMP-Launcher thinking that is is not running on wine and skip LinuxPatch() function

if (result != ERROR_SUCCESS || getenv("USER") == nullptr)return;

I was able to make it work on Linux Steam, with proton, by patching the registry myself.

The launcher should, if it can detect being in wine/proton, simply prompt the user to put in the paths. Anyone on linux can probably figure them out, and no registry is necessary.

+1 on giving users the option to specify their own paths and/or to manually override the automatic linux-specific behaviors. I just installed the game + BeamMP on a Mac via CrossOver and this was the only thing preventing the install from being as seamless as it would have been on a Windows machine.

If the launcher hadn't tried to do anything special at all and instead just opted to do everything as if it were running on a real Windows machine, this would not have been an issue. (Thank you GreatHaop for the USER-variable tip.)

paths in config is implemented in V3 branch, to be refined as more testing is conducted :)

Note: I do not want to close any issues that are "fixed" in V3, just in case there is some additional behaviour requested down the line until V3 is ready to be released, thank you all for the valuable comments