BeamMP Run On Linux Guide 2025

scrollcaps · 12 November 2024 04:59

12/11/2024 Major Update For The BeamMP Launcher

A mere 6 hours after creating this post a major update dropped for the BeamMP launcher providing full native support for Linux, but only for the uncompiled version.

BeamMP now hosts an official Linux guide

For Steam Deck users

Before doing this you need to enter desktop mode, this can be done by holding the power button and selecting “Switch to Desktop”.

For read/write access, run sudo steamos-readonly disable in the terminal. You first need to set a user password, do this by running the passwd, I’m not sure how SteamOS handles users, this could be a login password so DON’T FORGET IT! It’s worth mentioning that any changes to the file system will be wiped in the next SteamOS update, this is of little concern as once the launcher is compiled you don’t need the building tools (until the next major BeamMP update).

The general guide starts here

First you need to clone and set up the vcpkg dependency manager. Open the terminal and type these commands

git clone https://github.com/microsoft/vcpkg.git
cd vcpkg && ./bootstrap-vcpkg.sh --disableMetrics

Then run this command

export VCPKG_ROOT="~/vcpkg"
export PATH=$VCPKG_ROOT:$PATH

Now navigate back to the home folder

cd ~

Next up, we need to install some dependencies

Run ONLY the command for your distro or derivative.
Debian sudo apt install build-essential cmake git
Fedora sudo dnf group install development-tools git cmake
Arch sudo pacman -S base-devel git cmake
openSUSE sudo zypper in -t pattern devel-basis
Void sudo xbps-install -Rs base-devel git cmake
SteamOS sudo pacman -S base-devel git cmake linux-api-headers glibc libconfig

With all that done, we get to the fun stuff where you see lots of test fly up the terminal window like a real cool developer.

Using the terminal clone the BeamMP launcher repo

git clone --recurse-submodules https://github.com/BeamMP/BeamMP-Launcher.git

Navigate into the directory

cd BeamMP-Launcher

Then run this script

cmake -DCMAKE_BUILD_TYPE=Release . -B bin -DCMAKE_TOOLCHAIN_FILE="~/vcpkg/scripts/buildsystems/vcpkg.cmake" -DVCPKG_TARGET_TRIPLET=x64-linux

If (in game) you get the bug launcher-can-only-connect-to-a-server-once then omit
-DCMAKE_BUILD_TYPE=Release from the above command, this will download the debug version that doesn’t contain this bug

If all done correctly you should now see the glorious sight of mesmerizing text flying high up the terminal windows. If you installed the above mentioned packages and you get an error, then I don’t know what you’re missing. Double check the commands you’re using before requesting help here.

At last the final command (make sure terminal is in the BeamMP-Launcher directory).

cmake --build bin --parallel --config Release

One cool wall of text later and congratulations! you’ve successfully compiled the BeamMP launcher. It is located in ~/BeamMP-Launcher/bin/

This launcher can be run from anywhere and the folder of cache that it creates (also used for mods) is located at ~/.local/share/BeamNG.drive/

I hope this helps. Enjoy!

This was initially a support query and so the earliest comments will not necessarily reflect this post. I preserved post #12 because several posts already link to it.

sapphic420 · 12 November 2024 12:32

thats brilliant! rename the game’s launcher to the beammp launcher which then launches the BeamNG.drive.x64.exe! how did i not think of that when i was tinkering with the steam tinkerer! /s

i could be wrong, but if running via wine/proton, choosing the vulkan renderer is redundant, because it will run in vulkan anyway, no matter what option you choose!

also,

DuckBoi321 · 12 November 2024 22:25

there is a tutorial that works perfectly fine for Ubuntu 24.04 even though its meant for 22.04 I’ve used it SO many times to make servers for people who ask
linux and Windows tutorial
just follow it step by step and it should work ask me anything if it doesn’t
the dude who made it is super easy to follow and is very underrated

sapphic420 · 14 November 2024 11:04

thank you very much for sharing this information that’s literally not found anywhere else here!

but as many people will come to try this out natively, there will be questions, and i, too, have one!how does one clear cache on a native build, when there is no game launcher for it? the launcher, afaik, can only be run via wine/proton/lutris/etc and it only clears its cache for its own prefix, not for the native linux binary which has its separate user folder! there is no mention of this neither in beamng’s documentation nor on the forums!

tl;dr ~/.local/share/BeamNG.drive/0.xx/temp/

^ clears the cache ^

scrollcaps · 14 November 2024 13:01

All that matters is that BeamMP/NG doesn’t see a cache folder so it generates a new one, this can be done in one of three ways as I’ve mentioned above.

This is summery contains outdated information

Summary

The clear cache tool just renames the cache folder to 0.33.backup or something similar, there is no fancy cherry-picking going on.

sapphic420 · 14 November 2024 16:17

you are incorrect . when you press “deep cache cleaning”, it creates a backup of your latest version user folder inside itself called backups/version.pre.0.0xx.x.x/date which is coincidentally in the path of your mods, configs and settings that you are suggesting to delete, move or rename just to CLEAR CACHE. it is then checking for file hash integrity and any misplaced files, which are moved into unknown_files_user_folder. finally, it then proceeds to clear the temp-orary folder, which is the cache itself (where you have confused it for the whole user folder). were you to rename, move or delete your user folder itself, as you correctly mentioned, the game will see it as an invalid user folder, and create a new one as if you had a fresh install. it would then make no sense to overwrite your old renamed user folder with a fresh one, if your problems still persist AFTER having cleared the cache. once again: it does not rename your user folder, it backs some of its contents up, excluding (!) the mods folder, btw. you dont have to misplace a whole user folder just to clear cache, as you mentioned in both of your replies… i, too, sometimes would rather reinstall the whole game than fix one specific problem! and thusly i have discovered the answer to my own question, as shrimple as that
i suggest you should rephrase your message accordingly

scrollcaps · 14 November 2024 17:31

I’m sorry, I didn’t use the tool in a long time and all the while its had several changes.

The core and focus of my replay though answered your initial question (location of cache) and you indeed explained very well how the tool now works. Let’s not lose focus here, as the post was initially made to help users run BeamMP on Linux.

sapphic420 · 17 November 2024 16:52

a few notes about linux and STEAM DECK:

auto update is NOT implemented on linux. please update manually ASAP as updates contain security patches.

tl;dr read this

ALL and ANY these instructions work ONLY in vanilla unmodified bash shell, cos POSIX!!!. MAYBE zsh
vcpkg as a package is not necessary! in MY case, i had to clone it to get its vcpkg.cmake toolchain, without setting any environment variables!
we compile a DYNAMICALLY linked binary called BeamMP-Launcher. i.e. it DOES NOT come with its baked (built-in) dependancies or libraries, meaning it WILL NOT work on other computers, were you to share this file. unfortunately, there are no instructions on building/compiling statically. AT BEST, perhaps an AppImage or a Flatpak package is in the works. (EDIT: there is an available launcher PR in nixpkgs (NixOS) in master)
using wayland? are you experiencing screen blinking or flickering (NOT tearing)?

…

so, uh, STEAM DECK?! if you wanna do this on a Steam Deck and youre on SteamOS, AND you use it as a “portable linux daily machine” like me - tl;dr is DO NOT ATTEMPT TO DO THIS ON STEAMOS. for all of you normal people who DONT hack the ■■■■ out of a Steam Deck - do not even BOTHER. because you will simply brick it. and then you will not have your gaming handheld device anymore. you will cry and RMA it because you will be unable to reimage it by yourself. BUT FOR THOSE WHO AT LEAST KNOW 1 SCRIPTING LANGUAGE - installing the base-devel package on SteamOS and any other dependency it requires to compile the BeamMP-Launcher binary (which, by the way, cannot be renamed, it’s hardcoded to rename itself back to BeamMP-Launcher, hope you found this cute little factoid interesting) - WILL BE FUTILE since SteamOS is a ■■■■■■ up read-only distro where YOU will have to make your ENTIRE FILESYSTEM writable/editable to install ANYTHING that isn’t a flatpak (like your chromium or ProtonUpQt, for example), okay, let alone building a native beamMP client (yes, surprise, SteamOS doesnt come with compile tools nor does it even come with a user (you have/had to set the user and password yourself!), cos it’s considered a “gaming distro” and not a workstation for you to tinker with, or so they say “uhm actually it’s for security reasons, so that you dont install malware into your root filesystem”…

ohh sod it, i made a guide for y’all how to bypass that ■■■■ alright very difficult stuff below. as difficult as a 10000 piece puzzle. or a frame perfect trick. or beating Rain World. or trying to survive on the nether highways on 2b. or hitting a 260 unit longjump in cs 1.6. ah, whatever, you’ve literally havent done any of that

EDIT: below, is an unedited mess. tl;dr is you should ditch steamOS for another distro. just DO IT. because eventually you will need a container (e.g. podman) to use outdated (therefore, dangerous) mozilla/cloudflare SSL certificates which were removed this april. without them, you will NOT be able to play beamMP, at all. it is the SAFEST way. the unsafest way would be to downgrade them like a ■■■■■■■ idiot. preferrably, you should be an experienced user for this…

SO, ya wish to proceed with installing and compiling, as well as getting one step closer to using arch btw (kill me ), huh? HUUHHH??! very well. understand these risks: YOU THEN, HEREBY, UNDERSTAND ALL OF THE POSSIBLE AND UNFATHOMABLE RISKS OF BRICKING YOUR ONE AND ONLY STEAM DECK!
BEFORE YOU BEGIN THOUGH – TRY NOT TO ERASE YOUR STEAM DECK’S INTERNAL DRIVE, it is very difficult to update your steam deck’s firmware OUTSIDE of steamOS, though i say this on another system and i havent updated it in years. OH, that is, haha, unless you dont want to actually install anything. yeah, then just scroll to the bottom until you see the word “HOWEVER”…
–consider these requirements – we will be turning your steam deck into a stationary desktop PC (uhmm… actually it IS already a PC! ):
(1). get/buy an external (!) SSD (& a cable to connect it with - preferrably usb-c to usb-a and/or an adapter) AND a dock station AND/OR a usb-hub for your Steam Deck (w/ at least 3-5 USB-A ports for the periphery and general quality of life, 1 USB-C PD for charging, OPTIONALLY with a built-in NVMe for an SSD - though not recommended); also, as mentioned before, get a USB-C to USB-A adapter in case you are going periphery-less by using only the track pads and the on-screen touch keyboard or if you’re controlling your steam deck remotely via SSH, but be aware that you will not be able to charge your steam deck simultaneously (EDIT: add "usbcore.autosuspend=-1" to the kernel parameters to disable USB power management), VERY OPTIONALLY even an HDMI cable and some fancy curved 4k monitor if you cant stand the smol 720p60fps LCD screen, you casual.
–bit of trivia: steamOS, unlike most other distro’s, is imaged as is, it occupies your WHOLE drive where it is installed on, it is impossible to shrink its partitions during AND/OR after the installation, because its recovery image is not your standard calamares gui, not to mention that the image itself is not even a live .iso. to make matters worse, steamOS reimages itself after an update anyway - all the EFI entries, for example, will be gone, therefore it is impossible to install anything alongside it on the same drive, which is why we’re getting a secondary system to tinker with on an external drive in the first place! if you DID manage to find a way to dual boot with steamOS on the same drive and not lose the image merely after an update, let us know! you’d be the first person!
–also, if you’re wondering “why SSD and not a microSD - its so much easier!!!” - you can go ahead and close this tab. of course i thought about this. but i thought this was UNIVERSALLY ■■■■■■■ KNOWN that they’re extremely ■■■■■■■ slow (10x), they’re a piece of ■■■■, unreliable as ■■■■ and fragile (these last for a year AT BEST - ever owned a professional camera?). seriously, just shut the ■■■■ up and get an SSD. ■■■■, thank you. anyway…
(2). connect keyboard (and optionally A singular (1) mouse IF there will be space after the second step - ■■■■, i really have to mention the quantity of mice to connect to these people… yeah, connect ■■■■■■■ 6.9 mice, you ■■■■■■■■),
– of course, at this point, if you know how to and/or haven’t already, use SSH.
–*WARNING: hot swapping (aka hot plugging) while connected to a dock station could temporarily disable ALL OF YOUR PERIPHERY, INCLUDING BUT NOT LIMITED TO SSDS!!! this is enough to potentially cause corruption and loss of data. DO NOT disconnect, connect or reconnect ANYTHING while installing, burning or otherwise making ANY changes to your drives. this includes (un)-plugging the charger! EDIT: ■■■■. as mentioned previously, add "usbcore.autosuspend=-1" to kernel parameters and you’re sorted
(3). connect usb flash drive (leaving the last remaining port for the keyboard, so use the track pad as mouse. if your distro of choice does not include trackpad/touchscreen drivers in live mode, rest in pepperoni. guess you’re gonna have to uno reverse it by plugging only the mouse and using the on-screen keyboard. if you dont even have an on-screen keyboard, then it’s time for you to learn how to connect to your steam deck via SSH and remote control that ■■■■■),
(4). burn your .iso of choice (see list below) onto said flash drive (if you only have one flash drive but also want to copy some other files, you can use Ventoy, that can both be used as a boot loader with different .iso’s and as a storage device); hopefully you DO know how to do things by now - im not gonna explain everything!
(5). connect your external (!) SSD (unless your dock/hub has a built-in one),
(6). shutdown,
(7). when it is off, keep holding the “volume down ‘–’” button and press the power button ONCE (1 time) until it beeps,
(8). when it beeps, go to boot manager and pick your new bootable drive with your live .iso,
(9). proceed with installation onto your external (!) drive - do not confuse your internal steam deck’s nvme drive with your steamOS on it with your internal nvme drive of a usb hub! just follow your distro’s installation instructions…
–DO NOT accidentally or deliberately rewrite/wipe steamOS in the installation process, it is needed for firmware updates!!! (at least). EDIT: no one is stopping you from deleting it, but you might get a random zenbleed CVE, if you even care what that is.
*ALSO because it’s mildly infuriating getting it back in case you brick your steam deck completely. here’s why (READ THIS IF YOU ■■■■■■ UP, COMPLETELY BRICKED YOUR STEAM DECK, CRYING AND PANICKING): now that you probably understand that steamOS has a very aggressive approach to imaging, it gets even worse than that - its recovery image block size is 128 megabytes (link to instructions), which means you HAVE to use an external drive like an SSD or a VERY FAST (and expensive!) flash drive that you probably dont have or want to sacrifice, otherwise it’ll basically freeze or not boot at all… thankfully and hopefully by step 1 you should have already caught 'em all. now, for this you have to use another computer. once you’ve burnt the recovery steamOS image onto your external drive, plug that in to your SD and boot off of it, then choose what recovery option suits best for you - INSTALL ONTO YOUR INTERNAL STEAM DECK’S DRIVE! once you got your steamOS back, fancy trying all this again? i thought so, let’s get back into it:
(10). now you should (hopefully) have two working systems to choose from in the boot menu: SteamOS and your desired distro or its linux boot loader! (unless you actually deleted steamOS, well, you already know what you’re doing)
(PSA: oh, by the way, haha, say goodbye to your beloved “gaming mode” because that ■■■■ just wont work with beamNG and beamMP. first and foremost, native beamNG is an X11 application, it was compiled EXCLUSIVELY for it. probably a crazy shocker if you didnt know this factoid. it basically means that this game only works in 1% of cases, because LITERALLY EVERYTHING ELSE is NOT using deprecated, unsafe and outdated technology, so doesnt gaming mode, which uses wayland window system… oh, how i wanna see the look on your face when you’re gonna be all like “b-b-b-but what’s all this!!! it’s j-j-just 1 pixel… why do i get a black screen??? somebody heeeelp!!!” second, gaming mode (gamescope) wont work with beamMP, be it via proton or run natively, because… of the aforementioned problem. to learn more, read this and write down any differences. do you see it? one is a proper window system written from scratch, other is a legacy server (!) that has no security)
(11). and finally, YOU ■■■■■■■ DID IT!!! YOU’RE WINNER!!! congratu-■■■■■■■-lations!!! you’re amazing and not a lazy piece of ■■■■■■■ ■■■■, yay and hooray and ■■■■. ahh, right, anyway, you may now proceed with the rest of the guide to compile this ■■■■■■■ beamMP launcher. oh and dont forget what i said literally in the first paragraph of this long ■■■ post though haha
here’s some out-of-the-box Steam Deck distro’s that worked for me (not in order, im just separating the links with numbers. anyway, my fav is definitely NixOS. its just soooo ■■■■■■■ gay, i love it. i think you should try it if you love spending over 6 hours doing nothing, like following these instructions):
(1) CachyOS Handheld Edition (arch, optimised 4 gamers, blah blah blah),
(2) Bazzite (fedora, IMMUTABLE! can update firmware like steamOS (?), for epic gaymers! – also see Nobara, from the creator of Proton GE),
(3) EndeavourOS (at least it’s not Manjaro, copium… has steam deck drivers, obvs, its arch),
(4) NixOS (NON-FHS, IMMUTABLE, ATOMIC!!! but so worth it. you write your own system (NOT from scratch!). install services, daemons and packages with 1 line. not even joking. you install steam and mesa with 1 line, like a bundle. all the cool girls use nixos. and there is a lot of steam deck stuff, out of the box or not).
(5) OR this assortment of ■■■■ – NOTE: if you wanna install windows – get the windows 10 LTSC edition. no, srsly, you should know by now where the technology is going - down the ■■■■■■■ ■■■■■■■. so i propose you get all your anti-spyware and anti-bloatware nukes ready, because there is a ■■■■■■■ war out there, if you dare to install win 11. it doesnt ■■■■■■■ matter what kind of hardware you got, when the system is going to take it from you anyway. anyway, nevertheless, vulkan on linux is faster than vulkan on windows, period. BUT beamNG on windows via directx11 is infinitely faster than running beamNG via proton or wine, which some of yall STILL do for some ■■■■■■■ reason… trust, native linux vulkan experience - better than anything ■■■■■■■ else. just remember to enable the shader pre-caching in steam download options… because without it, vulkan will be completely useless otherwise. and dont get me started on macos, steam deck will never be a hackintosh. if you’re that masochistic, try nixos (see above).
HOWEVER!!! IF YOU ARE UNABLE TO INSTALL A SECOND SYSTEM, THEN RISK IT FOR THE BISCUIT EVEN MORE WITH THESE GUIDES THAT (TEMPORARILY) MODIFY STEAMOS – you just need to create a user:
(1) this simple guide,
(2) this github SteamOS issue,
(3) this reddit tutorial,
(4) this userspace guide.

i should rewrite this someday… maybe?

scrollcaps · 18 November 2024 05:47

12/11/2024 Major Update For The BeamMP Launcher

A mere 6 hours after creating this post a major update dropped for the BeamMP launcher providing full native support for Linux, but only for the uncompiled version.

BeamMP now hosts an official Linux guide

For Steam Deck users

Before doing this you need to enter desktop mode, this can be done by holding the power button and selecting “Switch to Desktop”.

For read/write access, run sudo steamos-readonly disable in the terminal. You first need to set a user password, do this by running the passwd, I’m not sure how SteamOS handles users, this could be a login password so DON’T FORGET IT! It’s worth mentioning that any changes to the file system will be wiped in the next SteamOS update, this is of little concern as once the launcher is compiled you don’t need the building tools (until the next major BeamMP update).

The general guide starts here

First you need to clone and set up the vcpkg dependency manager. Open the terminal and type these commands

git clone https://github.com/microsoft/vcpkg.git
cd vcpkg && ./bootstrap-vcpkg.sh --disableMetrics

Then run this command

export VCPKG_ROOT="~/vcpkg"
export PATH=$VCPKG_ROOT:$PATH

Now navigate back to the home folder

cd ~

Next up, we need to install some dependencies

Run ONLY the command for your distro or derivative.
Debian sudo apt install build-essential cmake git
Fedora sudo dnf group install development-tools git cmake
Arch sudo pacman -S base-devel git cmake
openSUSE sudo zypper in -t pattern devel-basis
Void sudo xbps-install -Rs base-devel git cmake
SteamOS sudo pacman -S base-devel git cmake linux-api-headers glibc libconfig

With all that done, we get to the fun stuff where you see lots of test fly up the terminal window like a real cool developer.

Using the terminal clone the BeamMP launcher repo

git clone --recurse-submodules https://github.com/BeamMP/BeamMP-Launcher.git

Navigate into the directory

cd BeamMP-Launcher

Then run this script

cmake -DCMAKE_BUILD_TYPE=Release . -B bin -DCMAKE_TOOLCHAIN_FILE="~/vcpkg/scripts/buildsystems/vcpkg.cmake" -DVCPKG_TARGET_TRIPLET=x64-linux

If (in game) you get the bug launcher-can-only-connect-to-a-server-once then omit
-DCMAKE_BUILD_TYPE=Release from the above command, this will download the debug version that doesn’t contain this bug

If all done correctly you should now see the glorious sight of mesmerizing text flying high up the terminal windows. If you installed the above mentioned packages and you get an error, then I don’t know what you’re missing. Double check the commands you’re using before requesting help here.

At last the final command (make sure terminal is in the BeamMP-Launcher directory).

cmake --build bin --parallel --config Release

One cool wall of text later and congratulations! you’ve successfully compiled the BeamMP launcher. It is located in ~/BeamMP-Launcher/bin/

This launcher can be run from anywhere and the folder of cache that it creates (also used for mods) is located at ~/.local/share/BeamNG.drive/

I hope this helps. Enjoy!

This was initially a support query and so the earliest comments will not necessarily reflect this post. I preserved post #12 because several posts already link to it.

Fairplex · 19 November 2024 12:24

I compiled the BeamMP executable but the game crashes on launch. The steam version (normal and vulkan) works fine so I dont know where is the problem with this BeamMP linux version.

This is the beamMP logs:

[19/11/2024 13:26:51] [INFO] Mod caching directory: ./Resources
[19/11/2024 13:26:51] [INFO] BeamMP Launcher v2.3.2
[19/11/2024 13:26:52] [INFO] Launcher version is up to date
[19/11/2024 13:26:52] [INFO] IMPORTANT: You MUST keep this window open to play BeamMP!
[19/11/2024 13:26:52] [INFO] Game Version : 0.33.3.0
[19/11/2024 13:26:52] [INFO] Game user path: /home/fairplex/.local/share/BeamNG.drive/0.33/
[19/11/2024 13:27:06] [ERROR] Game Closed! launcher closing soon
[fairplex@archlinux ~]$

OctopusCarDoor · 19 November 2024 12:28

@scrollcaps @sapphic420 I have moved this topic into the FAQ category. The FAQ category is locked so it will prevent this post from getting lost in the sea of people asking us why they can’t log in while already being logged in.

sapphic420 · 19 November 2024 14:34

okay, very interesting, what does it say in the game crash logs in your user folder and is it possible if you could just manually ./BeamNG.drive.x64 and see its output in the terminal?

OctopusCarDoor · 19 November 2024 14:35

Moved us back to support because being in the FAQ requires reply approvals.

OctopusCarDoor · 19 November 2024 14:35

There we go, that’s better

Fairplex · 19 November 2024 20:31

After testing further, the issue seems to be that the BeamMP launcher starts the Vulkan version of the game, which dosn’t work correctly under wayland.

Is there a way to change the default version of BeamMP?

sapphic420 · 19 November 2024 23:34

ohhhhhhhhhhhh, right… how could i forget about this…

in Steam Deck’s gaming mode, which is using bare wayland (which is a window system that is a SUCCESSOR to X11!.. well, maybe it’s not so “barebones” as it is literally always in its exclusive fullscreen mode governed by the gamescope compositor - but thats besides the point!!), were you to try launching the NATIVE BeamNG binary from
~/.local/share/Steam/steamapps/common/BeamNG.drive/BinLinux/BeamNG.drive.x64
it then hilariously launches it in 1x1 pixel resolution. but THEN in its DESKTOP mode, aka the normalwindowmodethateverybodyknows, which is KDE (a popular desktop environment) under xwayland, that can run both X11 and wayland apps, beamNG DOES (!) work… except for the horrible screen flickering (epilepsy warning!), not to be confused with screen tearing, which can be fixed with a compositor (unless you are already running on wayland, which IS a compositor) - screen flickering (blinking) is a FEATURE. that is how it works!

■■■■! to clarify, as i mentioned previously (good reading, btw!), one must understand the differences between X11 and wayland. so, a “compositor” in X11, is an EXTERNAL, additional process. it “helps” with screen tearing. if you are running a xorg session, get picom (github) or something. a WAYLAND compositor, is a complete FULL session, like labwc (github). in SOME cases though, for example, with hyprland, you can apply a window rule to a specific application (which x11 compositors CANNOT do by design, they always composite the entire server/monitors) or allow tearing globally. so, when wayland runs an xwayland application which is tearing, you only have 1 option here: turn on vertical synchronisation. if THAT doesnt help - it is really over. the application was most likely compiled exclusively for xorg, and there is nothing you can do, but switch to xorg (x11) session yourself. i recommend leftwm (github). wayland by design renders x11 frames like this - with black screen buffering. and that is the bottom line.

…

anyway. if you are unable or cannot run beamMP/beamNG NATIVELY (via launching the binary), here are some miscellaneous links to running via wine/proton/STL/lutris. i do not recommend this! go fully native OR ■■■■ ALL. its either all or nothing, dont even bother with emulation!

addendum:

alternatively, SCREAM AT THE BEAMNG DEVELOPERS! directly to their emails from the contact list. scream, scream! you MUST scream because x11 MUST. ■■■■■■■. DIE. nobody should ever make games for x11 in this century. EVER. why the ■■■■ would ANYONE be willing to compile anything exclusively for xorg, a ■■■■■■■ game???! mind you, xorg is a piece of shitware which has a full network stack, a SERVER, all of whihc has 0 security, because EVERY SINGLE applcation keylogs your every input.

wayland or ■■■■■■■ NOTHING.

scrollcaps · 20 November 2024 06:47

This isn’t a fortune 500 company, no need to take the piss. Wayland itself still has many bugs so I can’t blame them for focusing on other things and waiting for it to fully bake. Yes the Steam Deck uses Wayland, but that’s not used as a desktop, it has a lot stripped out of it. You can use Wayland like a Windows user (little to no modifications) and probably get by mostly fine, but that’s not the point, try get your hands dirty and Wayland will be dirty.

Fairplex · 20 November 2024 11:27

Ok I understand your frustation. But we know that the game works fine if:

Ran using Direct3D, on both X11 and Wayland
Ran using Vulkan, on X11 only

So as we have to compile BeamMP ourself from the source, there should be a way to tell BeamMP to run the game with Direct3D instead of Vulkan which is experimental. To me its more like a mistake to make Vulkan the default version of BeamMP launcher.

Luthenium · 20 November 2024 13:50

Everything is laid out in detail since I had to solve the exact same issue. Running DirectX BeamNG on Linux without Proton/Wine is sadly impossible.

Please check my topic if you need help running BeamMP under DirectX.

SoIAmGonnaCrash · 28 November 2024 04:29

I’m new here, but I ran into some difficulties.
I am on PopOS (Debian based), with a fresh native steam install of BeamNG. I installed all of the dependencies, and attempted the instillation multiple times.
Terminal throws errors during the final script (cmake --build bin --parallel --config Release). Here are the last few lines:

[ 94%] Building CXX object CMakeFiles/Launcher.dir/src/main.cpp.o
/home/[USER]/BeamMP-Launcher/src/main.cpp: In function ‘int main(int, const char**)’:
/home/[USER]/BeamMP-Launcher/src/main.cpp:31:11: warning: ignoring return value of ‘int system(const char*)’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
31 | system(“clear”);
| ^~~
/home/[USER]/BeamMP-Launcher/src/Startup.cpp: In function ‘void ReLaunch()’:
/home/[USER]/BeamMP-Launcher/src/Startup.cpp:131:11: warning: ignoring return value of ‘int system(const char*)’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
131 | system(“clear”);
| ^~~
[100%] Linking CXX executable BeamMP-Launcher
/usr/bin/ld: cannot find -lssl: No such file or directory
/usr/bin/ld: cannot find -lcrypto: No such file or directory
/usr/bin/ld: cannot find -lws2_32: No such file or directory
/usr/bin/ld: cannot find -lssp: No such file or directory
/usr/bin/ld: cannot find -lcrypt32: No such file or directory
collect2: error: ld returned 1 exit status
gmake[2]: *** [CMakeFiles/Launcher.dir/build.make:341: BeamMP-Launcher] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:83: CMakeFiles/Launcher.dir/all] Error 2
gmake: *** [Makefile:91: all] Error 2

I assume this is supposed to generate an executable (x64) in BeamMP-Launcher/bin, but no such file appears.
I really have no idea what happened, I’m a total newbie with this. Any help would be appreciated.