Molecular0079 @ Molecular0079 @lemmy.world

Posts

24

Comments

723

Joined

2 yr. ago

The failure to wait for network-online was the last thing preventing me from going rootless. I am going to have to try this again.

I've always hated it and thought it was a stupid untuitive mechanic that didn't map to anything in real life. It also looks equally stupid in multiplayer when you see player character models spasm their way up a ledge during a crouch jump. It's an old school mechanic that I am glad is going out of fashion due to better vault controls.

like a simulation of pulling your legs up in real life.

You don't pull your legs up in real life though, you use your hands to vault onto something. You can't just swap stances in mid air without holding onto anything. Even if you were talking about box jumps, like the kinds you normally do at a gym, it still isn't anything remotely like a crouch jump. Also anyone doing a box jump in an actual combat situation just looks goofy.

Any time a game explicitly has a tutorial for crouch jump, my immersion is completely broken. I am instantly reminded that it is a game.

Performance parity? Heck no, not until this bug with the GSP firmware is solved: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/538

Yeah, it's amazing how upvoted the previous comment is. Just a bunch of idiots jumping on the web-hate bandwagon when even basic media players like Kodi have a tough time playing back video on the Pi.

It just isn't a very optimized device for video playback. The Pi 5 is actually a step backwards as well, providing only H265 hardware video decode which the web doesn't even use.

Some people have reported that installing the 32-bit version of mesa libva drivers makes it work for them? Might be worth a shot.

Thanks! So VRR works out of the box for you or did you have to do tweaks to get it to work? The answers on the Amazon page are conflicting, with the manufacturer saying VRR is not supported but some users saying it does. Don't know who to believe.

It is not necessary to add the nvidia stuff to initramfs. The important part is nvidia_drm.modeset=1.

I have the Arctis 7 as well and the default EQ sounds just fine, although I do prefer the Bass Boost. You can run the software inside a Windows VM, passthrough the USB dongle and configure all your settings as well. They get saved into the headset and work just fine in Linux without Linux native software.

Usually yes, but it doesn't apply to BG3. The vulkan renderer is terribly broken ever since Patch 3.

They borked the Vulkan Renderer somewhere around Patch...3 I think? It used to be so performant, but now it runs only at 40-60fps on my Nvidia 3090 compared to the DX11 renderer which can render at 80-120 T_T

Here's the adapter I use: https://www.youtube.com/watch?v=-b6w814wXvc

Did you copy the wrong link? This was a random youtube video.

Good to hear that some adapters do work though. The lack of HDMI 2.1 basically prevented me from ever considering AMD, but if there are converters that work that certainly opens up my options.

Yeah, in a Reddit comment, Hector Martin himself said that the memory bandwidth on the Apple SIlicon GPU is so big that any potential performance problems due to TBDR vs IMR are basically insignificant.

...which is a funny fact because I had another Reddit user swear up and down that TBDR was a big problem and that's why Apple decided not to support Vulkan and instead is forcing everyone to go Metal.

Do they support VRR though? Last I heard that was still an issue with these converters.

Nowadays, I mostly don't even care about compatibility issues anymore and just expect a game to work in Linux, which is just freaking cool. Obviously, some competitive MP games are off the table due to anti-cheat, but that isn't my main gaming category nowadays so it works out.

I have a 3090 and just swapped over to the beta 555 drivers and Kwin with explicit sync patches applied (the patches will be available out of the box with Kwin 6.1). Honestly, the Wayland experience is basically flawless now for most cases. The only bug I am experiencing is Steam shows some corruption in the web views on start up until I resize the window, but it's a minor quibble in exchange for getting Wayland. I expect most of the minor remaining issues to be hammered out quickly.

Honestly, I've had genuinely bad experiences with AMD. I hated my unstable Vega 64 that would crash almost every day and was much happier when I finally ditched that card for my 3090. My laptop has a Radeon 680M and that would regularly have hard system hangs, broken video acceleration, etc.

Besides that, I also think being part of the AMD ecosystem is difficult at times. FSR sucks compared to DLSS, raytracing is sub-par, there's no path reconstruction equivalent. From a compute perspective, ROCm is unstable. Even running something as simple as Darktable with ROCm would cause half of each of my photos to not render out properly. Blender with Optix is much faster than Blender with AMD HIP. If you want to do AI, forget AMD as the ecosystem has basically gone with CUDA.

And yeah, the lack of HDMI 2.1 means no 4k 120Hz VRR on a wide variety of displays. Everyone says "why not display port", but it is tough finding a DP capable monitor with the right specs and size sometimes. For example, try finding an equivalent of an LG C2 that has DP. There's only one, its by Asus, and it costs $600 bucks more.

A lot of displays don't support DP unfortunately. I have an LG C2 which is perfect for desktop use and one of the more affordable OLED screens out there, and it does not support DP. The PC monitor equivalent that uses the same panel is made by Asus, but that one has a $600 dollar mark up.

Yeah but none of that means they're giving up the consumer space. This is all just conjecture.

I've heard something about Apple Silicon GPUs being tile-based and not immediate mode, which means the Vulkan API is different compared to regular PCs. How has this been addressed in the Vulkan driver?

Huge fucking deal, especially for Nvidia users, but it is great for the entire ecosystem. Other OSes have had explicit sync for ages, so it is great for Linux to finally catch up in this regard.

You're correct. While the stable version of KDE Wayland is usable right now with the new driver with no flickering issues, etc., it technically does not have the necessary patches needed for explicit sync. Nvidia has put some workarounds in the 555 driver code to prevent flickering without explicit sync, but they're slower code paths.

The AUR has a package called kwin-explicit-sync, which is just the latest stable kwin with the explicit sync patches applied. This combined with the 555 drivers makes explicit sync work, finally solving the flickering issues in a fast performant way.

I've tested with both kwin and kwin-explicit-sync and the latter has dramatically improved input latency. I am basically daily driving Wayland now and it is awesome.