BHZ
Published
Awesome visuals, great performance, the game seems to have great optimization. Great experience.
DualSense controller was detected immediately, plug and play.
The experience could be better, but the crashes seem to be there in Windows.
Crackling while loading new scenario, pretty common in UE games.
3 crashes total in 24 hours, some gameplay progress lost, but never more than 10 minutes.
Hunting around in the forums I have found Windows users having a crash in the same point of the same chapters, so probably unrelated to Proton.
I had to install specifically Proton 5.13 since on Proton 6 mouse wouldn't work. Also, videos didn't play for any Proton version I tried.
In-game mouse right click will not work on Proton 6.13
It will be noticeable with big armies
This game should be Steam Deck verified. There are other verified games with smaller fonts and/or icons.
Having played this game on a big screen, I'd go as far as to say that Steam Deck (or a handheld) is the ideal device for this game. Runs surprisingly smooth, between 40-60 FPS, and looks absolutely gorgeous on the Steam Deck screen. The small screen compensates for the bad camera implementation. I had no crashes and no sound issues in my whole playthrough.
Playthrough with all three factions, used factions' full tech trees and abilities, no issues whatsoever.
Crashed only once on first launch, like many other games, which is why I though it needed to switch to experimental, in which I have been doing my whole playthrough.
However it seems to work now on default Proton as well, so this first-launch crash may be a different issue, certainly unrelated to this game.
Needs fix for multiplayer, otherwise excellent.
Needs known fix, otherwise playable.
Fortunately videos play for me, out of the box. Fix for multiplayer is (as described in other reviews) updating the ucrtbase.dll extracted from vc_redist in the directory where the game was installed:
cabextract vc_redist.x64.exe
cabextract a10
cp ucrtbase.dll (steam folder)/steamapps/compatdata/813780/pfx/drive_c/windows/system32
This is the same fix that other games needed. We have known about this for quite a while. I wonder if the needed library could be included in the game already on installation.
ENABLE_VKBASALT=1 gamemoderun mangohud %command%
Out of the box, it gives a warning of unrecognized graphics card driver and keeps giving the same warning afterwards. It will also launch in lowest graphical settings regardless of your hardware.
The random de-syncs in multiplayer seem to be now solved: rare Microsoft win.
In game installation folder under "steamapps/common":
- Rename dowser.exe into something else
- Rename AoWFP.exe into dowser.exe
The game is not well optimized in Windows either.
- Background on startup screen may not show up, depending on the patch version.
- The initial (sign-in) form in the startup screen may show up but not be visible, you must just blindly press ESC or Enter in order to skip the form and get to the startup screen.
The performance issues may be similar in Windows according to the reviews. The form that pops up might be too annoying for some people. Otherwise, the fact is that the game is fully playable once you press start/continue game.
Plays smoothly, all cut-scenes played. No issues.
In normally crowded scenarios, performance is perfect.
This game can get bullet-hellish at times. With 40 enemies or so on the screen, Unreal Engine and most general-purpose engines will suffer. CPU temps will be higher than GPU's, and the CPU single-threaded performance is most likely to be the bottleneck.
Near perfect game for the Steam Deck. I played in fact for some 31 hours, mostly offline.
One or two pixel-wide lines are misaligned during cutscenes. Barely noticeable.
Perfect or near-perfect roguelike fit to play on Steam Deck.
Battery life was decent, maybe some 4+ hours on the SD OLED. Not as good as the pixel games, not as bad as most Unity games.
All the videos work, and it was possible to seek to rewind or fast-forward without any issues.
Proton pretty much required for multiplayer, but excellent experience.
Native runs well enough. However, nowadays, the game performs better under Proton than native, and this is easily demonstrable thanks to the built-in benchmark tool. I don't know if this is good, or very, very sad if you think about it. On top of that, Proton is basically required for multiplayer as most other players use Windows.
Full campaign playthrough (only act 1). All videos play. No tinkering done.
Note that campaign is very short right now, mainly multiplayer game. Tested some matches against AI, the unit unlock system seems to work as well.
Full campaign playthrough of all 4 capaigns, no crashes.
Sustains rather stable 90 FPS, not going much lower than that even in big battles, a significant improvement over Homeworld: Deserts of Kharak (80 FPS with lows of 30 FPS). Very important in this type of games as the situation changes dramatically with big armies.
90-110 FPS with my hardware on a game with this level of visual detail are a luxury. I mean, the lowest FPS that I get is during the videos.
Crashes right when exiting the game after a long session, not a factor in practice.
Full playthrough. Only 1 crash, and only before first game start.
Performance seems to be excellent, probably on par with Windows.
PS5 controller not always detected, fixed by disabling Steam Input
2 crashes in 34 hours. Known issue in Windows as well.
Summary of fixes:
- Most crashes: enabling V-Sync in the in-game options.
- If crashes still happen: capping frames to e.g. 60 FPS using something like GameScope.
- I had to use the beta branch in order to get past the Archon scene.
- PS5 controller: disabled Steam Input.
Certainly not the best game for gamepad controls, otherwise incredibly low battery consumption.
A "typical" player would enjoy perhaps 5 hours of this game on Steam Deck, after which I believe they would need to do some tinkering.
Performance gets notably worse in big fights.
Roughly 2 hours of battery, not much but maybe enough for an first-person shooter. Too low frames per second just when things get interesting. I am sure both battery and frames per second can be improved a lot with some tinkering, but the experience out of the box can be disappointing for such a challenging first-person shooter.
Play the demo and see for yourself. I played start to finish without tinkering. Known issues are common to Windows.
The frame rate of cutscenes seems to be lower than in-game. This is the case in Windows as well.
- By all means, try to avoid upscaling. The game will enable upscaling by default. The experience with upscaling is not worth it IMO.
- Cutscenes at 30/40FPS is something of a standard on console. It is of course a letdown on PC, where one expects a better cinematic experience, but can be improved with tinkering. I didn't feel it was necessary for my experience, but play the demo and see for yourself.
- Combat is the most important part. Combat was very performant in my machine. Combat requires timed dodges and parries. I wouln't have played this many hours otherwise.
This game is all about multiplayer, but it implements it almos flawlessly and pain-free under Proton.
Alt-tabbing was not working in old-school big picture mode. A bit of a problem in story mode.
I have not experienced any noticeable delays. Performs better online than pretty much any other fighter I've tried.
Noticeably more battery drain than other fighters, even compared to modern 2022 fighters. Can be relevant e.g. if/when using a laptop.
Works perfectly out of the box. All the FPS you need.
Only one crash after full play-through (around 16 hours). Possibly not Proton related.
Flawless experience like the original, + DX12 seems to work.
I tried both DX11 and DX12 for a while, both worked OK. I stayed on DX12 for the last maps. I had no crashes in my 20h of gameplay, but maybe I got lucky and involuntarily avoided the moment when DX12 mode crashes. Anyway, flawless experience for me (like the original).
Multiplayer works. **This is the EA release**, I am not reviewing the demo.
This may be the same bug on Windows: Mouse scrolling in the menu while paused seems to also zoom in/out the game. Basically, mouse seems to be active in the game at the same time as in the menu.
Runs reasonably smooth on my system, 3-player full army tower defense is no problem. Minimum 20 FPS. A good example of how an RTS should be made.
All story mode videos finally work with Proton Experimental. Playstation button layout is detected when disabling Steam input.
Only the videos of chapters 1 and 2 had problems in earlier Proton, videos which many players may have seen already in the previous game. So it's not a game-changer, but good to have finally.
Everything works out of the box. Even launching your default browser from the game.
RPG mode: Got two fatal error in the mission/fight against the Grand Order ("Captain's will"). However, the mission can be completed after retrying. Multiplayer: Game hanged after finding a match. However, restarted the game and it was possible to find another match and play.
The game was hung on the loading screen and it was necessary to shut it down. After that, I was able to find another match and this time it worked perfectly.
Due to the very low population of the game (106 players at the time of writing), there are low chances of finding an opponent, and, when you do, the lag may not be optimal. However, it does work and the multiplayer issues seem to be related to the game and its support.
Only for the experienced players, or connecting the SD to a big screen.
Conversation from the shades was very difficult to read, although it is not crucial to the story. Jars with gold, enemy animations before attacking, and other much more crucial elements of the map are difficult to spot in a small screen, and there is no time to use the magnifying glass in the middle of combat.
Battery life is quite underwhelming. Average two runs, in a game where you pretty much won't turn off the SD until a run is finished.
The Steam Deck hardware is more than capable of running this game, and the graphics look beautiful on the OLED screen. However, this game has an isometric view and has way too many small details that the player has to spot in the middle of battle.
Enemy attack animations, jars with gold, little spots where you can get a bit extra lore. Sometimes even a fishing spot can be missed in the small screen (in the lava, it melds with the lava animation. In a big screen, you never miss them).
The battery is another important issue for a roguelike. After one run, I am dangerously close to half battery. This is not the case with my other roguelikes, and I think severely limits the use case of the SD for a game like this.
Near perfect experience out-of-the-box, except for a small full-screen issue.
Each time, need to go to in-game options to switch to windowed and back to fullscreen.
Full campaign play-through. Since this game is primarily campaign mode, and even multiplayer is co-op campaign, that is all you really need to know.
More than half of the game is enjoyable, but scenarios with interrupting audio are unbearable.
Audio gets interrupted during rain scenes. A deal breaker in a game that heavily depends on sound for in-game clues.
DualSense support making us resort to Proton on a game that is perfectly working on native.
- Save games lost when playing on a different computer (Proton to Proton)
- Save games lost later on the original computer after "cloud sync"
- Save games from native not found in Proton
Frame drops on very crowded scenarios. I believe this is a game issue, same for native.
PS5 controller not supported on native, difficult to enable under Proton
I had to force Proton + Disable Steam input + In-game "Disable native controller input" for DualSense controller to work, which is very disappointing for a game that works perfectly fine on native. Losing game saves in a game as difficult and long as this one, as easily as loading it in another PC, is a very bad experience. More so when this is the first game of my library in which this happens. The paths to game saves are not easy to find at all.
Full campaign playthrough with no issues.
Multiplayer may not be relevant as the number of players is very low. There were no public games nor multiplayer matches to be found.
Cutscenes would not fully play without Proton-GE
Proton-GE only needed for cutscenes, otherwise fully playable. Great game.
Full story mode with both endings, no issues.
The first run seems to crash, otherwise works perfectly. This first-run thing has happened to me with Doom Eternal as well, not unique to this game.
I have not noticed long loading times for fights, at least not longer than with Mortal Kombat 11. If that was the case for other users, I would venture that this may be an issue more related to this type of game, or Unreal Engine 3 games in general, rather than this game in particular.
The Linux native version is pretty good. I didn't have any issues at any point during gameplay. Hopefully it will leave beta status soon.
Everything seems to work on Proton 6.3 and latest game update.
Videos work out of the box. Improvement boost from earlier ~100 FPS to currently ~ 130 FPS. All in all impressive improvement with latest update.
Works pretty well. Default Proton chosen by Steam.
Full playthrough of Towercall campaign (around 11 hours). No crashes, no issues.
Playthrough of main story, 6 hours, ZERO issues ;)
PS controller is supported, DualSense worked perfectly out of the box.
ENABLE_VKBASALT=1 %command%
Grainy image on Radeon card, seems to be common for this game engine. Graphics can be tuned up a lot without damaging performance. I strongly encourage to disable FSR.
Had to ensure Steam Input is enabled (this is not a problem IMO), that was the only way for my DualSense to work. I think this is the first time I encounter this situation on my PC: I have to disable Steam input in many games.
gamemoderun mangohud %command%
Holds 144FPS most of the time on my hardware, only because that is the max. I set KDE to, and I have to really try hard with moving the camera to make it go lower than 144. The lowest I've seen is 80. If you have Dishonored 2, this runs just as well or better. The graphics are great. It's a very interesting take on Pinoccio, a rather difficult game.
Great game, works right out of the box, better even than the demo.
Full playthrough, including the hidden memories and lots of extra challenges. No crashes, no lost saves, no performance problems.
There is flickering and stuttering, and some other bugs that are clearly present on the Windows version as well. Not a Proton problem.
Stuttering, flickering.
Disabled Steam Input: the game supports playstation controller mapping.
Maintains 90 to 110 FPS on my hardware and default (high) settings, even during web slinging, good to very good to almost unbelievable.
Disabled Steam Input for the game to detect DualSense PS5 controller
Controller support is the only issue that I have managed to find, maybe more to do with Steam than with the game. The game recognized my PS5 controller natively if/when Steam Input was disabled.
Almost flawless stability with one crash. But DualSense (official PS5 controller) experience is far from optimal.
When trying to click the center pad button, either switch to keyboard/mouse is activated or a swipe is detected, which makes it very unlikely to toggle map mode.
DualSense is detected, with and without Steam Input.
Unfortunately, DualSense's mousepad is activated too easily when trying to click the center button, which resulted in me barely using the map at all. Definitely not good for an emergency, minimap shows up maybe 1 out of 5 tries.
Luckily the game was so easy that I rarely needed to use the minimap or spend skill points, but this is not the intended experience.
pw-metadata -n settings 0 clock.force-quantum 512 && pw-metadata -n settings 0 clock.force-rate 48000 && ENABLE_VKBASALT=1 gamemoderun %command% -cpuLoadRebalancing
I had to force rate and quantum with Pipewire.
It is possible to skip the shader preparation phase. But if you cannot, the game can get stuck never finishing that phase, and one must delete the precached files (USHADERPRECACHE) from the steam folder manually.
It looks something like this:
find ~/.local/share/Steam/steamapps/compatdata/1971870/ -type f -iname *shaderprecache* -delete
Most of the problems you may face are common with Windows users. Some of the biggest problems seem to be fixed after latest patch.
- Upscaling doesn't look good in this game. Avoid using it if you can.
- Haven't noticed much difference between DX11 and DX12.
- Have tried VkBasalt to try to make it look better. Not a big deal either way, though.
All of story mode plays, however I would not try multiplayer with what I've seen.
Audio stops during hanging/loading times in the middle of a fight.
When the game hangs in the middle of a fight, it can ruin the whole experience. Even though the game doesn't hang often and 90% of the time it works well.
gamemoderun %command%
Using installer from https://github.com/z0z0z/mf-install.git
Multiplayer matches require dowloading ucrtbase.dll
Multiplayer will work with fix described in https://github.com/ValveSoftware/Proton/issues/2594#issuecomment-833121204
The game can be made to work in both DX11 and DX12 mode.
Tinkers that I needed:
- mf-install: for movies not crashing.
- ucrtbase.dll: so that multiplayer games would not disconnect.
- Force using Proton 7.0-2: so that movies would be in sync.
- Disable screen lock / screensaver in XFCE.
As some other reports have mentioned, movies can crash the game AND your GPU, which is very bad news. In XFCE, this seems to be triggered by the fact that screen saver/lock pops up, so I disabled it while playing the game.
The game is perfectly playable, the issues I met are well known also in Windows.
Audio interrupted sometimes while still loading scenario in-game.
The game is known to be poorly optimized, this applies also to Windows.
In my case I had only 1 crash in 31h of gameplay. The game is just not a very good PC port. Some players are using mods, but in my case I thought this wasn't that bad, it wasn't necessary.
Playable, but with notes.
From Steam Input, invert X and Y axis on the right joystick. The default right stick behaviour seems to be opposite to most twin-stick games.
That surprise VC++ redistributable installation dialog requires using the touchscreen, or perhaps plugging a mouse.
Fullscreen works, but it is difficult to get it to fit to the Steam Deck's screen.
In display settings, switch to full screen and change resolution to highest available. My advice: use Steam Input and invert both X and Y axis on the right joystick.
Possible to play Galactic War but that is maybe 6h. worth of gameplay. Multiplayer is most of this game, and it's mostly unplayable.
Prevent a black screen by enabling fullscreen under ".local/Uber Entertainment/Planetary Annihilation/window_settings.json", following forum recomendations.
- Menus not appearing sometimes during gameplay.
- The whole map whitening out, forcing you to wait for a while until color comes back.
Multiplayer custom map: the whole map can be whited out, making it near impossible to play.
Multiplayer 1v1 matchmaking is unable to create a game. Custom game can be joined, but graphical glitches make it virtually unplayable.
Videos won't play.
Forced Steam Linux runtime was not needed in Ubuntu, but it was necessary in Arch-based: Manjaro, Garuda.
Some graphical glitches can be avoided by disabling HDR in game settings.
For a game that is mostly multiplayer, the multiplayer bugs are a deal-breaker.
Default Proton, perfect performance, zero issues.
For some reason, Steam warns you of limiter controller compatibility. I'd say this game is perfectly compatible with the PS5 controller, including feedback and color changing with health.
VKD3D_CONFIG=dxr11 gamemoderun %command% -dx11
Audio interrupts while loading, happens less in AMD/Radeon when forcing DX11
Save games sync between devices work correctly. Steam Input disabled to get DualSense controller recognized, and really recommend DualSense with this one. The haptic feedback, the way that this game uses adaptive triggers, it's great. Performance and audio cuts improved noticeably when forcing DX11. I didn't need FSR. In any case, I recommend adjustments to get high FPS, this game demands it.
1 crash in a cinematic, out of 26 hours of gameplay. Very acceptable.
The online for this game is rather laggy, but this is not an issue with Proton.
If movies are not skipped and the wrong version of Proton is used, the game could crash.
For 95+% of the game, the player won't find any issue.
Controller kept rumbling permanently and game eventually froze
1 crash around the 15 hour mark. Retried with reflections disabled.
I tried to see how far I could get without disabling reflections, as others have reported. I got nearly to the end, but unfortunately I got one crash and that is a no-no. However, crashes seem to be so rare in this game that I don't think it's a factor.
Multiplayer is a very important component, especially when there is no campaign.
Multiplayer does not work reliably.
Apparently, the multiplayer issue has the usual fix for vc++ redistributable version. Really, this is too cumbersome even to test that the fix works, especially in a game like this, where a scenario is so long.
Playthrough of the two campaigns, no issues.
Alt-tabbing works. Multiplayer may also work, but couldn't find games.
Everything works, but performance was barely playable.
30 FPS or thereabouts, the game is barely playable.
Didn't do any workarounds and didn't need the ping workaround. However, there are probably tweaks needed for the FPS to be playable.
32-ish hour playthrough of full game, no crashes, slight audio problems for which I described possible cause / workaround.
With the in-game tactical pause (shift) I had crackling sound problem on my Radeon card, which seems to be mostly solved by keeping the in-game FPS limit turned off (it's off by default). There are reports of this problem also on Windows.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command% /fullscreen 1920 1080
Crackling after long (>1h) playing sessions
Some missing textures after long (>1h) playing sessions
I was able to get FAF client running on Linux, however the client was not able to start games due to missing init.lua file. Since this is where almost all multiplayer games are played, the multiplayer is not functional.
A working FAF client is crucial to this game, as it provides a platform for the vast majority of the community. However I won't count it in my review as it doesn't come with Steam.
HOST_LC_ALL=en_GB.UTF-8 gamemoderun %command%
Unable to play online.
Online functionality is the main attractive of this game. Single player content is mostly a preparation for online matches, which disconnect on Linux.
Moreover, the Linux player will have previous disconnects shown in their profile, making them less desirable matches even if/when they switch to Windows.
Setting the record straight. Online works now. Everything OK, game on the way to Platinum.
HOST_LC_ALL=en_GB.UTF-8 gamemoderun %command%
Quite common in UE games if your GPU is also your audio device, nothing specific to Tekken.
I disabled Steam Input for my DualShock-compatible/DualSense controllers. If you must use upsampling on AMD, I recommend TSR. The game doesn't have PlayStation layout detection, but there are reports of the same issue on Windows as well. Keep in mind that most of us are not using standard Sony gamepads for this game.
It's great that a game like this can be kept alive thanks to compatibility layers and updated netcode.
gamemoderun %command%
I had to disable Steam input for PS5 controller.
Multiplayer works like a charm, and it is great to see so many players for this game.
Probably a good idea to set full-screen in the in-game graphical settings. The game will not launch full-screen since it is pretty low resolution.
Great experience including online multiplayer.
Functioning multiplayer, with enough people still playing.
Short, green flash, when a video should have played. This blocks from story mode content.
gamemoderun %command% -v
Videos would not play under any circumstances.
Definitely tinkering needed. The -v parameter will skip the initial video and thus allow you to start the game. However, this forces you to miss story mode content.
Either videos could never work in my distro, or else don't work with 7.0-6. Cannot get videos to play, not with older Proton versions, not with MF install script.
Videos are finally working under Proton Experimental, removing the blocking of story mode progress.
As I wrote in my first review, story mode is very important for a game when it does not have that many players online. Now that Proton Experimental has changed the way videos are played, I can set the record straight.
Capped at 60FPS, but it maintains stable 60 FPS with all settings maxed through the whole thing.
Requires proton-ge-custom for story mode, otherwise some movies don't play.
25 games, not a single crash so far.
Alt-tabbing works. Team pass I works out of the box, all characters playable. Note: I have not needed the VC++ redist patch.
Unreal engine game, works like most other fighters. But performance on battery is slightly better than other fighters. I can adjust game settings so that I can set my laptop to ~40W max. power and this way get >2h battery life while maintaining 60 FPS. I cannot do that with e.g. Guilty Gear Strive, nor most modern games.
Same old problem with video (codecs?) as of last game patch (2.41) and latest content update.
%command% -dx12
Hard to tune down graphics to the point that one can get consistent enough 60 FPS, this is a requirement for multiplayer.
Constant 60 FPS is rather a requirement due to rollback. Of course you can play locally offline at 30 FPS, if that is comfortable, but the online software will give you serious problems.
It's important to clarify that "not being able to watch videos" means that the game (story mode) freezes, does not respond to input (other than alt-tab), and you have to force-stop it from Steam, so it really is unplayable. You can test whether videos work on gallery mode, and avoid a game crash that way.
Both on Steam Deck and desktop, still I am unable to watch videos unless forcing DX12, none of the Proton versions seem to help.
Multiplayer also works! 47 hours and pretty big battles, and not a single crash. Take that, Total War!
gamemoderun %command%
Alt-tabbing from full screen on KDE works, but you must click on another screen a second time to really switch.
None of the cinematic videos played with any Proton version that I tried.
None of the intro/ending videos played in any Proton version I tried. Everything else seems to work. I think there are only two videos, though.
Basic gameplay is good, good performance, although sadly it's CPU single-threaded. The GPU seems to be pretty well utilized.
On this hardware, in a typical skirmish game, I am getting average 70 FPS with a dip down to 37 FPS in the 1% low, and then down to 17 FPS in the 0.1% low, so 17 is about worst frame drop I get.
Multiplayer works, although it may take half an hour to even find a game... and that was when there were 2000 players online.
DXVK_ASYNC=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 gamemoderun %command%
render_system "dx12" to "dx11" in steamapps/common/Riftbreaker/conf/initial_config_win.cfg Configuration utility does not launch from Steam, the link has been broken for a while.
Since Metal Terror DLC came in, roughly 20% less FPS on DX12. However, DX11 performance remains as before.
2 crashes in 32 hours, very acceptable
PS controller is not detected immediately, have to wait for some seconds during which the cursor keeps moving on its own. Sometimes I have to move with the keyboard to get it un-stuck.
I have some experience with Exor games on Linux, played X-Morph for a while, mostly trying to make it not crash. Played Riftbreaker since launch and have used its benchmark quite extensively. The crashes are not zero but not as many as a year ago. Overall the situation for this engine on Linux has improved considerably.
Runs basically like native.
Must enable Steam input for DualSense controller to be detected. In case of an update, game may need reinstalling.
Linux native save games not available on Proton, probably also vice-versa.
Works well in Proton. However, it also works well in native version. Since the saved games from Linux native are not found, it is unlikely that players will use Proton.
Steam Linux Runtime
Tried out other community layouts
40 FPS limit give a very promising 4h+ battery life on the SD OLED.
The newly introduced CA launcher hides the crash of the second launcher (Feral's launcher). Has to be debugged through CLI instead.
Font slightly too small
After recent updates, you must use some compatibility option, either Linux or Proton.
The hardware is ready: very stable 40 FPS, decent battery life with projected >4h on the OLED, excellent graphics, the trackpads make gameplay feasible.
The software is not ready: this game is just not controller-friendly. Font size too small, none of the layouts is good enough, too many options and small spots to click.
Excellent shooter for Steam Deck.
With the game's gamepad support, auto-aim, and gyro, (and the shotgun), this is the closest I have been to using my Steam Deck as a main device for a first person shooter. Unfortunately, I still need mah mouse to headshot, which this game seems to require at times.
Only 2 hours and 2 "dungeons" visited so far, this is an excellent game for the Deck.
Controller support is excellent for a first-person game and battery drain is reasonable, and can be tweaked a lot.
ENABLE_VKBASALT=1 gamemoderun %command%
I have had rather stable framerates for the most part. No issues with cutscenes or most of what I've read in reviews. But there have been several updates before I started playing, so I assume many issues have been solved by the time I started.
Full campaign playthrough and some more.
Finished online mathes, no issues.
This is a great out-of-the-box experience and, for a 2008 game, Proton makes a great use case for game preservation in this particular case.
Benchmarks 170 FPS all settings maxed, better than native.
Missing textures after long play sessions.
Was able to complete all games without issues.
Proton version needed for multiplayer, cross-platform play not supported.
If running native, must use Linux runtime. If running native, must have the -tcp launch option. The option is added in Feral launcher, not in Steam configuration nor desktop launcher.
Proton version is needed to find multiplayer matches. However multiplayer games seem to always crash to sync error.
Sync failure always on multiplayer
Native version runs fine. But gameplay is limited to campaign. The native game does not support cross-platform multiplayer with Windows and that means 99% of other players online.
In Ubuntu, disappearing mouse cursor can be fixed. Alt-tabbing should be avoided. Otherwise it's fully playable.
-fullscreen
Missing textures after alt-tabbing
Flickering mouse on fullscreen on Gnome, Ubuntu
Flickering mouse pointer, could only be followed while moving
The out-of-the-box experience in Ubuntu is not good for this game. This is because Ubuntu has Gnome as default desktop. A disappearing mouse pointer is a deal-breaker in this game (it's mostly played with mouse), therefore it must be fixed somehow. I fixed it by switching to XFCE. Windowed-mode is another fix, but not an acceptable solution for this game. This is because the most common method of moving the camera around is just sending the mouse cursor to the screen edges, and that won't work in windowed mode.
Game freezes too frequently it's unplayable. Tried the ESYNC setting but it doesn't make difference for me.
Game freezes during campaign cinematic, does not recover
Saves are not kept in different proton versions.
Very frequently, freezes rather than crash.
Updated my report as I can now play a full campaign scenario + cutscenes with no issues.
Great that this is now playable on Proton, more importantly, just in time for Steam Deck!
So far, a perfect game for the Steam Deck. Looks glorious.
Max 60 FPS on SD OLED, meaning: brought down max FPS from 90 to 60
This is so far the best fit for Steam Deck of my Steam library. This is where it's at. I can get away with 60 FPS because, even then, the expected battery life remained at over 4 h. The game runs smooth even during the big waves and boss battle.