BeamNG.drive
Forum rules
Behave
Behave
- Grogan
- Your Host
- Posts: 3211
- Joined: Sat Aug 21, 2021 10:04 am
- Location: Ontario, Canada
Re: BeamNG.drive
I'm downloading this now, so I can crush some pianos or something with that big loader 
- Grogan
- Your Host
- Posts: 3211
- Joined: Sat Aug 21, 2021 10:04 am
- Location: Ontario, Canada
Re: BeamNG.drive
Hey, did you know there's a native Linux port for this game now? I didn't know. I don't think it's "official" (turning off "force compatibility tool" would just use the default proton), as both Linux and Windows binaries are installed and it looks like you'd have to run BinLinux/BeamNG.drive.x64 manually (with Steam open or there's a way to do it with the Launch Command... like "path_to_binary %command%" I think)
I tried
but it just crashed on launch. So I removed the game and checked the "Linux Runtime (Sniper 3.0)" compatibility tool but it looks like it's downloading the same files, both Windows and Linux so the result is probably going to be the same. (I find that generally things don't run through that Linux Runtime, I just select that to force a game to download Linux files and then uncheck it again to run the binaries natively)
Yes, it just downloaded the same files. If I try to run it through the Sniper runtime, it crashes. If uncheck that, it still runs the Linux version but it crashes
HOWEVER, (not so) oddly, it runs if I have steam open and run the binary manually. I say not so oddly, because I've seen this behaviour before when it's the Steam integration that a native binary is having a problem with. For example, Borderlands Pre-Sequel Linux binary can still run like this, but barfs on running it normally through Steam.
While in the steam/steamapps/common/BeamNG.drive (installation directory/working directory). e.g. for me:
Note that if you've been playing it through Proton, and you try this, you'll have to copy your stuff from its place in steam/steamapps/compatdata/284160 (since its gone I can't remember the exact location) to ~/.local/share/BeamNG/BeamNG.drive/current. It doesn't bother me because I don't have any stuff. If I did, I would have just lost it by uninstalling the game anyway 
P.S. Actually is IS working normally (the Linux port) without forcing any compatibility tool (unchecked setting). I forgot that I didn't remove the ./BinLinux stuff from the Launch Options.
So it does default to the Linux native binary now. I've just always had it running with that setting in place (for my proton_tkg_custom_valve) so every time I remove and download it again, it was running the Windows version. I don't have to run it manually after all. It seems to work pretty well. I'm not sure about "better" but I might as well use it.
Also, I think I vaguely remember trying the Linux port before and having it not work correctly or something. It could be a false connection, but I got that feeling that I'd been there before.
I tried
Code: Select all
./BinLinux/BeamNG.drive.x64 %command%Yes, it just downloaded the same files. If I try to run it through the Sniper runtime, it crashes. If uncheck that, it still runs the Linux version but it crashes
HOWEVER, (not so) oddly, it runs if I have steam open and run the binary manually. I say not so oddly, because I've seen this behaviour before when it's the Steam integration that a native binary is having a problem with. For example, Borderlands Pre-Sequel Linux binary can still run like this, but barfs on running it normally through Steam.
While in the steam/steamapps/common/BeamNG.drive (installation directory/working directory). e.g. for me:
Code: Select all
cd /storage3/shit/steam/steamapps/common/BeamNG.driveCode: Select all
./BinLinux/BeamNG.drive.x64P.S. Actually is IS working normally (the Linux port) without forcing any compatibility tool (unchecked setting). I forgot that I didn't remove the ./BinLinux stuff from the Launch Options.
So it does default to the Linux native binary now. I've just always had it running with that setting in place (for my proton_tkg_custom_valve) so every time I remove and download it again, it was running the Windows version. I don't have to run it manually after all. It seems to work pretty well. I'm not sure about "better" but I might as well use it.
Also, I think I vaguely remember trying the Linux port before and having it not work correctly or something. It could be a false connection, but I got that feeling that I'd been there before.
- Zema Bus
- Your Co-Host
- Posts: 1955
- Joined: Sun Feb 04, 2024 1:25 am
- Location: Arizona
Re: BeamNG.drive
Interesting, I wasn't aware of that.
- Grogan
- Your Host
- Posts: 3211
- Joined: Sat Aug 21, 2021 10:04 am
- Location: Ontario, Canada
Re: BeamNG.drive
It crashed once on me, while I was changing vehicles. I had loaded several maps and many different vehicles in that session though. It kind of froze, but that's because a crash was intercepted. There was a crash handler dialog on my icewm taskbar that closed the program for me. I loaded up again with the same vehicle and I was doing great, not a scratch, driving around East Coast USA. I was just thinking that, when... I briefly drifted off to sleep and wracked my vehicle into the trees (and it was time to quit) 
- Zema Bus
- Your Co-Host
- Posts: 1955
- Joined: Sun Feb 04, 2024 1:25 am
- Location: Arizona
Re: BeamNG.drive
"Asleep behind the wheel" lol!