UnsupportedShow Details
Unknown
SARD Has been fully removed from the game, thus allowing APB to run on Linux again, with stock proton.
Another Kernel level Anti-Cheat made Linux gamers bite the dust.
SARD Anti-Cheat (The newly implemented Kernel-Level Anti-Cheat) completely denies launch for Linux users.
They enabled kernel level SARD anti-cheat
Very dissapointing, especially since it previously worked on Linux... Don't expect this to ever run on Linux again unless they change their mind :(
SARD - Kernel Level Anti-Cheat
Unfortunately they've introduced a kernel level anti-cheat solution from SARD and this has made it so the game no longer works.
DXVK_CONFIG="d3d9.cachedDynamicBuffers = True" %command%
winetricks vcrun2017 into the prefix. protontricks would probably work also
without d3d9.cachedDynamicBuffers enabled, theres frametime spikes when shooting
"$HOME/.local/share/Steam/compatibilitytools.d/GE-Proton9-5/proton" waitforexitandrun "$STEAM_COMPAT_INSTALL_PATH/Binaries/APB.exe" -language=1031 # %command%
The provided launch options use Proton GE with the option -language=1031 to load a custom config. This part is optional.
Works flawlessly now using Proton-GE, dependencies issues might arise if you use default proton, so i will always recommend using Proton-GE instead, simply no problems now.
Works as well as the Windows version. Could be confirmation bias, but it feels better to play on Linux than on Windows.
Same as the windows installation.
"$HOME/.steam/steam/compatibilitytools.d/GE-Proton8-25"/proton waitforexitandrun "$STEAM_COMPAT_INSTALL_PATH/Binaries/APB.exe" # %command%
Older hardware requires Proton GE to load into the district servers fast enough to not get kicked by the Anti-Cheat system.
Installing Proton GE is recommended on older hardware, as the standard versions of Proton can result in such long loading times that the anti-cheat will kick you. Another advantage of using Proton GE is that you don't need to disable Steam login via configuration files or the -nosteam option as Proton GE bypasses this issue.
[LoginSettings]
bUseSteamLogin=False
The following lines must be added to APBGame/Config/APBMachineOptions.ini to disable Steam login which crashes the game:
[LoginSettings] bUseSteamLogin=False
general choppyness every so often
Currently June of 2023, Steam released a UI update which is crashing games trying to call the overlay. Login via gamersfirst account.
some studders but overall runs just fine
Fails to get past the launcher.
The APB launcher loads, but presents a popup box saying "Not enough free disk space: 3.83 GB is available, 4.49 GB is required.". The launcher then shows a red 'error' icon in the top right, and the APB Error Report window appears. I've tried setting launch options and making sure that the Proton BattlEye Runtime is enabled, but all to no avail.
The following lines must be added to APBGame/Config/APBMachineOptions.ini to disable Steam login which crashes the game:
[LoginSettings]
bUseSteamLogin=False
This can be accomplished by the following terminal command (run after the game has already installed)
echo -e '[LoginSettings]\nbUseSteamLogin=False' >> "$HOME/.steam/steam/steamapps/common/APB Reloaded/APBGame/Config/APBMachineOptions.ini"
Slight stutters when interacting with custom player-created content, such as shooting at custom vehicles
Steam login crashes the game
With the latest (05/05/2023) Experimental and an ini tweak, it works without the need for launch codes
In .../steamapps/common/APB Reloaded/APBGame/Config/APBMachineOptions.ini add the following two lines to the end of the file:
[LoginSettings]
bUseSteamLogin=False
Still crashes occasionally
%command%; $HOME/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=113400 -- $HOME/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- <path to steamapps/common>/SteamLinuxRuntime_sniper/_v2-entry-point --verb=waitforexitandrun -- "${STEAM_COMPAT_TOOL_PATHS%%:*}"/proton waitforexitandrun "$STEAM_COMPAT_INSTALL_PATH/Binaries/APB.exe" -nosteam
Still crashes occasionally.
EasyAntiCheat requires the game to be launched via the runtime or it will complain about an unregistered executable (APB.exe). Running it with the launch options above (thank you to @telqor on Github) works around the issue.
'/home/steam/.steam/steam/steamapps/common/Proton 7.0'/proton waitforexitandrun '/home/steam/.steam/steam/steamapps/common/APB Reloaded/Binaries/APB.exe' -nosteam # %command%
Works same as on the Windows.
Works better than Windows (as of FPS). Download GE and enter that launch options will works good. Played some minutes and no problems except some little slow loadings.
%command%; $(echo %command% | sed -r "s/proton waitforexitandrun .*/proton waitforexitandrun/") "$STEAM_COMPAT_INSTALL_PATH/Binaries/APB.exe" -nosteam
Make sure Proton BattlEye Runtime is installed.
/usr/share/steam/compatibilitytools.d/proton-ge-custom/proton waitforexitandrun '/opt/SteamFiles/steamapps/common/APB Reloaded/Launcher/APBLauncher.exe' && /usr/share/steam/compatibilitytools.d/proton-ge-custom/proton waitforexitandrun '/opt/SteamFiles/steamapps/common/APB Reloaded/Binaries/APB.exe' -nosteam # %command%
Game crashes infrequently
Outside of the significant launch codes necessary to make it work and infrequent crashes, it's fine.
'<path to steamapps/common folder>/Proton 7.0'/proton waitforexitandrun '<path to steamapps/common folder>/APB Reloaded/Launcher/APBLauncher.exe' && '<path to steamapps/common folder>/Proton 7.0'/proton waitforexitandrun '<path to steamapps/common folder>/APB Reloaded/Binaries/APB.exe' -nosteam %command%
Some sections are improperly lit, not as noticeable with Bloom disabled.
Infrequent crashes while playing the game. These happen in different places and in different situations.
The player driven Markeplace (auction house) doesn't display the preview on the right side pane as it should.
%command%; $(echo %command% | sed -r "s/proton waitforexitandrun .*/proton waitforexitandrun/") "$STEAM_COMPAT_INSTALL_PATH/Binaries/APB.exe" -nosteam
make sure proton battleye runtime is installed
'/home/xaen/.steam/debian-installation/steamapps/common/Proton 7.0'/proton waitforexitandrun '/home/xaen/.steam/debian-installation/steamapps/common/APB Reloaded/Binaries/APB.exe' -nosteam # %command%
Edit the paths where the abp is installed and don't forget to go to Steam and install battle eye from the library browser. the game works very well after 5 minutes of play, it has to load some things.
~/.steam/steam/steamapps/common/Proton\ 7.0/proton waitforexitandrun '/run/media/mmcblk0p1/steamapps/common/APB Reloaded/Launcher/APBLauncher.exe' && ~/.steam/steam/steamapps/common/Proton\ 7.0/proton waitforexitandrun '/run/media/mmcblk0p1/steamapps/common/APB Reloaded/Binaries/APB.exe' -nosteam # %command%
It's running stuttery at first. Probably due to shader creation on demand or something like that. After some playtime it smoothes out though.
Works as expected.
It will work just fine. Make sure Proton BattlEye Runtime is installed too.
Credits: MasterMe‘s post on ProtonDB.
This is a slightly improved version of his code. It will launch the APB Launcher first to make sure the game is up to date, and after it closes, will launch the APB.exe to play the game.
It performs well on the SteamDeck, even when playing on 1440p with FSR enabled. Keyboard and Mouse strongly recommended.
~/.steam/steam/steamapps/common/Proton\ 7.0/proton waitforexitandrun '/run/media/mmcblk0p1/steamapps/common/APB Reloaded/Binaries/APB.exe' -nosteam # %command%
The launch arguments above will only launch the game. To update it, the launcher is needed. So first run the game without any arguments, that the launcher can update everything. After the launcher is ready "Start button visible", re-add the arguments and it will launch the game directly.
The first run is slow, probably due to shaders being cached on the go. It will perform relatively well after playing a while.
When using Steam-Login, the game crashes on the login screen. Hence the "-nosteam" argument
Make sure that the Proton BattlEye Runtime is installed.
Credits: This is a variation of MasterMe's comment down below, just SteamDeck flavoured.
The game starts and login character very smooth, but Battle Eye give a error [Please help APB 1.30] 15/02/23 D/M/Y
'/home/xaen/.steam/debian-installation/steamapps/common/Proton 7.0'/proton waitforexitandrun '/home/xaen/.steam/debian-installation/steamapps/common/APB Reloaded/Binaries/APB.exe' -nosteam # %command%
i need fix battle eye after 64bit update with easy anticheat i think have 2 anti hack in same time. Please help!
'/home/steam/.steam/debian-installation/steamapps/common/Proton 7.0'/proton waitforexitandrun '/home/steam/.steam/debian-installation/steamapps/common/APB Reloaded/Binaries/APB.exe' -nosteam # %command%
Just works, make sure to install proton BattlEye runtime (soon APB switches to EAC)
Currently the game's launcher does not actually launch the game (APB.exe) when pressing play, it just quits. So after installing/updating with the launcher set the launch options to point to the actual game binary APB.exe and it'll boot up. (Change paths as needed.)
Using the steam login integration somehow causes a crash in the login screen, so disable that with -nosteam and log in manually. After that everything works fine.
There is some stutter on first time playing, probably shaders compiling on demand, very smooth after absolutely no lagspikes.
Game opens but crashes after character selection.
You need add a non-Steam shortcut pointing to (APB Reloaded Game Root)/Binaries/APB_BE.exe to launch the game.Launching from updating client is not working. If it throws a error for installing PhysX, install from (APB Reloaded Game Root)/TPI/PhysX/PhysX_9.10.0129_SystemSoftware.exe file.
Game opens normally but after character selection it crashes to this error:
General protection fault!
Script call stack:
Function APBUserInterface.cUIDataStore_Chat|OnPlayerProfileChanged
the date bla bla...
Game does not launch because of BattlEye
Developers need to contact BattlEye to enable linux support
As mentioned in previous reports, developers can enable linux support by contacting BattlEye.
Launching game through Steam
When launching the game normaly through steam, the APB game launcher opens and crashes without launching the actual game binary. To launch the game without crashing do the following:
- Press "Add a Non-Steam Game..." in your steam library.
- Select the "APB_BE.exe" file located in:
<steamdir>/steamapps/common/APB Reloaded/Binaries/APB_BE.exe. - Launch "APB_BE.exe" from steam library.
- The BattlEye window will open and get stuck with error "Failed to initialize BattlEye Service: Driver Load Error (6)".
If you get an error about PhysX not installed, do the following:
- Press "Add a Non-Steam Game..." in your steam library.
- Select the "PhysX_9.10.0129_SystemSoftware.exe" file located in:
<steamdir>/steamapps/common/APB Reloaded/TPI/PhysX/PhysX_9.10.0129_SystemSoftware.exe. - Launch "PhysX_9.10.0129_SystemSoftware.exe" from steam library to install PhysX.
Launching old version of game through standalone version
- Download the standalone version of the game available here.
- Use Wine or Proton to install the standalone version.
- Since this standalone version is older, it does not have BattlEye, and the game successfully loads up to the login screen.
- When trying to login, the game gives an error due to the game version being wrong (old).
Как всегда Battleye
Писал разработчикам на форуме пару месяц назад просьбу о добавлении поддержки линукс. Но поддержки всё нет
Developers need to contact BattlEye for linux support
Game crashes on launch
All proton versions, including GE currently crash. I had some hope because of the BattleEye Support.
Unable to launch
Stuck at Starting BattlEye Service...
