This is what the most recent log file looks like.
its a silly idea to screenshot logs that other people in the future cannot search by keywords, because a screenshot is not text and cant be queried in a search engineā¦ even IF discourse (this forum) doesnt allow to attach files.
please use a text pasting service, e.g. https://pastebin.com/ to paste the LATEST beamNG log called beamng.log, NOT beamng.123.log, in its ENTIRETY. you can set it to be temporary or hidden. then, paste the link to it here. the most important information is most likely just before the crash.
if nothing interesting is in the game logs, well, check dmesg and journalctl, just to be really sure its not a hardware issue. look for big scary red walls of text. and i dont mean |E|Steam| Could not initialize - Error code 1 - this can be completely ignored, because we are (most likely) launching a native binary, which is outside of steam play features. i have it too!
that is a bit of a conundrum. well, unfortunately, because i am on a FHS non-compliant AND kinda immutable but atomic system myself (non-FHS in a sense that it is a container by itself, so - double entropy, and immutable in a way that it just allows for rollbacksā¦ long story short, i DO have sudo and write permissions on the filesystem 
), i am unable to just simply āexecute a binaryā, so i have to do everything in another container. sort of a similar situation, but we both have to use container images sometimes. because of this, i have no experience of launching binaries outside of podman and i cant help you with this, im sorry. i recommend you should stick to compiling AND launching beamMP AND beamNG via podman + distrobox, which works for me.
just to be clear, i mean dynamically linked binaries. of course, i can still run linux native games outside of a container, but not literal binaries or executable files. just a quick reminder: steam is an FHS, which could give a few clues: perhaps it doesnt crash when BeamMP-Launcher is run via steam-run?
i suppose since you are compiling beamMP for native use, does that mean that you are also running beamNG natively too? so, does BeamMP-Launcher run BeamNG.drive.x64? NOT PROTON? NOT WINE? just to double check. beamMP should launch the native binary by default anywayā¦
yeahā¦ perhaps i should edit my ātutorialā, somewhere up there, to remove bazzite from the list. ive only heard of it as a nice steamOS alternative suitable for handhelds. i didnt know they literally copy the immutability of steamOS, but oh, wellā¦
(optional) - so, about permissions. DISCLAIMER: i have no idea how UID mapping or user namespacing works, nor how permissions in a container workā¦ but please check who is the UID/GID of ~/.local/share/containers AND ~/.local/share/containers/storage/volumes/<volume> folders. are the folders inside volumes of 100000:100000? then, compare them to /etc/subuid AND /etc/subgid. they should at least have the same GIDā¦ you may skip this whole paragraph anyway.
remember, you can always wipe/reset (destructively) your containers with podman system reset, if using podman, that is. orā¦ get fedora:latest. or try another distro, maybe? as in both as a container image and as a host? possibly NON-immutable?
yeah that is something that im familiar with. for me it was texture quality that kept crashing my steam deck. exactly a few seconds after loading the map. which CAN be reproduced in singleplayer. so, maybe its the shaders? try clearing the vulkan shaders. untick and tick the shader caching in steamās settings.
ah, madlad. for me, im a learner only when needed. 10 years, but i dont develop things, contrary to popular belief. i just like the publicly open philosophy, see?
anyway, no clue, SORRY. im also on a bit of a break from beamMP (i have been playing non stop and havent found anyone who can impress me so i was bored out of gaming at this time). please send logs and please try launching native beamMP and beamNG in a containerā¦ because i was unable to replicate this behaviour in my container, even though im not even playing anymore. beamMP on fedora:41 works via podman + distrobox for meā¦ 
P.S. this reminds me when i was distrohopping out of cachyOS (arch). when everything was broken and i couldnt play beamMP. it was alright, for a rolling release. but i was still using windows just to play there. but one day beammp on win10 kept constantly crashing (and BSODāing!) with a 100% chance. i even made posts about that vulkan is better, faster and more stable ONLY on linux nowadays. dunno if anyone reads these. but now windows is completely useless and should be disregarded, so is arch, btw. arch has long lost its culture. nowadays the big talk is about nixOS. just a little fun story, idk
hey it gave me on linux mint gave me ths error
Make Error at /usr/share/cmake-3.28/Modules/CMakeDetermineSystem.cmake:176 (message):
Could not find toolchain file: ~/vcpkg/scripts/buildsystems/vcpkg.cmake
Call Stack (most recent call first):
CMakeLists.txt:3 (project)
please respond asp
Did you install and properly set up vcpkg?
I have the same issue, did you ever find a solution? I am also on Mint so this may be a LM22 issue.
Ye I used playitt for the tunnel connection
I am unfamiliar with āplayittā, how can I run it and what does it do?
I managed to get BeamMP running, I posted my solution here:CMake Errors on Linux Mint - #4 by MintCondition