More easily translating Windows' behaviour to Linux was obviously the primary initial motivation, but I don't think it will end up as the only one. Being able to wait for one of many signals seems like the kind of thing that would be generally useful; there's a reason Windows has that function, after all.

View this comment - View article - View full comments

Quoting: Ehvis

Quoting: CatKiller

Quoting: Liam Dawe

Quoting: ElectricPrismImagine we could do for GIMP what has been done for Blender, what an amazing thing that would be.

Will never happen while it's called GIMP.

Unfortunately, the project for GIMP-that's-not-called-GIMP withered on the vine.

It's a obscure non-contextual meaning in one language that is not the native language of most people. You can't expect the general population to care.

I'm not bothered by the name. Sure, stating from the outset that your product is in some way subservient or hobbled isn't the best marketing move, no matter how hilarious the initial devs found it, but whatever. There are other products whose names are gibberish (Tumblr and what-have-you) or way worse (the Toyota Shit, for example).

Liam's right that there are some people that are bothered by the name. Glimpse showed us that there aren't enough people that want to use and improve the Gimp, but are bothered by the name, to make it actually viable.

Personally, I think the non-responsiveness of the Gimp project to the GTK and Python transitions is what's doomed it, way more than the name, and some other project will steadily acquire more advanced functionality and eventually take over that niche entirely.

View this comment - View article - View full comments

Quoting: Liam Dawe

Quoting: ElectricPrismImagine we could do for GIMP what has been done for Blender, what an amazing thing that would be.

Will never happen while it's called GIMP.

Unfortunately, the project for GIMP-that's-not-called-GIMP withered on the vine.

View this comment - View article - View full comments

I think this might bump me onto the Experimental branch. The only game I really use Proton for at the moment is No Man's Sky and - because I use overlays to cap the framerate to compensate for the game's lumpy frame timing - I'd stuck with 5.10 rather than the containerised versions. NMS is getting DLSS, 470 gets DLSS that Wine can use, and Proton Experimental starts using it. Should be interesting to try.

View this comment - View article - View full comments

Quoting: 3zekielBtw, do we have any news on when 470 series is coming ? I am quite hyped now.

The DLSS-in-Proton needs 470, since that includes the dll to be dropped into the Wine prefix, and they said that that was happening this month, so sometime this month. Roughly.

View this comment - View article - View full comments

Quoting: gardotd426This is nonsense and demonstrates that you have no idea what goes into anything to do with vkd3d-proton. And Joshua is a vkd3d-proton *and* DXVK developer, and knows infinitely more about this shit than you do.

In particular, he was involved with the creation of the vendor-neutral Vulkan ray tracing extension, redid Q2RTX to use the vendor-neutral Vulkan ray tracing extension, and... wrote an open source implementation of Vulkan ray tracing for AMD hardware, which AMD have failed to do themselves.

View this comment - View article - View full comments

Quoting: MohandevirIronburg Inventions didn't create back buttons, they just adapted something that was already used elsewhere.

Well, to be fair, an innovative arrangement of existing things is legit patent material, and Valve did try using buttons rather than paddles and found that it wasn't as good.

QuoteOh well... Pattents...

Yep.

View this comment - View article - View full comments

Quoting: mphuZIn order for AMD to start working with Linux faster, they need motivation. And finance. Maybe if they were offered help, they would think about it.

Quoting: mphuZWhat is the point of this, if there were no and almost no games with RT on Linux?
What's the point of chasing a niche (at the moment) technology?

What you're saying here is that AMD are too poor and too incompetent to be able to follow standards in innovative graphics technology, which is a way harsher judgement than 3zekiel's (they just don't care very much) that you took exception to.

View this comment - View article - View full comments

Quoting: MohandevirWhat is specified in the pattent?

It's specifically having paddles on the back of a standard controller. The patent is here, for those that are interested.

View this comment - View article - View full comments

Quoting: mphuZ

Quoting: 3zekielPlus, considering AMD did not deem necessary to proprely support VK ray tracing on Linux...

Nonsense. Who told you that?
It may take a lot more work than you think. Have patience.

Joshua Ashton

QuoteIt is really sad to see how little AMD cares about Linux as a platform for Vulkan.

On Linux, it took them 5 months since the ray-tracing spec-launch to be bothered to rebase and release their proprietary driver with ray-tracing support – and we have still yet to see their open-source variant, AMDVLK have any support.

On Windows, this was day 1.

Nvidia had day 1 Linux support, albeit in their beta driver. And they had day 1 support in their main driver when they released the vendor-specific one previously. Intel managed to get Linux support for Vulkan ray tracing before AMD, and they don't even have any ray tracing hardware.

View this comment - View article - View full comments