Quoting: ShabbyXWhy couldn't they? Add an extension no one else can implement (or want to, because it's believed to be a bad idea), devs start using it because needed for xbox/windows, shader is now no longer portable to other systems

For Linux gaming it doesn't make much of a difference whether to implement/emulate some proprietary Microsoft shader feature in vkd3d-proton/dxil-spirv or implementing a SPIR-V extension. Except the latter should be actually easier, since the spec is open, you don't have to reverse engineer anything, you can utilize existing infrastructure in Mesa and probably more people will benefit from it in the end.

Ultimately this is a positive change. Microsoft contributes to SPIR-V, everyone benefits from it. Windows apps (not only games) will be a little bit more stable and faster on Linux, less burden on Proton developers

View this comment - View article - View full comments

I wonder how Microsoft will handle all games that still going to be DXIL based. This change doesn't make much sense if driver developers will still have to maintain DXIL support for backward compatibility. Would be fun to see Microsoft using Proton's dxil-spirv conversion library for that instead

UPD: ah, so they will provide tools for conversion, but still not clear whether they will be developed by MS or maybe they could consider dxil-spirv

View this comment - View article - View full comments

What exactly are their developments? Is it just another meta launcher like Heroic? How are they going to monetize the development in the future? Are they going to invest in development of the Linux ecosystem itself, like Valve does with drivers, wine and other stuff?

View this comment - View article - View full comments

Quoting: MohandevirOk! So the thing about fps cap is tied to the Frame Gen part? That's probably why I read that FSR3 is better than Lossless scaling; it includes Frame Gen, if I remember correctly?

FSR3 Frame generation is integrated by the game developers into the game engine. AFAIK the algorithm for FSR3 frame gen can be used without integration, but it will look worse this way. This is how it works in Lossless Scaling (and potentially in gamescope)

View this comment - View article - View full comments

Quoting: Mohandevirand works differently

It works exactly the same in principle, you need to lower the game's resolution and then it will be upscaled with the selected algorithm. LS just offers more upscalers. Plus there's Frame Gen (interpolation), which can also be implemented in gamescope, but probably only FSR.

View this comment - View article - View full comments

Well, if you think about it, this was not necessary for the Steam Deck at all. Firstly, nobody connects their Ally to Deck and use it as a controller. I don't even think it's easy to do. Secondly, this is still useless without Steam Input officially supporting Ally since the extra keys are not recognised by the input configurator and you can only map them on standard Xbox layout instead of actually making them extra.

View this comment - View article - View full comments

Quoting: creeddaDarn that's deeply disappointing if its OLED only.

It was said on OLED announcement that Bluetooth wake is only available on it afaik. However, I guess HDMI-CEC wake means that your TV should be able to wake the deck now too?

View this comment - View article - View full comments

I wonder if "Xbox" here also includes PC gamepass

View this comment - View article - View full comments

Quoting: pbI wonder what's keeping Valve from just officially releasing SteamOS for general use.

They answered many times already - it's not ready yet.

View this comment - View article - View full comments

I watched the presentation and didn't really understood the point of it. Apparently, the only reason this gets picked over fsync is because a few methods that are not commonly used by Windows applications, especially the modern ones, cannot be emulated with fsync/esync. But if they're not commonly used, why not just leave them working through this old RPC mechanism?

Quoting: sonic2kkTo this point, most custom kernels (i.e. Tkg, Zen) already have fsync too!

Fsync was merged into upstream kernel a few years ago.

View this comment - View article - View full comments