Quoting: Cley_Faye

Quoting: rustynail

Quoting: Cley_FayeUbuntu's track record of allowing fine control over some features does not bode well. We still have to jump through hoops to remove "ubuntu advantage" on systems it is irrelevant (and no, it's not "completely harmless" to leave it there).

If they go in a way that gives full control to the user, with like a checkbox/prompt before enabling something new, who cares. If they go in a way that forces things on because "it's ok, trust us bro" and "who cares, it's just a little harmless extra nail in the coffin", then no. And, well, with Canonical really liking to force things over… we'll see I guess.

I know there are alternatives out there, but the less people will care about this, the more it will become prevalent. And when every major distro decides that it's ok to do that, we're screwed.

usually I would think that on any linux system managing packages and services is so straightforward that it's hard to truly enforce anything. But then what if you have something like a snap daemon running that basically does whatever it wants on its own like windows does, and disabling it may also have consequences you don't want? hard to say but it's a bit suspicious (also I'm not really sure what people already have to do to "debloat" ubuntu cause I never really used it)

Debloating ubuntu these days is relatively trivial, and the "bloat" part is largely exaggerated. The "bloat" here is an extra package/software manager, and a nagging screen that pops up in terminal, both of which can be removed with relative ease. It's laughably little compared to a windows debloating process: snapd and his ilk can be removed with a few commands, and the ubuntu advantage can be removed by installing a fake empty package instead.

Still, the intent is there; ubuntu advantage in particular is a direct dependency of most metapackage that ensure you get a usable system, and not using these metapackages is a pain in the butt. Since we're talking open source, there's no way to make things absolutely inevitable, but Canonical sure could get very aggressive with extra layers of bullshit, which they did not do so far.

It's not ideal, but even now, I think the situation is relatively fair to everyone. KDE Neon, for example, explicitly built over Ubuntu LTE, have such an empty package to disable this part.

Substituting a package with an empty one already feels like a filthy hack tbh that would take me a while to figure out on my own, like you probably have to build it and all. I guess it works this way because it was more convenient (or like a more "proper" implementation in line with how the rest of this stuff works) for canonical rather than more malicious but it doesn't make it any less annoying

View this comment - View article - View full comments

Quoting: Cley_FayeUbuntu's track record of allowing fine control over some features does not bode well. We still have to jump through hoops to remove "ubuntu advantage" on systems it is irrelevant (and no, it's not "completely harmless" to leave it there).

If they go in a way that gives full control to the user, with like a checkbox/prompt before enabling something new, who cares. If they go in a way that forces things on because "it's ok, trust us bro" and "who cares, it's just a little harmless extra nail in the coffin", then no. And, well, with Canonical really liking to force things over… we'll see I guess.

I know there are alternatives out there, but the less people will care about this, the more it will become prevalent. And when every major distro decides that it's ok to do that, we're screwed.

usually I would think that on any linux system managing packages and services is so straightforward that it's hard to truly enforce anything. But then what if you have something like a snap daemon running that basically does whatever it wants on its own like windows does, and disabling it may also have consequences you don't want? hard to say but it's a bit suspicious (also I'm not really sure what people already have to do to "debloat" ubuntu cause I never really used it)

View this comment - View article - View full comments

If it also remembers what screen and desktop windows were placed at it's the best thing since sliced bread, because it means no more window rules for the most part

View this comment - View article - View full comments

I do like the idea they sort of use Steam to promote GOG but it probably doesn't mean much to people who don't already have an idea of what GOG is

View this comment - View article - View full comments

Quoting: sarmadGnome 50 has a serious regression in graphics performance, so stay away from Ubuntu 26.04 until it's fixed.

https://www.phoronix.com/review/nvidia-595-kde-gnome

I think KDE has reached a state where you can fall back to it as the most reliable option. Especially since on wayland everything has its own implementation of everything so it's more likely to run into differences and issues depending on the desktop. I moved from a window manager to KDE while playing Death Stranding 2 and I think it actually improved performance, maybe because it seems that Plasma has a proper support for exclusive fullscreen mode unlike the WM I used, although I could be wrong and it's some random coincidence, but I still kept using plasma for now as it also fixed some other random issues I've had recently

View this comment - View article - View full comments

Quoting: tgurrYou probably still need to install 32bit graphics driver on your host for as long as you want to play 32bit native games. Maybe they could add an option like "Always run the windows version of the game (through Proton) for games which only have a 32bit native version" to be able to really get rid of the need to have to have 32bit libs installed. As (old) 32bit native games won't magically go away any time soon - if ever.

I always thought that when Wine/Proton finally reach the state when they're 64 bit but can run 32bit apps (which is supposed to be pretty close), you don't need multilib at all except for steam itself. But maybe I'm missing something.

edit: ahh I guess you mean linux native games. Then probably yes

View this comment - View article - View full comments

Played through the intro on rx6600 using default (medium) settings and Proton Hotfix.
The game itself ran fine, but in the cutscene/talking part it was freezing for like one second every 15 seconds or so, and then it crashed. And it didn't even save, so I played the whole thing again except I switched from pico upscaling to fsr, it looked exactly the same, but the game was smoother I think and then cutscenes didn't crash but still had some occasional hiccups. Also I actually rebooted before the second run just in case, it seems that in rare cases long uptime with a bunch of suspends in between can hurt gaming on this system

edit: also I had mesa 26.0.2 and 6.18.13 zen kernel
edit2: and by crash I actually also mean complete freeze

View this comment - View article - View full comments

Quoting: Purple Library Guy

Quoting: rustynailTo me it seems fundamentally impossible that this will ever work well. DLSS only has the current frame to work with, so all of the information used to add whatever it adds to scene NVIDIA has to pull out of their ass. This is also true for upscaling which is why it will always have all the artifacts, but made up details that don't make any sense are obviously way worse.

To be clear, I don't know what this press release sentence means, and I'm not enthused about this whole schtick. But, this might be relevant to them claiming they can pull that off:

materials that are anchored to source 3D content and consistent from frame to frame.

One specific related thing I was thinking about is that because DLSS makes character faces kinda glow, it seems to sort of put fake light sources above them that don't actually exist, so I think it has no idea what is actually happening in the scene, and maybe even doesn't really have any real concept of lighting (at least in the sense in which it would be explicitly accessible to devs so they could actually tell what the model is doing rather than just spitting pixels out based on some unfathomable statistics or whatever). Tbh now that I think about it more, my argument about it only knowing about one or few frames is probably not even that important, because if something is not in the game then it's not in the game and it's going to be made up in any case, whether it's nonsensical faces or subtle random color changes all over the place.

View this comment - View article - View full comments

Quoting: WanderdueneI'm not surprised to see something like this popping up in the Redering pipeline now. I'm torn about that. For games with a realistic look, this could be the final step toward achieving true photorealism. On the other hand, that could lead to more AI-generated look and make everything look increasingly generic. I really hope the developer has control over what gets used. As a developer, I'd be pissed if Nvidia's AI replaced my visual style or the appearance of characters with an AI-generated look without control over it.

To me it seems fundamentally impossible that this will ever work well. DLSS only has the current frame to work with, so all of the information used to add whatever it adds to scene NVIDIA has to pull out of their ass. This is also true for upscaling which is why it will always have all the artifacts, but made up details that don't make any sense are obviously way worse.

View this comment - View article - View full comments

Quoting: pbPlease tell me the left hand image is just lowest settings. Tomb Raider from 2013 looked better than that without any mumbo jumbo.

Resident Evil 9 didn't look anywhere near this bad when I played it on a potato-ish rx6600 without any upscaling

View this comment - View article - View full comments