Faalagorn
Published
Starts with a black screen
Uses Steamworks as well as Games for Windows -- Live!
Game can be launched to menu, but not played without GFWL
As Seegras mentioned, you can use xlive.dll that disables GFWL, eg. from https://community.pcgamingwiki.com/files/file/576-bulletstorm-xlivedll/ to "play" offline, but you will only be able to view menus and change options as all other features require GFWL to play.
You may need to run on lower details to avoid crashes, but they also appear under Windows. Except for that, the game runs flawlessly.
The game won't start in Proton 3.15-5 Beta at all for me, even if it started (but crashed when loading the map) previously. Will update the report if things change.
Didn't work on previous Proton versions, now seems to work flawlessly -- game loads and runs flawlessly (250+ FPS on highest settings on 1920x1080!), at least on the first level, and server browser seems to load fine as well.
Unity 2018 game also available on browser but you can't use the same char on Steam. Only DX11 (default) and DX12 renderers are available
May be something on my side, but after first launch, audio was appearing in Pulse Audio volume control, but it wasn't playing
Since the last update, the game starts. I can't match with the default proton, but when changed to proton-tkg (4.12.1 currently), I can match and play the game normally. The only issue I have is the problem with mouse, when I sometimes can't choose the upgrades in buy menu (but can shoot just fine), though I think it's the plethora of mouse-related tweaks I have applied.
Everything in menu works, but clicking the matching button starts a countdown that never match.
It used to work with custom proton-tkg (see my previous report), only having that issue with regular proton, but then it stopped working on or shortly after the free to play update for me. Currently doesn't work with the newest proton, I too suspect anti-cheat to be a problem here.
The game had trouble matching previously, but now it seems to work fine. No idea what was the problem before.
I had to disable my second monitor to be able to select my main monitor resolution
I had to fiddle with resolutions and fullscreen modes before finding the one where my mouse would be bound accurately
The launcher starts fine as of Proton 3.16-5 Beta, however due to servers being offline, it can't be tested further.
The launcher starts fine as of Proton 3.16-5 Beta, however, due to the servers being offline, it can't be tested further.
Daybreak logo screen shows, but the game closes afterwards after some time
The launcher starts fine as of Proton 3.16-5 Beta, however due to test server not loading and main servers being offline, it can't be tested further.
Not all keys can be bound
Migh be because the game is emulated and we played 2-player game with Steam Remote play
You have to click "ignore" on initial errors
D3D11 using DXVK. Sometimes results in a little stutter, at least in the mechanical drive, the first time shader cache needs to generated, which could be solved by having up to date shader cache. Sometimes stutter won't go until the restart which may be issue on my side. Otherwise no issues whatsoever completing the game.
Sound is working and you can click stuff blindly, but there's only a black screen
Even with DXVK_HUD=full %command% no hud appears
Still now working as of Proton 5; gamescope shows pink screen
I was able to get a pink screen when using gamescope, but the game still won't show anything past this in Proton 5.0-1 including various GUIs. The command I used for this was:
gamescope VK_INSTANCE_LAYERS=VK_LAYER_MESA_overlay MANGOHUD=1 GALLIUM_HUD=fps DXVK_HUD=full -w 1920 -h 1080 -- %command%
I now see the main screen that's 1024x768 and goes toward the language selection menu, though no overlay or mouse/keyboard input work.
I'm using sway running Wayland with stable Mesa from DXVK. The screen refreshes every time I try to force fullscreen again, though. There are glitches around the screen if the resolution is different, but setting screen resolution to 1024x768 didn't help either.
Game didn't work at all before, so that's a progress.
Random gibberish that fills the entire screen beside the game window.
The game runs at 4:3 resolution which causes the area around my 16:9 monitor to be filled with garbage. While the game can be switched to windowed mode, it lacks any window stying and sometimes have trouble rendering when window size is trying to be changed.
When the game lost focus for the first time, I can't click anything anymore, area behind game is being clicked instead.
Sometimes the game doesn't refresh screen properly, resulting in heavy frame skipping for me.
Game can only be SIGKILLED
It always launches on my second screen and sometimes I can interact with it, it seems playable then but I didn't play a lot to check everything before I broke it by trying to change to windowed or switch monitors.
As of 3.16-4 the game no longer crashes when browsing the server list. .NET framework not installing can be ignored. To fix audio issues, you have to install xact via winetricks, protontricks or protonfixes.
After 3.16-5 Beta, no tweaks are needed to fix the audio and the game seems to run just fine.
Game crashes after several seconds, no matter the settings I use
Might be an xwayland issue, but after I launch the game, it stops responding few seconds after it launches.
If using systemd-resolved, game will crash shortly after start without this applied: https://wiki.archlinux.org/title/Steam/Troubleshooting#Games_Running_with_Proton_5.13_have_no_Internet_Connectivity
Either says that it's missing executable (at first), or throws "Runtime Error (at 123:1458)"
The game launch now (at least with custom Proton-tkg 4.11.r6.gfbb8eac8 for me). The launcher seems to work, you can click Play, read the BattleEye notice, but the game crashes afterwards with the option to send bug report.
Sometimes map textures are loading slowly, though It's hard to say where's the fault at
Minimal microstuttering once every several minutes, hard to tell it's the game's, Mesa's or DXVK's fault.
Crashes when Uplay overlay is enabled
Player avatars do not always load, but it might as well be game's fault
Should run without issues both in 32-bit and 64-bit mode now. D9VK works too. If Unreal causes trouble with mouse or window size, use fullscreen (in the game's menu or /UDKGame/Config/UDKSystemSettings to "Fullscreen=True")
Some launcher window appear, but with no clickable elements and it can only be closed with ESC.
Might be some Wayland issue or something to install through Winetricks
