Google has proven to be outstanding in showing off limited corporate attention span and fad chasing. Not sure why the Sony boss has anything to fear from Google.
TBH that Sony boss isn’t as bad as other Sony bosses.
It’s interesting to see how scared big gaming honchos are of Google and Amazon “becoming the Disney of games” (see the leaked Microsoft emails), when Google’s gaming thing is already dead and Amazon still haven’t managed to make something worth playing.
This GPU is right on the edge of what DXVK supports. Kepler (600/700 series) isn’t supported past 1.10.3, but the 750 ti happens to be a super early Maxwell card. Might be worth trying proton 7.0 to see if that makes a difference anyway, since that version uses DXVK 1.10.3.
Windows redistributables are installed in each game’s Proton (Wine) prefix directory, not globally. However, I have seen an example of Proton continually forgetting that it had already installed .Net for a certain game, which turned out to be due to a registry entry not getting set during install. If you’ve found a situation like this, it’s probably worth reporting on the Proton issue for that game.
people are really big on flatpaks right now but avoided that due to issues with like the two native linux games that still exist in Steam (mostly joking).
I don’t know what issues you encountered, but if you’re interested in the Flatpak, it might be worth trying those games again, possibly with Steam Linux Runtime manually set in the game’s compatibility options. Recent runtime versions have changed how they provide libraries to native linux games.
Weird. Each compatibility game should be running on their own proton prefix, each prefix is independent and changes to one game environment should never affect other games. Soldier configures it all automatically. I’ve never had to clear “downloads cache?” I wouldn’t even know where that is. How did you debug the issue, did you try protontricks? It makes directX and other common tinkering options simple.
Also, 40 minutes to compile shaders, even if it’s just once on first run, sounds sus. I’ve never had a game take longer that maybe 5. Maybe there’s something else in your system interfering? Do you happen to have Nvidia, by chance?
This ☝️. Every game has its own “container” of Proton and redistributables. My guess is that you have an odd install of Steam. I’d ditch what you have and migrate over to the Flatpak install.
Its a fairly common issue that crops up when you google the symptoms. Ended up doing a logging run and figured out it was hanging in (I forget the official term but the stage where steam installs dependencies into the prefix). And the way to reset that is to clear the download cache in Settings/Downloads.
And yeah, nvidia. But the Warframe shaders are apparently a pretty well known issue. No idea why, but I do know DE are a lot closer to old school iD these days in that a lot of people there enjoy doing fun graphics/engine stuff. Just amuses me that Warframe will take 40 minutes after an update/new proton version whereas Hitman is like 40 seconds.
Yes, CS2 beta isn’t natively available on Linux. It works through proton but VAC is only enabled for native CS2 (same goes for CS:GO). This means playing with bots or on private servers should work, but not matchmaking.
I didn’t realize that, though it seems to run fine on my potato (Ryzen 5: 1400, 16GB DDR4, Radeon 6770) with the occasional stutter, locked at 30fps 1080p for the most part. I haven’t tried faster frame rates yet as I’m trying to mirror the feel of the game between both this system and my Deck.
I’ve got Corectrl up and running with AMD Overclocking functioning on RDNA2 (6800 XT).
From yesterday’s limited testing I’m kinda blown away.
The card runs significantly more efficient under Linux so despite setting the same target clock as in Windows being 2700MHz, the cards actual clock when ruining games and not bouncing off of power limit is only 30MHz lower, on Windows it was usually around 60MHz lower.
But the major thing is that when bouncing off of the power limit I’ve seen the clock drop only by around 100MHz on Linux but on Windows it was usually a massive swing by 200-300MHz.
VRAM OC on Linux seems to be completely broken though, even increasing clock by 1MHz when on desktop will result in massive artifacts and eventual crash.
Voltage control and behaviour on Linux also seems to behave quite a bit differently than on Windows. Needs further testing though.
GTAV works better with AMDVLK, as one of the very few games out there. You could give that a shot, but be aware that AMDVLK often gets selected as default, so having AMD_VULKAN_ICD=RADV in your global Env. Variables are a good idea.
And then launching GTAV with AMD_VULKAN_ICD=AMDVLK %command%.
linux_gaming
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.