Ignore this if you’re on Wayland, it doesn’t have this problem. If you have two monitors, X11 throws a hissy fit over varying refresh rates. Ie, your main monitor runs at 144, the secondary runs at 60. If you launch a game on the 144hz monitor, it often locks it to the lowest refresh rate (60 in this example). Double check to make sure the game is actually running at the desired refresh rate (easiest way is to turn off the second, slower monitor and launch the game. 144hz would now be the lowest refresh rate).
Also look into CPU scheduling. Could be locked to a power saving governor. You want it on a dynamic or performance mode. Also check out if Resizable BAR is enabled in your BIOS.
Found this note on ProtonDB that recommends Proton-GE and some tweaks such as setting launch options to gamemodecmd %command% and maybe 120 fps as a cap, some other notes are suggesting the latest Halo Infinite update might’ve affected performance a bit.
Ok I just installed gamemode and made sure it was running and passed all tests. Do you enter the game name where %command% is? so for Halo Infinite it is gamemoderun Halo Infinite ? Sorry if this is a dumb question but game wont open now lol
But thanks for help with command it works for other games.
Edit: have no idea It seems whenever I change whatever compatibility I use it breaks after a fresh install. I have reinstalled the game 3 times now boots first time but as soon as I change anything in breaks and brings that image back even if I revert back to what was there…
Valve can’t distribute the codecs legally, but the community sort of can. VLC for example can get away with it because France doesn’t recognize software patents and in general has pretty good interoperability laws. So the codecs exist in open-source form that you can compile yourself. I think Proton-GE does bundle them, and if not I’m sure someone did or at least have instructions to compile with the codecs. We’ve dealt with wmv files in games well before Proton even existed, well before Valve even supported Linux at all.
For the shaders, it’s a normal and one-time thing. Once they’ve been compiled once they’re cached, and then afterwards it doesn’t need to recompile them and you don’t get stutters. What Valve does there is they collect the compiled shaders and distribute them to everyone so it’s faster. So it’ll be a stuttery mess for a couple minutes and it’ll progressively get smoother and smoother as new shaders will become rarer and rarer until they’ve all been seen once.
Right, I’m familiar with what performance looks like when the shaders aren’t compiled, but is it still the very visible and tangible issue that it was back when Proton first came out, when playing a game through Heroic/GOG? If so, do modern enough games relieve the issue by having the shader compilation step within the game itself?
And as for the distribution of those codecs, does Heroic handle that automatically? Or if I have a version of Proton-GE, does it know to use that version when applicable?
Everything about this seems kinda sus. The website is worded very strangely, makes a lot of big but really vague claims, shits on other OSs, just generally seems… again, “kinda sus” is the best way my lizard brain can describe it.
It still won’t work with Playtron since it also can’t load Windows kernel drivers under Linux.
The only way this could ever happen without also making it work for SteamOS is if they made a deal with Epic to either support user mode anticheat with their OS or to compile and ship ring 0 anticheat with every release of Playtron.
That issue will be true on any linux platform because Epic Games is a nasty company that doesn’t care about consumer friendly practices. How will this device get around that?
Regardless, to say that the Steam Deck is locked down to the steamverse, is such a weird thing to lie about. You can install basically anything on Steam Deck:
Fortnite works (confirmed in beta), both anticheats it uses work, Epic just needs to enable Linux support in the EAC dashboard and ship the library to get EAC to work, and for BattlEYE all that is required is an email. They just don’t care about us.
Is it really worth dealing with Windows’ bullshit to play a native version of a bad competitive shooter from a shitty company, with a controller? It’s not like you can play it offline either.
Is it on a tty in embedded mode? If so does switching ttys using CTRL+ALT+F{1…10} work? Usually the display manager is on F1 or F7. If it’s not in embedded mode, does Left Alt + Enter work?
EDIT: Re-read and realized I didn’t understand completely. You’re starting it with your display manager. I’m not sure how you would kill it in that case.
Remember that experimental is a constantly changing version. When you see users suggesting you set a game to use proton experimental, always check the date, because more likely than not, experimental no longer refers to the same experimental they used.
I’ll test this out and get back to you on whether I can run it.
I installed the windows version from steam. The game does not run under proton 8.0-5, but does with the current versions of experimental and Proton-GE from the AUR.
I did not need to set windows version to XP, or do any other kind of extra fiddling. So all you should need is to set the no DRM launch option in heroic to allow the Epic version to run.
If you haven’t installed that Proton-GE package from the AUR, I suggest doing so. It’s been the only “custom” proton version I’ve needed for ages, it gets updated when a new version comes out and makes itself available for selection in both Steam and Heroic, so it’s a very set and forget way to use the GE versions of Proton.
Still the same. It tries to launch, I get a short blackscreen, and then it crashes again. I have sideloaded it into Heroic, and the log stops with these two lines:
INFO: [Frontend]: Refreshing sideload Library
WARNING: [Backend]: refresh not implemented on Sideload Library Manager
If I download and install it directly from Epic again, and simply check the box for it to run offline, it works just fine. But that kinda defeats the point, I want to be able to sideload it without having to authenticate myself, which should be possible according to the entry at PCGamingWiki
I put it into the field for launch options in Heroic first, to which it told me that it’s an environment variable I have to define in the appropriate table below, so I did that.
The Steam version doesn’t seem to need any launch option tweaks to be run directly from the executable, but then again, Steam also sells the native Linux version.
One more info I found is that the game might crash on startup when it can’t load the correct audio device. But the file that is mentioned, where I’d have to manually select the device, doesn’t exist. So that’s another avenue to explore.
I’m so confused though. I tried it on Windows too, added the launch option to avoid authentication, but it does not want to launch.
The information was added to the wiki by an unregistered user, though most games on Epic at the time were DRM-free. This particular game being DRM-free on every other platform also makes the claim plausible.
If gamescope misbehaves, proton-ge releases include wine fshack with fsr capabilities. Select proton-ge as the compatibility tool and add WINE_FULLSCREEN_FSR=1 %command% to the launch options. Once in game, select any resolution you like, and it’ll scale it using fsr to your display’s resolution.
I tried so hard to use the Steam Flatpak, but hit a wall when I wanted game libraries on multiple drives. The Arch wiki recommended to use the native binary.
Shot in the dark - Is there any chance the game data is on a shared NTFS partition? The start > blackscreen > dead pattern often happens if you happen to be accessing the game data from an NTFS partition, but that part of the error message is super deep and not really obvious.
After some more trial and error, I think I’ve come to the conclusion that either the Epic Version can’t actually be run DRM-free, or I’m somehow being too dumb to copy paste the launch option that allows it to.
linux_gaming
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.