Ramelstag
Published
gamemoderun mangohud %command%
Crashed once when alt tabbed, read that someone also had that happening, switched from fullscreen to borderless windows and that seems to have fixed that.
Proton-GE not necessary. Some time ago, Nvidia had borked the game but now it's fixed. Performance is pretty good, not as good as i had on windows but it's perfectly fine, lowered some settings from high to medium and i get 70fps or more at all times, even inside stations. However, i have a rather low display resolution (also had to disable FSR being on by default because it made the fonts barely legible), so, if you have a 1080p display or higher make sure you have something beefier than a 1050 Ti and a 4th gen i5. Even my joystick is working, i just had to go in the control settings, and select a preset, such as generic joystick, otherwise there was no inputs and i thought it wasn't picking up my joystick.
Proton outperformed native
Keybinds that normally use left alt are using right shift for some reason
Always fun to see windows versions under proton outperforming the native version. Except when it's necessary like in CS2. I tested the vanilla game with the same settings, and a fairly consistent benchmark of launching the Kerbal X straight up and stopping the benchmark as I reached 70km. Also tested three different protons, all had the same performance. According to another report, EVE WILL BE BUGGY/NOT WORK on the NATIVE version, so, it's good that the proton outperforms native, if native has that issue. The only weird thing is that left alt thing, I thought it would only happen on the native version but it also happens on the windows version, which is very strange.
Performance hit is larger than the average translation layer performance hit.
NO EAC MEANS NO MULTIPLAYER!!! It seems the game has gotten more playable, according the older reports. The performance i got with my 1050ti was good enough to enjoy singleplayer/pve, but, i'd be in a huge disadvantage if i were to get in a short range fight with another player. Good thing is, almost everyone has hardware FAR better than mine, and thus, despite the larger performance hit, the average player nowdays would probably get plenty of FPS to be competitive with. Also, the FSR 2 implementation in this game seems pretty good. Regarding multiplayer, people need to ask the devs to enable EAC on Linux, just gotta hope the devs or the windows users won't go "waaaaaah there will be cheaters waaaaaah". (as if there weren't cheaters already... even kernel level AC's aren't bulletproof) I was also getting really bad stutters, but, i didn't mention that on the performance part because im 95% sure it's because i have it on an old HDD, and the game asks for AT LEAST an SSD. So yeah, don't play this on an HDD.
Tested the demo, works good, no issues here
Played on high preset, highest preset made performance not good enough. Got on average 90 - 110 fps, with the lowest being on the 60's at the heavily forested island you start in on the demo. This was under proton, only noticed it had a native port after I decided to quit testing. No idea if the native version runs better.
-dx11
expected better performance with my hardware but it's okay
Noticed an update, decided to try it, with experiemental it didn't work so i tried with GE9-3 and it actually worked. GE9-4 probably works too but i didn't feel like updating mine. i was able to start the game, have the game not freeze on "start game", was able to log in, and for real, start playing. on my first attempt there was an EAC error but i tried again with proton-ge and it was fine. i played the tutorial and then played high seas (standard online game mode), sailed around for roughly 15 minutes, didn't get kicked or banned. i would have played for longer, but, i ran out of time and gotta bugger off.
Also, very important note, I AM NOT using glibc-eac. So, no need for that which is absolutely fantanstic.
Menus, and the main menu have no sound but in-game, audio works almost completely fine, it had a bit of crackling, but only when i had just joined the world, and, a few minor sounds like button clicks and block plops are missing. idk if that audio dll workaround fixes that, i'll try it with tinkering some other time and make another report.
Slight weirdness, i tried joining two servers, one of them was a small, empty one, and the other was one of Keen's official servers, the latter crashed Kwin on the first time i tried to join but later i was able to join, experience was kinda rough tho. but i think it's because i have the game of a buggy, ntfs hard drive.
So, decided to try it OOTB with proton-ge9-1, and, it certainly does look like there were patches for this game on GE. Maybe some other day i'll try the protontricks dotnet and that audio dll thing workarounds, to see if i can make the experience better. i haven't tried mods, but it feels like they'd work. If i were to move the game to an ssd with a proper linux fs, i'd be more than fine with this experience, especially because i play this game pretty much exclusively singleplayer.
still a little bit of crackling but only when stuff is initially loading
still pretty buggy
This was supposed to be a follow-up of my previous report, but this time with tinkering, but, I checked the patch notes for proton-ge9-3 and there was an audio patch for Space Engineers, and, now, the game's audio is mostly fixed. there still a bit of crackling but only when loading stuff. There's button clicks and main menu theme now. It seems like the protontricks dotnet workaround is not necessary anymore unless it is needed for more things which i am not aware yet, i haven't tested mods yet.
-skipintro -useallavailablecores
protontricks 244850 --force -q dotnet48
it still takes a big performance hit
PROTON-GE FIXES THE AUDIO ISSUES. This is an update to my previous report, this time i had the game on an nvme drive, albeit it a relatively slow one, gen2. My previous report was on an hdd, and, it definitely becomes a lot more playable on the nvme, so, i'd say to use at least a sata ssd. Multiplayer still seems like a gamble. this time i used the dotnet48 workaround, and, it definitely improves performance but i hear it can cause further instability. maybe if your hardware is better than mine (very easy to far surpass my hardware), it's gonna be good enough without dotnet48. to me it already felt good enough without dotnet48, but i don't know how that would hold up on a longer playthrough. If you have 4gb of vram, reduce textures to low, if you have 3gb, reduce it to low and limit dxvk max chunk size (see dxvk config in their github) to 4, otherwise you could run too low on vram. im way too lazy to put together some mods, but i feel like it could handle it. I have no idea if that useallavailablecores flag actually does anything, everyone in here is using it, but, people have a tendendency to just copy and paste launch options that often have no meaning, but, this one can't hurt i suppose.
gamemoderun mangohud %command%
Because of my outdated GPU I have to use the 470xx drivers, which prevents me from using ProtonGE or Proton Experimental because the current version of said runners require the 510xx drivers. :( Using the OpenGL translations instead of DXVK had very similar performance, but, there was a small graphical glitch regarding the Scanner. So, I just used the latest proton which wasn't GE or Experimental. The only weird thing that I noticed was the cursor, which looks a bit weird, but, that is completely irrevelant. Great results.
gamemoderun mangohud %command%
Due to my outdated GPU I have to use the 470xx drivers. This makes me unable to use Proton experimental and ProtonGE because those require the Nvidia drivers 510xx or Mesa 22.0. Otherwise, it wouldn't run without telling it to use the DirectX >> OpenGL translations, which suck. So I went with Proton 7 which allowed DXVK and then got a perfect performance, reaching my target 60 FPS at basically all times,
