Open zrooda opened 2 months ago
For me usually on the 2nd try of starting a new game it does not disconnect.
The main issue I run in to is that the game gets stuck on the loading screen when resuming the campaign. It runs fine until I quit the game, after which I become unable to resume the campaign. I can however still start a new game.
Update: I think I found a workaround, disabling internet seems to allow me to launch a solo game.
The game also crashes any time I receive a Steam achievement.
Update 2: Actually, maybe the disabling internet trick does not work, and I just got lucky a few times.
Update 3: Disabling the Steam overlay solves the crashing issue. I managed to do a full playthrough with this workaround. Game may still crash on shutdown but otherwise works fine.
Just to be sure, you have the Proton EasyAntiCheat runtime installed, right?
Just to be sure, you have the Proton EasyAntiCheat runtime installed, right?
Sure, the install script will add it either way if you don't (my mistake this is false, the runtime isn't automatically installed). FWIW I can run other EAC games fine - Elden Ring and Hunt: Showdown from what I have installed atm. I guess I can try reinstalling the whole thing. You can run the game I presume?
For me usually on the 2nd try of starting a new game it does not disconnect.
Interesting. I'm getting 100% failure rate, always in the same spot when the camera shows the green goo cannister. Tried with various Proton versions probably 20 times.
I've cleaned the prefix and reinstalled EAC runtime but unfortunately the "Failed to connect" problem persists 😢 The install script for the game seems to correctly set up both EAC and EOS as far as file structure, although I couldn't find any specific logs from the process. FWIW I've also connected the game to the PROS account, seems that can't be easily disconnected again - might or might not be related.
At this point I'm out of ideas, hopefully someone chimes in. The perks of early access on Linux 😄
Replying to https://github.com/ValveSoftware/Proton/issues/8072#issuecomment-2332663938
I was looking into getting regular version but it looks like the game devs didn't put on the game page that it uses Epic Online Service (Lots of bad reviews because of that) so maybe Steam wouldn't install it automatically, but if you are playing Hunt, you should have installed.
So for me using GE-proton 9-4 and turning cross play off under Game settings seems to make everything work fine.
started a new game and saw no disconnect message
Disabling Steam Overlay works! 🥳
(Settings > In Game > uncheck Enable Steam Overlay while in-game)
Finally could give it a try, and as the others, needed to disable Steam Overlay to make it work (Suck, because this games deserves getting some screenshots...) and crashing when closing it, have to stop it from the Steam client
This game seem to also affected by https://github.com/HansKristian-Work/vkd3d-proton/issues/1406.
launching the game with VKD3D_CONFIG=no_upload_hvv %command%
have ~20% fps improvement for me.
Can confirm a performance improvements with that flag! :D
Can confirm a performance improvements with that flag! :D
didn't work here, on windows the difference is 30% , but i think the issue is the nvidia linux driver and directx 12 , not really related to proton.
I've encountered another issue with space marine 2. For some reason when certain light sources are present on screen, weird green and red artifacts can be spotted on the edge of the screen when moving the camera. Here is a video displaying the issue.
My specs:
✦ ❯ glxinfo | grep "OpenGL version"
prints "OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.0.7"the game launches but once the cutscenes stop and I'm about to be handed control over character the game freezes with weird graphical artifacts
Replying to https://github.com/ValveSoftware/Proton/issues/8072#issuecomment-2349260726
looks like we have similar GPU + nixos, might that be some configuration problem with nixos?
Haven't seen any weird artifacts on the prologue and first level on:
7800X3D + 7800XT Arch + Gnome + Mesa 24.2.2
Or at least didn't notice, but I see the last messages are all about artifacts and using Nixos, maybe something related to how mesa is build there? Are you using Proton Experimental?
Replying to https://github.com/ValveSoftware/Proton/issues/8072#issuecomment-2350138190
yeah it's proton experinental. tbh its a pretty fresh install, im still trying to figure out how it's configured, i might be missing something
✦ ❯ glxinfo | grep "OpenGL version" OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.0.7
✦ ❯ glxinfo | grep "OpenGL version" OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.0.7
That's kinda outdated mesa
Replying to #8072 (comment)
looks like we have similar GPU + nixos, might that be some configuration problem with nixos?
Cant say, I havent changed anything bout my mesa config. This would be my config.
Haven't seen any weird artifacts on the prologue and first level on:
7800X3D + 7800XT Arch + Gnome + Mesa 24.2.2
Or at least didn't notice, but I see the last messages are all about artifacts and using Nixos, maybe something related to how mesa is build there? Are you using Proton Experimental?
I mainly see the artifacts when moving the camera, I thought maybe my GPU might be dying, but I experience no such artifacts in other heavy games. They only appear during fast mouse movement and only in indoor areas where warm light sources are present.
Haven't seen any weird artifacts on the prologue and first level on: 7800X3D + 7800XT Arch + Gnome + Mesa 24.2.2 Or at least didn't notice, but I see the last messages are all about artifacts and using Nixos, maybe something related to how mesa is build there? Are you using Proton Experimental?
I mainly see the artifacts when moving the camera, I thought maybe my GPU might be dying, but I experience no such artifacts in other heavy games. They only appear during fast mouse movement and only in indoor areas where warm light sources are present.
Have no idea of Nix, you sure you using RADV and not AMDVLK right? I saw the env var to be setted correctly, but also AMDVLK installed?
Reply to https://github.com/ValveSoftware/Proton/issues/8072#issuecomment-2351557454
AMDVLK is currently disabled on my system, games are running through mesa/RADV.
Replying to https://github.com/ValveSoftware/Proton/issues/8072#issuecomment-2350082785
Got the exact same issue: OS: Arch Linux Host: ASUSTeK COMPUTER INC. ROG STRIX B650E-I GAMING WIFI Kernel: 6.10.10-1-cachyos Mesa: 24.2.2 Resolution: 2560x1440 WM: KWin CPU: AMD Ryzen 7 7800X3D GPU: AMD ATI Radeon RX 7900 XT/7900 XTX/7900M Memory: 12176MiB / 64015MiB
For the moment got it to work switching to AMDVLK instead of RADV.
This game seem to also affected by HansKristian-Work/vkd3d-proton#1406. launching the game with
VKD3D_CONFIG=no_upload_hvv %command%
have ~20% fps improvement for me.
Adding that flag has no affect for me on my Nvidia 3090 with Proton Experimental.
I am also getting a long hang and then crash whenever I quit the game. Most of the time I get this dialog message.
Other times I get the crash reporter.
Replying to https://github.com/ValveSoftware/Proton/issues/8072#issuecomment-2357723450
To me on AMD game always crashes on exiting, have to stop it from the steam client. That flag helped me somehow for the game to make better usage of my CPU and GPU, if you were already CPU bounded it probably won't do anything.
I finished the campaign, what a bummer not to have the Steam Overlay, I would just non-stop make screenshots of it
To me on AMD game always crashes on exiting, have to stop it from the steam client. That flag helped me somehow for the game to make better usage of my CPU and GPU, if you were already CPU bounded it probably won't do anything.
The flag is for CPU bound. It trade gpu performance with cpu performance for some game, and it is for disabling rebar in vkd3d.
Check the issue https://github.com/HansKristian-Work/vkd3d-proton/issues/1406 for more information.
After 3.0 patch game doesn't playable in online mode. Looks like EGS services do not work anymore.
Online doesn't work on Proton 9.0-3 or Experimental or latest Proton-GE
After 3.0 patch game doesn't playable in online mode. Looks like EGS services do not work anymore.
Online doesn't work on Proton 9.0-3 or Experimental or latest Proton-GE
Not sure if because of not connection to EGS at all or if something fixed on the update, but the game is exiting fine now at least...
After 3.0 patch game doesn't playable in online mode. Looks like EGS services do not work anymore.
Online doesn't work on Proton 9.0-3 or Experimental or latest Proton-GE
Sigh.... Here they go again. It's really frustrating honestly. I was so excited for the new patch.
Steps I've taken:
Running OpenSUSE Tumbleweed, everything up to date.
Look like AVF error is not linux only problem.
There are few message said they have this error on windows example.
Most seem to be on linux/steam deck though.
Looks like everything that using online features doesn't work. Even PROS account. EGS account doesn't work too. PROTON_LOG=1 says nothing. Maybe there is another way to get some information.
I'm not sure if this is a good moment to get more info on the Steam Interface with the game, now the game can boot with the interface enabled, but it will just freeze when trying to open it
There's a bug report on their forum for the AVF error. Please upvote/comment if you're experiencing the same issue
Am also getting the AVF error, unable to use online play. proton log: steam-2183900.log sysinfo: https://gist.github.com/zaggynl/4d4649e98bcf1cf7b32a4945d6dec148
Update:
The response from the developer in the next message addresses the issues originally raised in this post now.
Dev just posted a announcement on discord that the issue linux/steam deck will be fixed next patch.
Regarding the black screen issue occurring on Oceania servers:
We are aware of it, the dev teams are on the matter at the moment. We'll let you know when we get a fix.
For the Linux/Steam Deck issue:
The next patch should fix the launch issue on Linux and Steam Deck.
<@&1242516345237798942>
Replying to https://github.com/ValveSoftware/Proton/issues/8072#issuecomment-2393686524
No expected date for that patch?
@alosarjos Nope, just this.
No date yet.
Hotfix 3.1 is released.steam link.
Space Marine 2 - Hotfix 3.1 Hello Space Marines!
We just pushed a small hotfix that brings various fixes. Thank you for your support!
Patch Notes
Fixed several crashes Fixed heavy stutters on some CPUs Fixed launch issue on Linux and Steam Deck Fixed issue with dynamic resolution and ultrawide screens Fixed issue with upscalers using wrong resolution parameters
Edit: Still getting AVF error. verifying game files.
Edit 2: Still getting AVF.
Edit 3:Adding env SteamDeck=1
seem to fix the online issue.From steam discussion
Yeah I just tried booting up in my lunch break. It works with the SteamDeck=1
variable. I can also run it alongside in gamescope by putting the variable in first. My env is SteamDeck=1 gamescope -h 1440 -r 165 --force-grab-cursor -- %command%
It's not the greatest fix, but it works I guess.
Edit: Note that the variable also sets all your in game settings to those optimised for the Steam Deck. If you were running on high graphics settings, they'll be turned down very low. I also don't know about people using Nvidia systems. There may be issues with DLSS, but I can't test this because I have an AMD GPU.
Works for me, and as previously said graphics are effectively nerfed...
Edit: Note that the variable also sets all your in game settings to those optimised for the Steam Deck. If you were running on high graphics settings, they'll be turned down very low. I also don't know about people using Nvidia systems. There may be issues with DLSS, but I can't test this because I have an AMD GPU.
DLSS works fine and AFAICT setting graphics settings back to ultra works, but will shoot out a warning about VRAM when doing so.
EDIT: It seems to be a Manjaro Problem: https://forum.manjaro.org/t/steam-games-wont-launch-after-2024-10-10-stable-update/169230 If someone has a solution, I will be happy anyways.
Unfortunality, the game does not work for me.
I only get a black screen and the game seems then to block my hole PC.
When I use gamescope with: SteamDeck=1 gamescope -h 1440 -r 165 --force-grab-cursor -- %command%
as suggested by @LazyWings the game also just produces a black screen, but at least I can use my computer after the failed start attamped without rebooting.
I tried so far:
Replying to https://github.com/ValveSoftware/Proton/issues/8072#issuecomment-2405735800
Hi - sorry, I've been busy so not been able to respond, but you found out it was a Manjaro/Arch problem unrelated to this. Hopefully that's resolved now. In future, you could maybe try the flatpak version of Steam if you run into any issues like that, until they get resolved.
More generally, I wanted to comment that the command I put is what works for me! I'm hoping most people know this but I know some people might just run into an issue and randomly start throwing out commands and environments they've copy pasted. I was quickly trying to get the game to work during my lunch break that day so just rushed out a response. I should have probably put: SteamDeck=1 gamescope [options] -- %command%
.
For those that don't know:
-h
sets the internal resolution height, defaulting to 16:9 if -w
is undefined. -r
sets the gamescope refresh rate. So that means my monitor is 1440p with 165hz refresh rate. You can launch gamescope at higher internal resolutions and such, but you'll just be wasting resources. --force-grab-cursor
is something I use specifically for Space Marine 2 because there's a bug with multimonitor that breaks the cursor grab. I can still change window and free my cursor, but this just prevents the bug. I recommend it for SM2. gamescope --help
in a terminal for a full list.I also should have clarified that the variable sets your graphics settings to what it considers Steam Deck optimised, but you can change it to whatever you want. I just didn't know whether it disabled DLSS or not, but seems like it just works and correctly recognises your graphics drivers, so it's all good.
Steam overlay is the only major outstanding issue for this game on Linux I believe. Which is weird because the Epic Games overlay works if you link your account.
Steam Deck LCD SteamDeck=1 %command% GE-Proton9-15 "SteamOS Holo" (64 bit) Kernel Name: Linux Kernel Version: 6.5.0-valve21-1-neptune-65-g33487bf05ed3 X Server Vendor: The http://X.Org Foundation X Server Release: 12101011 X Window Manager: KWin Steam Runtime Version: steam-runtime_0.20240806.97925 Video Card: Driver: AMD AMD Custom GPU 0405 (radeonsi, vangogh, LLVM 16.0.6, DRM 3.57, 6.5.0-valve21-1-neptune-65-g33487bf05ed3) Driver Version: 4.6 (Compatibility Profile) Mesa 24.0.5 (git-09d9c2fd7f)
game runs and appears to be stable, but the framerate is unbearable.
devs borked linux again, ever since WWZ this engine in particular struggles on linux smh, already tried 6.11, lts, same issue, crashes while loading a game, was working fine a few weeks ago, steamdeck=1 makes connection error go away but doesn't fix loading.
OS: EndeavourOS
GPU: Radeon RX 6700 XT
Kernel version: 6.12.0-rc1-1-mainline (6.11 or even lts 6.6 no difference)
Mesa version: 24.3.0-devel (doesn't matter, even stable crashes)
Desktop environment: KDE
Proton experimental, bleeding edge, proton-9, doesn't matter which proton version i use.
The game keeps freezing for me at the seizure warning screen. Anyone got a fix for this? I tried the cinematic skip launch parameter and the SteamDeck=1 environment variable without any luck.
EDIT: For some reason disabling cloud saves did the trick.
The game keeps freezing for me at the seizure warning screen. Anyone got a fix for this? I tried the cinematic skip launch parameter and the SteamDeck=1 environment variable without any luck.
EDIT: For some reason disabling cloud saves did the trick.
did you disable the steam overlay ?
The game keeps freezing for me at the seizure warning screen. Anyone got a fix for this? I tried the cinematic skip launch parameter and the SteamDeck=1 environment variable without any luck.
EDIT: For some reason disabling cloud saves did the trick.
As the person above said, disable Steam Overlay. Also turn off Mangohud and any other overlays you might have running. For some reason the only overlay the game likes on Linux is the Epic one. I also recommend Proton Experimental. I've found it crashes the least with that proton version. I've not tried GE9-16 but I had issues with GE9-15 and GE9-14.
This game seem to also affected by HansKristian-Work/vkd3d-proton#1406. launching the game with
VKD3D_CONFIG=no_upload_hvv %command%
have ~20% fps improvement for me.
this isn't a solution and is more of a band-aid. It actually makes heavily CPU dependent scenes run with even less FPS. GPU utilization is a bit better but still far from perfect.
Compatibility Report
System Information
I confirm:
steam-2183900.zip
Symptoms
Game launches fine. When new game is started and the intro cinematic runs (which seems to double as map loading), a message pops up saying "You have failed to connect to the game" in always the same spot. After confirming the popup the game displays a black window with a "Signed in as [USER]" message in left top corner and doesn't respond anymore.
Possibly anti-cheat related? Running
SteamDeck=1
doesn't help.Reproduction
Start new game, watch intro cinematic, always get disconnected.