BuckPrivate
Published
Fantastic out of the box. No tinkering required.
I have my Steam compatibility option set to use 8.0-5, and I had no issues. Everything worked exactly as it did on Windows, and dare I say it, the performance was better on Linux. I recommend using the Experimental Vulkan renderer when you launch the game (you'll see a dialogue box with a bunch of options, and it should be the second one) - this cuts your loading time down a lot.
I was able to play and mod the game in Linux, though the steps to mod are a little more involved than on Windows.
The game played as expected under Proton. I was able to install F4SE and otherwise mod the game using Mod Organizer 2, which functioned similarly to Vortex (Vortex does not run in WINE). Performance was comparable to Windows, with no major boon or deficit.
Works out of the box with no changes!
I made no changes - just installed and ran, and it worked as expected!
Works fantastic out of the box. No complaints here!
I didn't have to make any changes to Proton or use any launch commands to get the game to run. This should work just fine without having to make any changes!
Runs well, except for some small gripes below.
DO NOT run in fullscreen - this will crash the game on next launch. Running the game in windowed borderless is the only way to run it. While it does have an annoying, one-pixel-wide border in borderless, after a few missions you don't notice it anymore. If it really bothers you, you can run it in fullscreen, but swap back to borderless before closing.
Occasionally the game will chug at 15-25 fps; only restarting the game will fix this issue. Sometimes I have to restart the game two or three times, but after that it won't have the issue again for hours. If it happens, it's immediately noticeable on launch; it doesn't happen in the middle of a mission for me.
Besides the weird border and the occasional framerate issues, playing this on Linux has been good. I am able to play with my friends (one of whom is on PS5, the other two on Windows) with the only issue being server issues; typically, the game is more stable on my rig than any of theirs. I can't think of any major, game-breaking bug that would make me not recommend it.
Performance and stability have improved on Wayland.
Game now runs using fullscreen, but doesn't stay on top on launch. You'll need to select the game from the taskbar after launching in fullscreen - but it doesn't crash anymore! I have added the plasma-wayland package, so ymmv if running on KDE Plasma with X11.
If for some reason you want to run borderless, borderless still has the one pixel wide frame around the game.
Game runs as intended on Kubuntu with Wayland for me. I've been able to play games with people on Windows and Playstation with no issues, and the game doesn't crash on re-launch with fullscreen enabled.
Works great! Host an online lobby for playing with friends, as LAN lobbies are not guaranteed to work.
When storing multiple light-casting objects in the ship (i.e., lamps from Rend/Dine, apparatices), the game can slow down significantly (from ~120 fps to ~55). In multiple games, I've had my friends desync as a result, which required a restart to fix.
No problems with online multiplayer! I played with three other friend: with myself on Kubuntu, one of them on a Steam Deck, and the remaining two on Windows, we had no problems!
Could not connect to a LAN lobby. I'm the only one in the house running Linux, so I can only attest to Linux-Windows intercompatibility, which doesn't work.
I've only had the few minor issues I mentioned above, but other than those, this works very well out of the box!
Confirming game does not run
Installed Microsoft .NET 3.5SP1
Various versions of Proton yield a variety of results. Anything after 7.0-6 will launch the launcher. Anything before 7.0-6 does nothing. GE-Proton9-2 seemed to give the best result, with the launcher launching but the game's bootstrapper hanging in the background indefinitely. The game itself never launched, which could be due to the anti-cheat, if I had to guess.
It seems like the game thinks you're double-clicking in certain menus, such as accessing characters or the inventory. It's hit-or-miss, but since I'm not the only one who's mentioned it, I thought I should bring it up.
I was able to use the Nexon Launcher alone to launch the game through Bottles instead of using Nexon + Steam, but I previously linked my two accounts, so ymmv. With the exception of the occasional double click issue, this runs as I expect!
Just set up a bottle for the Nexon launcher, download the launcher from the Nexon site, run the application in your newly created Bottle, and the launcher runs as expected!
Bottles suddenly stopped working for me after the Ubuntu update to 24.04.1. I saw another user's report that Lutris worked very well for them and removed the double-click issue many have mentioned.
Lutris works great for me, and I recommend this route if anyone is having issues running Mabinogi with Bottles! I have no problems running this in Lutris so far -- it's practically perfect!
Game does not launch, even when using Bottles which worked for Mabinogi.
I was not able to boot the game in Steam using any version on Proton, nor could I boot it using Bottles using the same method that worked for Mabinogi. As both of these games use Nexon's Game Guard, I doubt the anti-cheat is the issue.
Despite Mabinogi running in Lutris, MapleStory does not.
Since I was able to get the Nexon Launcher and Mabinogi running in Lutris, I attempted to to the same with MapleStory. However, it looks like something about this game's anticheat is different -- where Mabinogi's launched right away, MapleStory's never does, which causes the game itself to not launch.
I want this one to work, but it looks like it's not ready yet.
This ran perfectly fine for me on the default Proton recommended by Steam (currently 9.0-4). The only issue I had was that the opening cutscene (skippable, thank God) didn't show any video and only played the audio. GE-Proton9-13 fixed that, so if you want the opening scene, that's all you need.
I see people recommend launch options with their reports without explaining what those options are doing. 9 times out of ten, you don't need them, so unless you know what the launch options are doing, don't use any. The options for MangoHUD and GameMode only work if you have those packages installed - otherwise, don't add them.
Certain cutscenes that relate to loading screens (i.e., intro cutscene and the cutscene at the end of the tutorial) had no audio for me. Others, such as during character introduction, worked fine.
Harsh stuttering, which seemed to be random -- as if the game were compiling shaders and/or loading textures. The game would randomly drop from my monitor's 165 to what looked like 20-30 fps. This issue seems to be especially prevalent during the tutorial, but continues throughout the game.
Certain cutscenes are also very choppy -- the main menu background runs like a slideshow for me irrespective of the version of Proton I use. Some loading screen cutscenes run the same way, but this issue is less consistent.
I had a repeatable crash when creating a character -- at the start of character creation, the game would simply CTD when using any version of Proton except 8.0-5. After creating your character, you can switch to any version of Proton you'd like, including the one Steam recommends by default.
Once you get past the tutorial, you've basically gotten through the biggest issues related to stability. Performance issues still persist; however, the game is playable except for some issues with cutscenes and the occasional choppiness.
I previously thought the performance was good enough to play, but the longer I played the worse it got.
Switched to Proton 8.0-5 to get past character creation.
Certain cutscenes were missing audio, especially the intro cutscenes before and after the tutorial.
I had some occasional lag with my mouse - windowing the game and then reverting to fullscreen fixed this for me.
Significant stuttering and framerate drops as if the game were loading in textures. Sometimes looking in specific directions would enhance the stutter; opening Whispers would cause a major ~1 second hang before the Whisper would open.
Running the game on any version of Proton except 8.0-5 would CTD at character creation. After character creation, any version of Proton may be used, including the one recommended by default.
As the game runs right now, it's almost unplayable on Linux. I got significant stuttering in the middle of combat and sometimes textures took forever to load in while wandering around. Valve has said they're working on Steam Deck support for Once Human, so we might see some performance improvements in the near future.
Using Proton Experimental ran fine out of the box. I wouldn't say it's identical to Windows, but it does run well.
Many of the reviews recommend Proton 6.3-8. I do not recommend using that version of Proton; doing so gave me 25 fps in the lobby. Your experience may be different, but that was mine.
I use Proton Experimental for most titles that require Proton. With my hardware, I was able to run 70-100 fps on max settings with Experimental, and did not need to add any launch commands. My only complaint is that framerates seemed to vary wildly, but again, your mileage may vary.
If you aren't comfortable running Proton Experimental (for one reason or another), 8.0-5 ran very similarly to Experimental.
Game crashes frequently and consistently at the beginning of each race. The best I've gotten is the end of the first race -- to do so, I turned off VSync. Since you can't progress the game's content without competing in these races, the game is virtually inaccessible as I experienced it.
I used ProtonGE9-2, Proton Experimental, and Proton 9.0-2 -- for some reason this game just does not want to play on Kubuntu.
I previously said that I was having a lot of stability issues, but after running this game with several different proton versions (read: "thirty minutes of trial and error"), I figured out using GE Proton 8-27 got the game to stop crashing. I was able to finish races and begin unlocking the tech tree.
For some reason, Steam won't clear the compatdata folder if you change Proton versions for this game, meaning you'll need to manually delete it. If you don't know how, it's in steamapps\compatdata, then delete folder "1279510."
If you're having stability issues with this and other games, see BIOS settings below.
Be sure "Above 4G Decoding" and "Enable Resizable BAR" are enabled in your BIOS. I had updated my BIOS and these settings were disabled -- after turning both of these settings on, all recent versions of Proton run very well. I've been running with the default Proton with no issues since.
Game does not launch from the launcher.
SteamDeck=1 %command%
Installed DirectX via protontricks, since the installer bundled with the launcher failed for me.
Hitting "Start" on the launcher just hangs -- the launcher will say "Launching," but the game never launches. I tried Proton 9.0-3 and GE Proton 8-31, and tried the SteamDeck=1 command (since someone here said it ran on the Steam Deck). None of those worked for me.
With the launch options described, the game works exactly as I remember it from Windows. Without them, the game is not playable.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 taskset --cpu-list 0 %command%
Game is virtually unplayable without using these launch options for Steam. The main menu will stutter and freeze frequently. I entered the main menu, but did not attempt playing without these options.
I used the launch options someone else described in these comments. Esync and Fsync are performance-enhancing variables in Proton (I barely know what they are, but thought it might help to provide some insight into what exactly you're changing). For Supreme Commander, this prevents the game from running too fast when you add the next variable, which sets the game to run on one CPU core, removing the stutter.
Multiplayer is still borked. The game does not work as intended on Linux.
Changing fullscreen resolution after launch caused issues with mouse inputs. Specifically, it appeared that the mouse inputs were being limited to the top left of my monoitor - that is, to reach an option in the top right, you would need to position your cursor more towards the top middle of the screen. Restarting the game corrected this issue.
Online multplayer (i.e., Quick Match) kicked me from the match immediately upon loading in. I'm assuming this is because of Ubisoft's implementation of BattlEye, as many others have reported.
I would not bother installing R6 right now. You will not be able to play multiplayer matches unless Ubisoft implements the Linux-compatible version of BattlEye.
Runs great out of the box with the Native Linux version.
No Proton required! Runs perfectly fine out of the box with the native version.
SteamDeck=1 %command%
Game had significant choppiness that was weirdly made worse by running on lower settings. I ran the game on Ultra at ~60 fps, but running at High ran at ~40-50. FSR made the game run better but lost a good bit of fidelity. Stutter was common with or without FSR.
You must use these launch options or the game won't connect to the Warhammer servers. You could probably play the game without the commands in singleplayer; I chose to run the commands to play with friends.
