A big problem with Android is ARM vendors don’t upstream anything in so you need to run very specific kernel and bootloaders just to boot the OS. SteamOS on x86 won’t have that problem, regardless of who makes the end device.

This looks nice, especially cool that it supports multiple vendors.

This is frame generation. That’s a second option on top of the older DLSS super resolution (upscaling) that doubles framerates at the cost of some latency. It only works on 4000 series cards.

That DLSS frame generation works in Proton

The problem with all these Firefox forks is most of them are dead ends, development wise. They don’t contribute upstream. Maybe Tor excluded.

Hopefully this one is different, it does seem to have some actual code behind it rather than just disabling features.

Yes, and ChromeOS is built from Gentoo. That doesn’t mean much, the end user experience is worlds different.

Mostly that it doesn’t work on Steam Deck. Hits memory limits IIRC.

It would allow them to do HDMI FRL also, which is probably what you mean when you say HDMI 2.1. AMD cards also do HDMI FRL I thought. FRL is what allows things like 4k120Hz (higher bandwidth modes). The VRR that the Dock does is the VRR standardized with 2.1, which is why it works on TVs and devices that do not support freesync (see: LG TVs).

Anyway, the Dock doesn’t have a fast enough HDMI converter to do that. It’s not a licensing issue. Next gen Deck/Dock will probably do it.

Actually it works fine on Steam Deck. It uses VRR over DP to the dock, which then translates it to HDMI with VRR. The dock has proprietary firmware to do this.

Intel and Nvidia hardware with open source kernel drivers also do a similar trick where the HDMI part is in a firmware blob. Only AMD does not work with HDMI VRR.

Hah! I wish it was email, so I could ignore it. Instead it’s either a Slack DM, which escalates to a phone call.

Yes it is. It’s not in mainline wine, it’s been in kernel for a long time now.

It’s annoying all the articles are focusing on performance versus stock wine here when basically everyone uses Proton or a fork of it anyway, which has had fsync for years now that does similar performance uplift.

The story here should be that we’re getting fsync level performance with fewer bug and it can be upstreamed to wine. There is no relevant performance uplift for Proton users, but I guess performance gets clicks so that’s the story all the press are going with.

It’s not merged, but the benchmarks are against upstream wine. Proton has hacks (fsync) that have almost identical performance uplift but were not suited to upstreaming.

So basically this will improve “correctness” versus current Proton, not performance. Should fix some bugs and improve compatibility.

Versus stock wine, it’s a huge perf uplift though.

What’s wrong with the Flatpak permissions system on Linux?

555.58 works great for me in Wayland. 3090 on Arch with Gnome

Finally some news to make buying dozens of studios then laying off tens of thousands of employees all worth it

As an individual consumer… Not much. Still wouldn’t buy their product as it’s showing support with whatever little power you have.

In a better world there would be market regulations or something to keep a massive company from burning all their money in a market to have an unfair advantage over all others.

I mean they’re a mega corp willing to lose billions upon billions to own the market. That none of their competitors are willing to bleed money like that isn’t surprising, and buying into such an obviously poisoned platform is not a good idea for the future of the industry unless you want it to be owned by Meta.

*Ik ben

Uhh nvidia has had native Linux drivers since the 1990’s…