Reminds me of Blizzard's response to our petition long ago; YoU aLwAyS hAvE AcCeSs To WiNdOwS aNyWaY.

That's when I stopped playing Blizzard games, never touched them once since.

View this comment - View article - View full comments

Quoting: GuestI still play Dying Light Linux Native a lot and for some reason both the 495 and 510 drivers don't work as in nothing but a black screen with an off centre white box is all you see, so i still have to run 470 driver to play DL.

Report the bug to nvidia?

Chances are it's a game bug though, like relying on undefined behavior that's simply changed in new versions. Simultaneously report a bug with the dev.

View this comment - View article - View full comments

Quoting: Philadelphus

Quoting: MasterSleortI wonder whether Crosscode is going to be playable. It has a native build, but that one completely messes up the controls, which makes it unplayable with the native build.
The developers say that it is a problem with are JavaScript library they depend on and thus "are unable to fix it".
I hope the steam deck gains enough traction, so that the developers try and fix the issue.
This game seems such a great fit for this device.

What distro are you having problems with? I played through the entirety of CrossCode (including DLC) last year on Debian 10 and had zero issues. I even fired it up just now to confirm it was the native build and not Proton.

Oh, wait, do you mean it doesn't work with controllers? (Since I played with mouse and keyboard and don't own a controller to check.) If that's the case I hope it gets fixed, since this was once of the games I definitely was going to play on the Deck. :sad:

I played it (and dlc) natively with a controller without a problem on Ubuntu 20.04.

View this comment - View article - View full comments

If ever a kernel-based anticheat is released for Linux, avoid it like the plague. Avoid it like you would a root login. Do you really want somebody snooping around *all of your memory*?

View this comment - View article - View full comments

Is it a bit worrying that a few weeks before launch they keep saying the software is not ready? I'm actually fairly certain the original 2 months delay was to sort things out more in software, rather than chip shortage.

View this comment - View article - View full comments

Quoting: Guest

Quoting: ShabbyX

Quoting: Guest

Quoting: ShabbyX

Quoting: Guesthttps://lists.freedesktop.org/archives/mesa-dev/2022-February/225668.html

To be fair on links, I originally saw it here:

http://tuxmachines.org/node/161051 [External Link]

That's pretty quick to have mesa supporting Vulkan 1.3 (even if it's only RC1 at the time of writing).

Mesa is bigger than just some open source drivers for a niche OS. It's actually a solid codebase with a lot of eyes on it.

Show some respect :tongue:

uh.....what?

Not sure if I'm reading it in the tone intended....

Mesa has traditionally waited until some spec is released before implementing it, meaning (at least in the past) it had lagged behind such support. Being already in a position to support Vulkan 1.3 suggests even more of a changing landscape, where Mesa is on par with the proprietary driver releases and that important new features are being provided at the same time between proprietary and FOSS drivers (thanks to community involvement).

The "show some respect part" was obviously a joke, but my reply was serious and it actually applies as a reply to your new comment too. Mesa is a big thing now. It had 1.3 conformance submissions submitted before 1.3 was even announced FYI.

Much like Linux itself, it's not so much the "community" that's driving it anymore as it is various companies.

Quite aware of where most Mesa development comes from and just how far it's come, but it's still a collection of drivers, developed in full view of and with the community. Equally however, AMD can't dictate development direction for the entirety of Mesa, nor can Intel, or anyone else. Having possible Vulkan 1.3 support so early is a compliment of how well Mesa is doing now, not a criticism, with underlying implication of hope that this will continue in the future.

If I mention that and it's read in a negative way, then I most definitely need to walk away from even more of the community.

Uh no, of course it was obvious you were complementing mesa. And yes, they are awesome. Perhaps you misunderstood my original comment. What I meant was "of course mesa is awesome, how dare you be surprised" in a joking way.

Not sure how you thought I would read your comments as a criticism of mesa, lol

View this comment - View article - View full comments

Quoting: Guest

Quoting: ShabbyX

Quoting: Guesthttps://lists.freedesktop.org/archives/mesa-dev/2022-February/225668.html

To be fair on links, I originally saw it here:

http://tuxmachines.org/node/161051 [External Link]

That's pretty quick to have mesa supporting Vulkan 1.3 (even if it's only RC1 at the time of writing).

Mesa is bigger than just some open source drivers for a niche OS. It's actually a solid codebase with a lot of eyes on it.

Show some respect :tongue:

uh.....what?

Not sure if I'm reading it in the tone intended....

Mesa has traditionally waited until some spec is released before implementing it, meaning (at least in the past) it had lagged behind such support. Being already in a position to support Vulkan 1.3 suggests even more of a changing landscape, where Mesa is on par with the proprietary driver releases and that important new features are being provided at the same time between proprietary and FOSS drivers (thanks to community involvement).

The "show some respect part" was obviously a joke, but my reply was serious and it actually applies as a reply to your new comment too. Mesa is a big thing now. It had 1.3 conformance submissions submitted before 1.3 was even announced FYI.

Much like Linux itself, it's not so much the "community" that's driving it anymore as it is various companies.

View this comment - View article - View full comments

Quoting: Guesthttps://lists.freedesktop.org/archives/mesa-dev/2022-February/225668.html

To be fair on links, I originally saw it here:

http://tuxmachines.org/node/161051 [External Link]

That's pretty quick to have mesa supporting Vulkan 1.3 (even if it's only RC1 at the time of writing).

Mesa is bigger than just some open source drivers for a niche OS. It's actually a solid codebase with a lot of eyes on it.

Show some respect :tongue:

View this comment - View article - View full comments

Quoting: Liam DaweI'm not being "defensive", I'm attempting to make things clear about what is and isn't acceptable.

Well this is not the first time I see you get defensive. Again, I hope you consider my feedback as given with care.

Also, if this is "not acceptable", then you'd need to put it in the community rules (like, no profanity, no politics, no admission of preference of native) (though I strongly discourage that). If it's not written, it's not law.

Quoting: Liam DaweAnyway, Proton coverage will continue because that is Linux gaming and it's the biggest thing we have going right now next to the Steam Deck. If all people want is "native or nothing", they really should go elsewhere. I don't want to have to keep going over this.

No arguments about proton's role in Linux gaming, by all means do continue the coverage! :) But please don't say "go elsewhere"; we Linux users are already being told that enough by every other gaming news site, surely you don't like that yourself. Native Linux gamers are now a minority between Linux gamers, do you really want to treat them the same way windows gamers treat you?

I think you just need to accept this as a fact of life that people are going to voice their preference. You don't have to, and you shouldn't try to "keep going over it", because there is nothing to go over.

View this comment - View article - View full comments

The irony is that we are Linux gamers/users who frequently get ignored, and we do point that out on every website in the hope of improving the situation, and they also do sometimes say "well just stop reading this". It's the same thing really with proton vs native.

Also, no offense, and I do hope you try and take this feedback positiviely Liam, but try and be less defensive about critism; it's what makes us better.

View this comment - View article - View full comments