natervader
Published
Near perfect out of the box.
Only major thing to note was there was connection issues at the start of a session that cleared up. I'm leaning on this not being related to proton itself but figured it was worth mentioning.
Pretty good experience overall, ilbeit a few bumps along the way
Initial loading marred on a standard HDD, moving to an SSD solved most performance problems.
At one moment through a playthrough the game's visuals were frozen, but could still hear the game being played. This happened during a cutscene so it was an easy fix, just restart the game.
Had initial issues with the Origin overlay and trying to join through that. Seems it later fixed itself however.
Using FSR helped with power draw and framerate stability.
Does not properly launch, furthest it will go is attempt loading OpenXR which instantly crashes the game and SteamVR
I've tried 3 different versions of SteamVR:
- Standard build
- Beta build
- Legacy "linux_v1.14" build Unfortunately none seem to work.
Using the legacy build does have the game prompt that OpenXR fails to load. Likely doesn't have OpenXR support. Honestly surprised that it doesn't work at all, considering it's a sequel to Boneworks which I've had no issues running previously I'd thought they would be similar enough to at least playable.
Didn't launch the game's most recent beta due to Easy Anti-Cheat
EAC is well known for not working on Linux systems. This is no different.
While EAC mostly works now, I can't get it to load anti-cheat module after one session
Switching to experimental build of Proton allowed EAC to load properly, however after a first test run (played roughly a half hour) it now refuses to launch at all. EAC reports that the anti-cheat module isn't running.
Not sure why this is the case.
Works perfectly out of the box with Proton 6.3-6, aside from Post Processing video setting issues.
Audio worked perfectly fine, however when system is having issues with post processing my whole computer's audio loads in as new frames are shown.
Draw distance seems to be shorter or weird, more frequent pop in noticeable especially on larger environment objects.
Changing graphics setting for post processing brings not only framerate but also the rest of my PC to a crawl with either high or ultra. Less is workable but definitely not something expected.
Crashes on loading Steam overlay. Otherwise no issues.
Intro cutscene muted, including the 2K and Gearbox stuff on launch.
A year ago this game hardly ran for me, now it's borderline native.
I've been using pipewire for 4 months or so, ever since switching there have been some issues with specific games loading audio at all. This appears to be the case for Black Ops 3 as well.
As others noted, installilng outside of the user's /home/ directory (for some reason) doesn't let the game detect installed mods. Have not tried any fixes, however moving onto my /home/ drive did fix the issue.
I hope someone is able to find a fix to these weird pipewire issues some games have.
Runs like-native. No issues.
At one point the game could not start whatsoever, despite Steam insisting it's running. An update to my OS and a reboot solved the issue.
Practically works as native without tinkering.
Ocassional stutters after loading new areas on ground, but I'm talking twice within a half hour test session.
Mostly works, however microphone issues ruin some of the fun
Microphone not working properly in-game. My mic gets sped up extremely fast, becoming barely distinguishable and sounds like gibberish. Likely a pipewire-pulse sync issue or something. As the game's core concept involves talking to others over voice chat, dampers the experience quite a bit.
Did not want to fullscreen initially, however adjusting the fullscreen/windowed setting fixed this no trouble.
Likely growing pains as the game literally just came out today as a surprise launch, won't be surprised if it's patched or a workaround available within the week or something.
Works as intended, amidst minor text issue.
Borderless fullscreen worked perfectly, just not true fullscreen.
If there are no players at the end of a round, it still displayed "1 Player Remaining" despite none remaining. Incredibly minor.
xrandr --output HDMI-0 --off && %command% --use-angle=vulkan && sh /path/to/.screenlayout/script
As others note, Nvidia GPUs suffer from an odd bug getting the game to properly fullscreen. Fixed by adding --use-angle=vulkan as a launch option.
I have two monitors with varying refresh rates. The game runs perfect (and I mean perfect!) on it's native port as long as all of your monitors follow the same refresh rate. It has fair performance issues (small stutters constantly being the main one) while running two monitors.
I skirt around this by setting my secondary display off for X, and have it run a small script generated by arandr to enable it again properly.
The game warns on first launch that having a high sample rate can cause stability issues, however have never had any issues on the Linux port with that.
While not a report for Proton version, I had tried using it a few times and while it fixes some stutters from dual displays it had a tendency to randomly hard crash after some time. This is likely related to dual displays or a high sample rate being used by my DAC.
Very poor performance in my experience. May be a better experience after tinkering but didn't work well for me.
Very poor performance, while it didn't run great natively on Windows 10 it would come to a crawl (average about 10fps) and not enjoyable to play at all.
Works for the most part out the box, however some adjustments may end up with confusion for normal users.
Mouse cursor in main menu was laggy initially however after adjusting video settings it seemed to resolve itself.
As others have noted, more recent GPU drivers for NVIDIA don't work with high VRAM allocation for whatever reason. Does not hinder performance on my GTX 1080, just left the setting on high. Looks fine graphically still.
Framerates are shown by the lowest refresh rate monitor on system, so my 144hz panel was restricted to 60hz despite fullscreen. Disabling the secondary monitors fixed the issue.
Game runs for the most part as expected, no major issues.
Occasionally some voice lines don't seem to load properly, and a sound effect (usually a thud) would play instead. Not game breaking but sometimes distracting.
Fullscreen doesn't seem to work properly, however windowed runs perfectly fine. To get it to run borderless I used KDE's window settings to force it in place.
Nothing major, but upon walking around certain areas there's a bit of a dip in framerate. Typically not noticeable unless using an FPS counter.
Crashed once through my playthrough so far.
Borderline perfect out of the box experience.
Fullscreen was most stable experience, however bringing the game back into focus after some time would sometimes take time to open again. Leaving open for hours like this could eventually leave it virtually broken, running risk of losing save data. Leave autosaves on!
EAC borked the game. Game refuses to boot due to failed Easy Anticheat module.
Poor experience opening the game as well as frequent-enough crashes ruining an otherwise fine time.
Game would crash at random points.
Game would not load properly into any menus while running dual monitors. Despite changing settings in-game to be windowed and whatnot, it refused to load past the opening credits (which were also extremely stretched and bugged out). Like magic, when disabling the secondary monitor I've had no issues initially opening the game.
Running standard Proton completely ruins load speeds for whatever reason. Switching to experimental or GE helped a lot.
- Limit framerate to 60fps in deck's performance settings or in-game's video settings
- Set in-game resolution scaling (FSR) to "quality"
- Optionally changing the overal graphic settings to low preset helps, but not significantly
As with desktop, GE is going to be your friend for this game. Despite the fast NVME drive in the deck, the load times can be terrible on standard Proton. Highly recommend going through the trouble of installing it.
Worth noting how the game never crashed for me on the deck.
gamemoderun mangohud %command%
Mouse was not smooth, impossible to play with it
Controller is the only good input for me
More or less worked as expected, however probably not as high of performance considering natively in Windows.
Crackling upon initial load and while testing with Proton 4.11-13, however on Proton-6.12-GE-1 it only started off with it. Once it was up and running properly no issues.
Haven't tested on Windows by any means but considering the minimum specs my system is well above, and graphically don't think it's too straining despite some pretty effects. Also might be due to early access stage of development however.
Had a bit of issues with performance, especially early on. however after changing it to fullscreen it seemed to help a decent bit.
Vastly workds OOTB. Main issues derive from online play, which is common on Windows as well.
After further experimentation, I could not get the game to boot into fullscreen mode. It does enter if the game is open already, however.
In order to change the setting manually, head to <steam_install>/steamapps/compatdata/553850/pfs/drive_c/users/steamuser/Application Data/Arrowhead/Helldivers2 and edit user_settings.config. Within that file, there's a line for enabling fullscreen. Simply set that to false and it should be fine again.
Recommend just leaving on borderless.
Nothing else to add, but my previous report's info still stands.
Performance isn't as good as it should be, connection doesn't seem as stable as it should be, however largely works out of the box.
I feel like the FPS should be better, but otherwise nothing major.
Had one crash upon changing video settings, particularly render scaling. Otherwise, the game tends to hang when alt+tabbed for a period. It comes back after some seconds.
Played three missions as of writing. First had ended with a connection error as finishing the mission, however progress was logged. Second had me disconnect again after the mission was all completed. Third had no issues. Don't see any major concerns right now.
Connection issues could be as simple as the game's traffic creating issues in general. I have no way to confirm this now, but worth noting.
Surprised I've has so few issues despite the anticheat and other reports!
(Kernel and GPU drivers are up to date, need to update my specs)
Game playable overall, however frequent issues with multiplayer. How much of that is down to Proton is tough to tell.
7.0r6-GE-1
Occasionally when swapping between applications ctrl would be held on it's own. Pressing it again manually on my keyboard solved the issue as it happened.
Not very frequent but have had a couple times where the game would hang and crash after some time. Particularly on 6.3-8.
Majority of time spent on this game was via multiplayer, and I had continuous issues playing with others.
The most broad issue was it seemed that loading into new quests would be a dice roll of properly connecting. I believe this is related to loading issues because the loading screen would hang for a few seconds at times, and after turning settings down to low the issue became less prevalent.
Another would be when finishing a quest with others and loading back into the hub world; it would also be a chance of kicking me out of the lobby. Rejoining is simple enough that it can be dealt with as it comes but definitely frustrating. This mostly happened on Proton Experimental.
Game runs perfectly fine otherwise. Believe that playing solo would be much simpler of a time.
FSR to improve battery draw.
Crackling only with RE logo on launch.
Game does not support 16:10 displays, leaving slight border on top and bottom of display. Perfectly fine and easy to ignore, but worth mentioning.
Perfect out-of-box experience marred by significant audio delay
Audio significantly out of sync, while sounding good, made timing properly very difficult. I was still able to mostly ignore it and continue enjoying the game.
I'm imagining the release version of the expansion will not have this issue considering it's still going to launch through MH:Rise itself as DLC, not as an independant game.
Like-native experience.
Switching workspaces in KDE Plasma would ocassionally cause head position to stay, leaving the mouse to act as a cursor in-game. Fixed by swapping back and forth again.
Decent performance drop on trying to stream the game through Discord.
Still like-native, however one weapon may make game prone to crashing.
Only times I've had crashes were from the gravity staff. Otherwise no issues.
Works perfectly now with Proton 7.0-1
- Game does not boot on SENTINEL update unless running 7.0-1
Largely plays like-native aside from issues with Pipewire
Had switched to pipewire to solve some issues my DAC was having with pulseaudio, ever since this was one of the few games refusing to have any audio output.
Slight delay (within 100ms) of mouse input, especially noticable within menus. Largely unimportant due to the game itself having floaty controls to begin with.
Unplayable Under a Wayland DE
Constant flickering under Wayland. Likely more issues with NVIDIA's drivers and display syncing or some such. Makes the game unplayable. Stick to an X11 desktop for this one.
Without another system to at least *start* the game on properly, the game will refuse to start.
Mouse slightly slower response time than normal
Game refuses to start past initial load UNLESS it generates system data on first launch elsewhere. Likely tied to Denuvo's antitampering methods. Once started on the Steam Deck and syncing saves it loaded in as intended.
Hopefully something within Proton could be fixed up to fix this weird issue. Also performance was perfectly fine otherwise.
Game launches after syncing a cloud save from elsewhere, however will not load into any saves
Update on my previous report: does not seem to work for me at all I guess. I can get into the main menu but attempting to actually play the game leads to a hard crash like everyone else.
Overall positive, however significant performance issues as compared to native Windows performance of GPU.
- Logitech Extreme 3D Pro was not detected with 6.3-8, swapping to a GE build had detected it however.
- Joystick is not detected if plugged in after the game boots. If you intend to use it while playing be sure to do that, not fun to hop in a ship and realize you need to reboot in the middle of an alert to get that functionality again.
I don't feel like it runs as well as it should given hardware, it runs much better dropping the settings to low but still worth mentioning. Sort of disappointing.
%command% --disable-gpuallows you to open the launcher, which is required.
Daybreak has added a whitelist for Proton within EAC, thanks to additions from Epic.
"Wine is not supported!"
Thanks EA.
The nature of specific protontricks command as well as install location would make things mostly confusing for normal users.
Game must be installed in standard directory for Steam games for protontricks to work properly. Had initially tried installed on a separate drive and wondered why it didn't do anything.
protontricks 221040 -q wmp11 to install codecs the game needs to run at all.
Very noticable stutters during all cutscenes, gameplay was for the most part perfectly fine.
Crashed once during my hour of playtime.
Had connection drop out at one point during a co-op session, however likely an issue on the game itself.
Borderline perfect experience aside from cutscene loading issues.
As others reported, the initial cutscene has something about it that causes the game to slow down to a crawl, sub 5 fps. Other cutscenes either don't load at all or play as expected.
Gameplay itself was perfect.
I've also tried running GE since that tends to play better with cutscene files however it didn't run as well for me while playing.
Played through most of the game with 40hz, it significantly cuts down battery usage while maintaing decent enough responsiveness.
Crackling noise (almost sounds like peaking) after waking from sleep mode. Roughly a 1/3 chance happening, and almost always occured when sleeping during gameplay. Pausing beforehand usually helped.
- The timing for the starting countdown for races didn't appear properly, would count extremely fast. The race otherwise acted normal.
- Without cloudsyncing saves the game's sort of a bummer to not be able to jump from the Deck to the PC. No dealbreaker, but worth noting.
Perfect out of the box experience for the vanilla game. Have yet to test popular SADX mod
Game has initial launcher for changing PC settings (resolution and whatnot). Be sure to change the input to controller before launching the game itself.
As noted earlier, be sure to enable controller in the launcher.
Fantastic, probably prefer playing it through proton than natively on Windows quite frankly.
The Windows port exclusively demands fullscreen and switches resolutions when switching maps, so any time you launch an instant action playlist from the main menu for example you go from 640x360 to whatever resolution you select.
This doesn't occur on proton due to how it grabs the game, making it essentially run in borderless window and does not switch resolutions whatsoever making the slight inconvenience completely nullified.
Largly works fine, however if other reports are true then updates can make experience inconsistent
PROTON_USE_EAC_LINUX=1 gamemoderun mangohud %command%
Grabs my secondary display's resolution to share as my primary display's resolution. Running fullscreen windowed makes this a null point, still fills the primary display.
Was playing perfectly fine for a number of days but it currently refuses to start, stating `Failed to initilialize dependencies" after attempting to boot up.
SDL_VIDEODRIVER=windows %command%
Game boots with a "Failed to initialize resources" or something unless you specify the lauch option SDL_VIDEODRIVER=windows %command%. This is likely a wayland specific issue.
Source: https://www.reddit.com/r/linux_gaming/comments/194yurj/comment/khmk1dx/
mangohud gamemoderun PROTON_USE_EAC_LINUX=1 %command%
Game totally freezes after a moment of being open. Likely related to recent update. Unable to play.
mangohud gamemoderun PROTON_USE_EAC_LINUX=1 %command%
Hangs after much less time than previously, however it still hangs after a few matches.
Game refuses to load past the company logos at launch, stuck on black screen
I've tried several times to get it working past that point but it just doesn't seem to want to load. Pretty disappointing.
Does not launch at all currently.
After installing extra dependencies it just fails to load the game. Any proton version comes with the same result.
Borderline perfect.
I played a large percentage of this game via my Steam Link in the living room, and in the final sections of the game there was EXTREMELY SLIGHT crackle issues. I've had audio issues with Steam in-home streaming before so it's likely down to that, but wanted to mention regardless.
Largely perfect.
As said elsewhere, mostly played via Steam Link in-home streaming. If booted up the game while using the Link no controllers elsewhere are detected, only keyboard inputs work once returned to the PC while the game is still running. Most likely an in-home streaming issue, but wanted to mention.
