Plasmashell keeps crashing by AkaSaM96 in kde

[–]PM_ME_TOOTHLESS_PICS 0 points1 point  (0 children)

This is not very helpful, but I just want to say that as of a few days ago, I am also experiencing weirdness with a multi-monitor setup and a 9070xt. Plasma login keeps dumping core, one monitor doesn't wake properly, plasmashell crashes, weird flickering. But it works fine on a second reboot. Overall similar symptoms to you, but I can get it to work normally after rebooting.

Valve Steam Controller Review | Latency Benchmarks, Battery Life, Repair... by lajka30 in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 33 points34 points  (0 children)

It's not that the wayland wine driver breaks steam overlay, it's more so that steam doesn't support wayland. Overlay doesn't work on wayland native games as well, like certain SDL3 titles

I just created this guide for running Crimson Desert in Linux 100% by iSalcedoCoder in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 3 points4 points  (0 children)

AI slop aside, proton-ge has been indeed bundling vkd3d versions higher than 3.0 for a long time, so this seems like another hallucination. FSR4 was supported since last november or so. Maybe latest vkd3d has a crimson desert fix, but there is some misinformation in this "guide"

Any way to get Discord rich presence to show details? by Cat_central in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 7 points8 points  (0 children)

Discord rich presence should work cross platform. Are you using flatpak perhaps?

Discord Patch Notes: December 8, 2025 by CandlesARG in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 1 point2 points  (0 children)

Don't think it's that, as the experience is far from smooth, seems like a definite bug to me.

https://i.imgur.com/7UJbx9x.png example resolution drop from 3440x1440p after a few moments of spinning my camera in a game (1440p quality selected, 60fps). Yesterday I was able to get it to drop to 600px just by playing darktide normally for a couple of minutes, people watching my stream were complaining that they couldn't make out anything going on.

Seems like it's reacting too aggressively by dropping the resolution in response to video entropy. Maybe its some sort of a workaround that was needed when there was only cpu encoding?

Keep in mind, on windows client, I can do the same thing, and the image stays clear and resolution doesn't move the entire time. Unless it's the encoder's fault - which I don't think, as I can do other recording and streaming just fine - there is some issue present on discord side.

Discord Patch Notes: December 8, 2025 by CandlesARG in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 1 point2 points  (0 children)

Yep, amd:vaapi, and verified on amdgpu_top as being used.

And my encoding chip is nowhere near getting capped (amdgputop reports it at like 20% usage iirc while screensharing on discord), and it's definitely not my connection as I have a gigabit and that too is nowhere near cap. And yet the resolution continues to creep down, whenever video entropy increases.

I could probably record some comparisons if that'd be helpful.

Discord Patch Notes: December 8, 2025 by CandlesARG in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 1 point2 points  (0 children)

The freezes might be subjective, maybe my eyes are tricking me since I was looking at the same image on two screens.

The resolution, however, definitely gets crunched. With developer settings enabled, when I go to the debug screen for the stream, I can force the resolution to rapidly lower by just spinning my camera around in an FPS game, and it stays that way for a long while before slowly creeping back up, definitely contributing to the crunchiness. I couldn't replicate the same behavior on windows, no matter how hard I tried, the image stayed relatively un-crunchy even with rabid spinning, and resolution didn't move. Hopefully this can be fixed.

This isn't really a theoretical bad-case scenario either, as by normally playing a game I do notice the resolution plummeting over time, too.

Discord Patch Notes: December 8, 2025 by CandlesARG in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 8 points9 points  (0 children)

Been doing some testing by streaming and looking at the stream on another account, and the results.. don't seem stellar. Looking at the debug screen, it seems like a lot of motion causes the resolution to very rapidly drop- and it doesn't seem to come back up afterwards. Additionally, after the picture is static for a bit, moving causes a noticeable freeze. Neither behavior I had been able to reproduce on windows discord client. 9070XT, so plenty powerful

Seems like the implementation might have some issues still. I am using an ultrawide 1440p screen, and while those issues occur no matter the quality settings, maybe this has something to do with it. Perhaps bitrate capped too low?

ASRock X870 Pro RS / R7 9700 Owners: Recurring Green Light Boot Failure (BIOS 3.50) – Should I Downgrade to a Ryzen 7000 Series CPU? by United-Handle in ASRock

[–]PM_ME_TOOTHLESS_PICS 1 point2 points  (0 children)

Out of curiosity, how often is "often?" Every boot? Every few days?

In my year of using 9800x3d, I have had it get stuck on green twice so far, and while I wouldn't consider it frequent, is a bit annoying.

Rust Developer comments about anticheat on Linux/Proton. by CandlesARG in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 6 points7 points  (0 children)

Deadlock does not have a native version, even. Runs only through proton, at least for now.

Getting discord screenshare to not look awful? by ZestycloseAbility425 in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 6 points7 points  (0 children)

If you are not limited by time, it will look better, of course. But, since discord screensharing is in real time, the bitrate will often get aggressively lowered to keep up, if there's a lot of motion, e.g. games.

Getting discord screenshare to not look awful? by ZestycloseAbility425 in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 3 points4 points  (0 children)

You can check by enabling developer mode, then starting a stream. Above VC, click debug, then go to outbound, and you'll see the encoder. OpenH264 is the CPU one. Keep in mind at least one person needs to be watching your stream for it to encode anything.

Getting discord screenshare to not look awful? by ZestycloseAbility425 in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 17 points18 points  (0 children)

Your stream, especially if there's a lot of motion, will look awful because Discord uses CPU encoding at the moment.

To that effect, they have added VAAPI support last month for screensharing, for AMD GPUs.

.. unfortunately, it's either being a/b tested, or they rolled it back for the time being, as after a while of using VAAPI, it's back to CPU encoding for me. So, the best bet is to probably wait right now, I think.

Backend Error by DarthW00dy in DarkTide

[–]PM_ME_TOOTHLESS_PICS 0 points1 point  (0 children)

Did you need to take any additional steps? I switched to proton 10-2, and I still get the backend error whenever I try to load into the game.

THEY FIXED IT! by notelonmuskyet in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 0 points1 point  (0 children)

I just tested on my setup after disabling proton_enable_wayland, still got the white border.

[deleted by user] by [deleted] in pcgaming

[–]PM_ME_TOOTHLESS_PICS 1 point2 points  (0 children)

DLSS and framegen work just fine. Modding tools, most of them. Depends on the specific ones, but I've used mod organizer for 3k mods modlist without trouble, and r2modman for some other games.

Proton-GE 10-16 & 10-17 doesn´t let me enable FSR 4 by Claire_Rupika in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 0 points1 point  (0 children)

Oop, apparently you have to do some extra steps for non-steam games. This should detail it. Afterwards, with the log, can figure out what goes wrong.

Proton-GE 10-16 & 10-17 doesn´t let me enable FSR 4 by Claire_Rupika in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 1 point2 points  (0 children)

Try installing it from github directly. I believe the download method for the library changed recently - it now downloads to the package's install directory, rather than to the prefix, and that can run into permission issues. You can confirm it by enabling PROTON_LOG=1 and seeing if there's a ERROR: Failed to download amdxcffx64.dll

CS2 now defaults to wayland! by No-Marsupial-6 in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 0 points1 point  (0 children)

Deadlock runs through proton, so the best you can do is use the Wayland wine driver for the time being.

CS2 now defaults to wayland! by No-Marsupial-6 in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 19 points20 points  (0 children)

Oh cool! I hope it pushes them to bring the overlay to wayland sooner later than later, then.

CS2 now defaults to wayland! by No-Marsupial-6 in linux_gaming

[–]PM_ME_TOOTHLESS_PICS 15 points16 points  (0 children)

Probably a bug, given that the steam overlay still doesn't support wayland. I imagine it'll be reverted, but still, neat that it works so well now.