atlas_core
Published
If you don't have friends, sure, this is a fine way to play. If you do have friends, you're gonna have to play on Microsoft Garbage.
%command% -dx11
Only during a cutscene, and only happened once. Interestingly, the framerate was still fairly consistent even though audio/video was choppy.
The game is still playable overall, and that might have been due to the fact that I was playing on DirectX 12 (or on Proton Experimental before switching to GE-Proton), and playing around in the settings didn't fix the slowdowns. It seems to only happen when rendering certain objects. I wouldn't make a big deal about it, honestly.
Multiplayer just doesn't work, and that's about it for issues on Linux, really. Maybe some slowdowns here and there, but not much.
Switching focus to another window completely breaks it (breaks the master loop?)
It runs surprisingly great considering my mid-range hardware. No issues with VRAM yet (although it is true that I haven't played much of the game yet). Again, don't. switch. windows.
As long as you play with a controller, it's Doom 64! Just avoid using a mouse with a high polling rate...
The game itself, and all rendering methods, were perfectly fine, even cranking all of the settings to the max. But whenever I moved the mouse, the entire game would slow down, so if you're using a mouse try turning down the polling rate like other reviews suggest, or.. don't use a mouse.
Again, the mouse is the biggest issue, and to some (or most) people that might render the game unplayable. The game itself is alright though, works perfectly! For the mouse/keyboard issue, here's an easy fix; just plug in a controller, maybe get Steam Link on the TV and get to shooting demons! IMO playing that way is more fun than with keyboard and mouse.
Without the SDL2 fix (pointed out by Vortex Acherontic), definitely not. With SDL2 updated though, definitely.
As a user named Vortex Acherontic recently pointed out, replacing SDL2 with an updated version completely fixes the mouse input lag issue (where you would move your mouse and the game would stuter). Although I will say, that is a complete non-issue whenever I tried playing this with a controller; Steam Deck (or Nintendo Switch tinkerers, idk) users will have zero issues, and this probably won't be needed.
Fixed after updating SDL2
As a user named Vortex Acherontic recently pointed out, updating SDL2 fixes the mouse stutter issues that were experienced (frame stuttering when moving mouse). This isn't necessary for people who just want to play with a controller, though (Steam Deck users, for example).
After the long hassle of setting it up, I think an average user would have a butter-smooth experience with this game. Would recommend.
PULSE_LATENCY_MSEC=60 PROTON_NO_ESYNC=1 %command%
I tried so many fixes listed with other reports here, I eventually got it to work. I don't know what exactly fixed it, though.
Sometimes, swapping from Windowed to Fullscreen would freeze the game: being forced to close the game, then launch it back. (fuuun...)
Without multiplayer, yes, that's half of the Halo gone, but the rest is quite good.
Basically no multiplayer: even tried launching with/without anti cheat.
Logging into Xbox felt a tad weird, but it worked.
Changed right trigger to the A button. For comfort.
It seems that audio clips out significantly when a lot is going on, making a distorted mess. That might be the game, though.
I had to install this game on my root hard drive: installing on an external drive (or my other SSD) would lead to the game not launching.
Steam SDL2 with Wayland, currently, is completely borked with no way of recovering it for Proton games.
Tried replacing SDL2.dll with that of Quake (first game, rerelease)
Running on X11? Great! The game will run flawlessly. Running on Wayland? Forget about it; lost cause, not even telling SDL2 to use the X11 backend will work, not even preloading whatever SDL2 library will change anything.
SDL_VIDEODRIVER=windows %command% -vulkan
5.1 audio worked flawlessly, using a tiling window manager (if a bit finicky due to the game capturing the mouse cursor) to tile the game window worked without a hitch, Steam Input worked fine... Really, it's Quake II. My prior issues were probably that of general SDL2 on Proton, I believe it was simply trying to run the Wayland backend which, in a Windows environment, does not exist. Setting the env variable immediately fixed that issue however.
Severed Steel, 95% playable on Linux (exception being cutscenes), but still very playable!
With VSync enabled, the mouse would have noticeable latency in the main menu, had to disable that.
It's very likely it's only a me issue, but running Severed Steel on i3 and X11 seems to give it a lower framerate than it should, even with picom disabled. The FPS counter was still showing above 50-60 FPS though.
Cutscenes seem completely dead on Linux. I can only see the color testing "no signal" image screen thing.
no option to turn on RTX/DLSS, although I think it's just DXVK just not supporting it. plus, I'm on an AMD GPU (although other reports seem to also not have that option)
the window/process name is "ThankYouVeryCool", ha :^)
Curious why Valve hasn't whitelisted this game yet: it's truly flawless. Just pop Proton 5.13 on there, and you're up and running.
Worked even with a Steam Controller. Did not expect that, to be honest.
Basically the same as running on Windows (if not better): flawless. Even on the Experimental branch, with mods. Truly amazing.
Sometimes the mouse/camera movements would feel.. not smooth. Rarely happened, though.
The game itself runs absolutely great. It's just the EA app that's an absolute hinderance now.
Northstar requires modifying game files/executables. Campaign does not however.
Occasionally would shadows on characters be bugged. Like, I could see some square lighting messing around, not rendering shadows properly. Infrequent and very minor however, I have to go out of my way to observe it.
It seemed to be a bit iffy, but KDE Plasma on Wayland makes Alt+Tab work just fine in fullscreen.
The EA app will sometimes crash out of nowhere after the game is done and when the launcher tries to close. I don't know if that's just EA being EA (bad).
Proton 7.0 would not let the game open, I don't know what's up with that; perhaps it is because I'm running the game off an NTFS drive (although I have symlinked the compatdata folder so the wineprefix shouldn't be an issue). And also, the EA app sucks. No really. Just saying it's the absolute worst thing left on the sidewalk to rot would not describe how much I hate it. (Even on Windows, it's worse.)
MANKIND IS DEAD. PROTON 6.13 IS FUEL. I have no more jokes here, just play it.
Sometimes jumping between Windows 10 and Proton with Steam Cloud would unequip some things. That's probably an ULTRAKILL issue though, I dunno.
Framerates would sometimes be lower than expected, or at least for the visual graphics.
It *can* be a hassle to install GE's Proton fork, but once everything is done.. It's Warframe.
Sometimes, ALT+TABBING out of Warframe to, say, Discord, wouldn't work: it would only work on the "pause" menu. Though this happens too on native games such as Half-Life 2, so not sure if that counts.
Other Proton versions worked (4.2 and 4.11), but they all had some performance issues. It still is playable, but with GloriousEggroll's fork, it's the best play.
