Well shit.

For the first time in my VTubing journey, I've managed to choke up my GPU. It's not even that old, either, an nVidia 3060. I suppose grandpa was right, cheap men pay twice.

So, any #linux #vtuber folks out there have any opinions or reccommendations? I've really not been paying attention to the graphics scene for a fairly long time. That being said, I have half a mind to go the AMD route.

@h_ingles I'd consider looking into why it's choked and complaining to the devs.

That's way too recent and powerful to reasonably be insufficient for most conventional vtubing stuff.

Exceptions, perhaps, for if you're doing VR stuff since the requirements for that aren't entirely gratuitous (it truly does get intensive fast).

@lispi314 I thought that it was too recent to be a slouch, too. But I've been wrong before.

Maybe I should change my approach. What GPUs are Linux folks out there playing AAA stuff on Proton with?

The lion's share was the remade System Shock, which was already running at below default. I doubt they're going to hear out a random man using it in proton. May very well be a one-off as well. That being said, this is the first time I've played a modern AAA game around release since, well, ever.

@h_ingles I've had varying experiences with Proton, with some games running significantly better than native, as well as the opposite.

I haven't looked into it enough to make a useful contribution on the topic. It does however seem to be *very* dependent on the graphics library APIs used by the game (Cyberpunk 2077 was unplayable for most of a year after a certain update, for me, for example; I mean that literally, it crashed on startup because of an unimplemented function stub).
@lispi314 @h_ingles unrelated to @h_ingles questuon, but I played the latest version of cyberpunk very recently with proton and had no issues. (through gog, rtx 3050 on laptop, I could hold 60fps at 1080p with low on shadow settings and a few other particularly demanding settings, and medium on most everything else)
@cibo @h_ingles Yeah, VKD3D has since been updated with the missing DX12 APIs that caused me issues.

@lispi314

I suppose a follow-up is in order, eh?

There really wasn't a good explanation for why a game like that would strangle a 3060 on default settings. But a particularly sharp cookie brought up one point in particular.

If System Shock is taking the lion's share of the GPU by simply running on defaults, and OBS is only capturing the game at 60fps for the purpose of streaming, then just lock the game to 60fps as well.

As I have 144Hz monitors, ths cut System Shock's usage by over half. Because... well.. it's drawing over 50% less frames.

The game has no way to set frame rate, so I used the launch option DXVK_FRAME_RATE to limit it.

@h_ingles Oh, that makes sense and explains quite a bit.