NOTE: DO NOT use the Flatpak version of Steam. It causes dependancy issues. I repeat, DO NOT use Flatpak.
For all five of us that play on the Linux Native port, here are some compiled binaries (and some other stuff) that'll save you the hassle for compiling it yourself. This was compiled on Mint (for Debian folks), Manjaro (for Arch users), and Fedora 37 (for Fedora users). The Steam Deck, due to Valves' insistence on using Flatpak, is not supported (Flatpak uses sandboxing, and system files are not easily accessible from it).
This download gathers togethers the latest patches from the Loader Gitlab page and the Lua Gitlab Page into one easily accessible download. This was orginally hosted via Google Drive, and could be found on a steam guide I created.
What This Includes:
- A Readme -- I urge you to read it.
- The Loader.
- The Lua Base Mod and "Linux IO Compat V2"
- Prerequisite search scripts that lets you find any pre-requisites needed to make it work. This saves me hassle, and frankly, I dunno how I didn't think of this sooner. HOW TO USE: Drag the file into terminal, press ENTER, input your password when prompted, press ENTER again, and accept all downloads it asks for by pressing ENTER again.
You will now have mod support!
NOTE:
As of right now, the game will crash when using later versions of Mesa built around LLVM 14 onward (Not a SuperBLT issue, but it's worth mentioning here); which rules out any up-to-date distro (even those using stock Mesa on Ubuntu). On Debian distro's, using custom PPA's that upgrades Mesa (Kisak, Mesaarc, Oibaf etc.) will also cause issues, and were the first to break due to being compiled against later LLVM versions.
The current solution is to enable Zink, an OpenGL -> Vulkan conversion layer built into Mesa, as the graphics backend instead of OpenGL:
env __GLX_VENDOR_LIBRARY_NAME=mesa MESA_LOADER_DRIVER_OVERRIDE=zink GALLIUM_DRIVER=zink LD_PRELOAD="$LD_PRELOAD ./libsuperblt_loader.so" %command%
This also allows you to continue using up-to-date Mesa, as well as letting you use the Native Linux port. Note that there may be some performance issues on certain heists (weird spiking in GG Casino's vault, but that's not exactly the poster child for PD2 heist performance anyway).
I getting crashed with this log
Segmentation fault!
Note: I tried to launch a Restoration Mod Overhaul and get this, no mods included expect beardlib, linux io a ResMod itself. It works fine on vanilla thought but not in overhauls. It's on my side or blt issue?
Resmod is likely the cause. I'll take a look in a few hours.
I asked some questions on discord server of resmod and what i can say:
There is no problems with blt4l, it just native version sucks.
@MRKARTOFAN Well I'd love to know what the crash involved. If you can send me a detailed log (found in the mods/logs folder), then I can look at working out what's wrong (or find people who can). It's not hugely surprising ResMod breaks on native, given how many moving parts to it there are, but blaming the port, and saying the "native version sucks" doesn't solve anything but build up unneccesary hate, and I'd rather just try and fix the issues than go that far off the rails.
Scanning through Github briefly, the first thing that catches my eye is the custom animation replacements, which yeah, will break on Linux due to the animation headers being 64-bit and no conversions being done via Beardlib yet, but I can't imagine that causing crashing on startup. I'll look into this, if nothing else but out of curiosity.
Also, BLT4L has been deprecated for years. I really hope you're not using that old loader.
EDIT:
Managed to successfully launch Resmod on native, so I know it at least loads -- albeit it does appear to like crashing due to some apparently malformed lua files.
@Dribbleondo-Van-Pelt You can succesfully launch pd2 with resmod, yes, but when i tried to change mask/weapon it's just crashes.
I can't provide you full blt log because i wiped out pd2 completly and now it's on proton
@MRKARTOFAN That's consistent with my experience, but still, I wanna work out why it's happening. It really shouldn't crash there.
@Dribbleondo-Van-Pelt Same error here :(
Segmentation fault! Obtained 23 C++ stack frames: 0x7f4028322127 libsuperblt_loader.so : blt::error::handler(int)+0x87 0x7f40276bef50 libc.so.6 : +0x38f50 payday2_release() [0x5843a0] payday2_release() [0x54272b] payday2_release() [0x90a310] payday2_release() [0x8f4db6] payday2_release() [0x8f19b2] payday2_release() [0x8f2a85] payday2_release() [0x8fbf7a] payday2_release() [0x9077ae] payday2_release() [0xf6b2b0] payday2_release() [0x563aa4] payday2_release() [0x991ba8] payday2_release() [0x993a6d] 0x7f40282be59d libsuperblt_loader.so : blt::dt_Application_update(void*)+0x65 payday2_release() [0x9935ef] payday2_release() [0xa4f63c] payday2_release() [0xa505a5] payday2_release() [0xa4f2b4] 0x7f40276a9790 libc.so.6 : +0x23790 0x7f40276a984a libc.so.6 : __libc_start_main+0x8a payday2_release() [0x4213f4]I really want to use to native version tho...
Also I had some issues with the provided basemode as it would crash when loading Resmod luckily there's a fix on github
If I can provide more information let me know I also commeted on a Gitlab Issue
@Bilal Resmod currently doesn't work; don't use it. Among other things, it has misnamed filepaths (damn you captilisation!) and it uses custom animations, so even if you got past the main menu, you'd crash in-game the moment a new enemy spawned.
So yeah. stay away from mods that add custom animations (and mods of this kind usually mention this).
@Dribbleondo-Van-Pelt What a bummer... Thanks for the answer
@Dribbleondo-Van-Pelt I am getting the same error however upon leaving the "BLT mods, mod options, and mod keybinds" causes the crash as I commented under the steam guide. Tried to remove all custom animation mods (there is only one and its perfect viewmodel) once and it still crashed doing the same thing
@konny da cherry Delete blt_data.txt in PAYDAY 2/mods/saves .The game will regenerate that file when you next start the game up. Given that it affects mod settings (which is what blt_data.txt houses), it's likely your file got corrupted somewhere along the line.
Not a linux specific issue, this happens plenty on Windows too, but it can be annoying.