Absolutely loving Pipewire, been using it for a while now. Reminds me a lot of CoreAudio on the Mac, though with a bit more up front configuration.

It being a drop in for PulseAudio, JACK, and ALSA, all at the same time while still being great on latency is just *chefkiss*. I can go from gaming to recording music tracks in Ardour with no messing around.

View this comment - View article - View full comments

Patreon's... definitely not my first choice, considering some of the stuff they've pulled over the past few years, but I appreciate there's at least another option (even if Paypal is *also* scummy... But pick your poison, I guess).

Glad to see it all going to good use and making this better for everyone! We appreciate the work you do. <3

View this comment - View article - View full comments

As someone who still hosts an old social MU* for friends off an old RasPi in a drawer, and learned Multi-User Forth (MUF) and MPI as some of my first programming languages in... elementary school...

This is certainly A Thing. I never got big into the combat-heavy MUD way of doing things, but it's fun seeing people keeping this style alive!

View this comment - View article - View full comments

Quoting: Samsai

Quoting: Kithop...really, the sound issue is because it's trying to hit ALSA natively? PulseAudio is... *checks notes*... 19 years old at this point. (GitHub issue link )

Though at least later on it sounds like it's from people using the Flatpak version instead of native - and yeah, that's the first thing I'd say for almost anyone: don't use Flatpaks for this. Use your distro's native Steam package as your first choice, and then move down the line to like, getting it direct from Valve or whatnot if they don't have one. Running Steam in Flatpak or Snap just sounds like a Bad Time. But hey, at least there's validation that the sandbox is, uh, sandboxing things!

...like your own app from a decent audio API... ;p

That's not how that works, the sandbox isn't just arbitrarily deciding to block a game from using ALSA (there's a bunch of other games that also use ALSA which work just fine). And, funnily enough, I tried it out on Flatpak Steam today and it seems to work fine, sound and all.

So, it's almost like the game either had regular launch problems or some setup-specific problems, but which weren't the fault of Flatpak. So, it seems your blame was misplaced.

I've admittedly never bothered with Flatpaks at all outside of the Steam Deck, and yes, there are potentially plenty of complicating factors, but multiple people had Flatpak issues; that's all I mean to reference, there. It sounds like it wasn't blocking ALSA, but access to PipeWire, so presumably there just needs to be some updated default configs upstream somewhere.

View this comment - View article - View full comments

One more reminder that with the Unity fallout, the solution wasn't going to be 'switch to Unreal', because there's nothing stopping them from being about to try to pull the exact same move.

View this comment - View article - View full comments

Yeah no, not after this fiasco: link

Not trusting any of their newer hardware on my home network.

View this comment - View article - View full comments

...really, the sound issue is because it's trying to hit ALSA natively? PulseAudio is... *checks notes*... 19 years old at this point. (GitHub issue link )

Though at least later on it sounds like it's from people using the Flatpak version instead of native - and yeah, that's the first thing I'd say for almost anyone: don't use Flatpaks for this. Use your distro's native Steam package as your first choice, and then move down the line to like, getting it direct from Valve or whatnot if they don't have one. Running Steam in Flatpak or Snap just sounds like a Bad Time. But hey, at least there's validation that the sandbox is, uh, sandboxing things!

...like your own app from a decent audio API... ;p

View this comment - View article - View full comments

Quoting: habernirhow do i install this FPS toolbar at the top?

thanks nir

On Steam Deck this is built in as the performance overlay ('...' button on the right), upstream it's just MangoHud

View this comment - View article - View full comments

Honestly, as weird as this is to say it - I honestly won't mind if this ends up going through. I know it's kind of blasphemy to root for Microsoft, of all companies, but the Xbox division at least has *sort of* shifted. First party games still ending up on Steam and in most cases running fine on Proton (even Starfield!), semi-official guides on getting xCloud Streaming working on Steam Deck, the work they put into WSL2... their accessibility efforts like that special pad w/ 3.5mm jacks for all the buttons...

Sure, you can argue it's for lock-in purposes, and there'll always be that to some degree, but heck - have we forgotten about the abuse & toxic work environment at Blizzard from a few years back? At least MS could rein them in and try to fix it.

It's not the ideal outcome, sure, but I can't bring myself to hate it either, I guess. I fully understand I'm in the minority on that one.

View this comment - View article - View full comments

A bit unclear here - do we know if these are also (at least as they pertain to games like Starfield) in
GE-Proton8-14? It says they updated to the latest VKD3D-git and of course GitHub just says 'last week' without an actual timestamp (really?).

Presumably the features have been in Git for a while before they tagged this release, and the performance seems... okay, so I'm going to assume 'yes', but I'm wondering if this might be a good reason to flip back to Proton Experimental for Starfield.

View this comment - View article - View full comments