My only major gripe with the SC2 is that the control layout makes the D-pad only accessible with the left thumb. I’m firmly an Xbox layout supremacist, and that’s partly because it allowed me to reach over to the D-pad with my right thumb without releasing the left stick (e.g. using a healing item while bravely running away).

Other than that, my main issues are related to Steam Input’s integration. If a game is running inside Gamescope, even if it’s launched from Steam, I can’t use the controller to send keypresses or mouse inputs to the game.

Fuck.

Says a lot about you that, of all of her achievements and qualifications, and the fact that she not just revolutionized but practically created the field of consumer-grade wireless VR… you get stuck on her being a woman.

God’s menagerie is vast, but the fences are low.

That’s literally what happened with the black PS5 shells. They used Sony’s trademark without permission, got a cease and desist, and didn’t learn a fucking thing from it. I’m sure they had the best intentions, but doing it twice was monumentally stupid.

A few notes on Linux.

Recent versions of Wine use SDL2 to implement XInput support. Any game running on a decently new version will work with the SC2 out of the box. Run wine control joy.cpl (with the correct WINEPREFIX obviously) to configure and test both XInput and DirectInput devices.

This unfortunately causes issues with SISR. Since both SISR (through Steam Input) and the Wine game (through SDL) process the input events separately, using SISR will result in double inputs. This can be fixed by telling SDL to ignore the SC2 altogether by passing this environment variable to the game: SDL_GAMECONTROLLER_IGNORE_DEVICES='0x28de/0x1304'

The Mystery Of The Droods. It runs perfectly, it records perfectly, I can save the game, and I didn’t even have to gut my PC to get it to work. Linux appears to be the ideal environment for the skeletonized remains of ancient Windows games.

Time to harrass Vivec’s well-dressed cousin, then poison a bum and steal his money.

I have horrible news.

Ring works perfectly on Linux. Apparently this game is an absolute wanker on Windows. Here it just glugs along gluggingly.

Mostly I can only describe it as “game no worky”. Steam pretends to launch a game, then nothing happens. My hypothesis is that Steam does something to the runtime environment that fucks with some games.

One other thing that I’ve noticed is that on Wine/Proton environments launched from Steam, the lettered drives (aside from C:) are mounted as some kind of overlay filesystem. Writing to them (e.g. by an installer) causes data to be written into memory, not to the mass storage where the drive targets are located.

They were shipped into the US from Hong Kong according to a cargo manifest from the 4th of April, so probably manufactured (or at least assembled) in East Asia.

https://www.importgenius.com/importers/valve-corp

I managed to fix it by forcing a firmware update in Steam’s developer mode, I’ve updated the post with details.

What’s the problem with Vortex (other than using Electron)? I’m using it for Fallout New Vegas on Linux desktop, and other than OS-specific issues (like having to fuck with the Wine config to make hardlink deployment work, or not being able to handle nxm links), I’ve really had no significant problems with it.

Look, if your dedication to lick Uranus is what it takes to get humankind to another planet, then so be it.

Not quite as far, but this article has the same energy.

• Press Y to concede with dignity

• Press N to let a game bully you