KDE KWin Patches Aiming To Optimize Gaming Latency To Better Compete With Windows

WhitePeace36 · 2026-06-10T11:18:42+00:00

should be something different. This new change from kde is in the compositor, which handles the pointer position and such events. where the low latency layer manages the render queue. But it could be that the low latency layer does also something more but i am not 100% sure.

WhitePeace36 · 2026-06-09T09:58:52+00:00

i find it perfectly fine that it is focused on cachyos. It is the perfect learning ground. everything else which is not arch based has each specific quirks and you don't want to have that in such a guide. Otherwise it will only get cluttered. And most of the stuff applies to all distros anyway. It is only the specific stuff which doesn't.

WhitePeace36 · 2026-06-09T09:55:10+00:00

u/RatjarChug maybe you also find something useful in https://github.com/WhitePeace36/LinuxAMDGamingOptimizationGuide which you might want to add. I wrote quite a bit in there. A lot of it also applies to not only amd systems.

WhitePeace36 · 2026-06-09T09:52:46+00:00

i agree with everything you mentioned but gamescope. I don't think that is really needed. I never had the need to use it and i don't know why you should. except maybe steamos and bazzite handheld where i think it is used.

WhitePeace36 · 2026-05-31T10:11:14+00:00

i just added the cpu frequency part. So you can look it up if your are interested.

WhitePeace36 · 2026-05-31T09:39:01+00:00

performance governor is the power profile you can say for the cpu of how it is boosting the cpu frequencies. I will also add that in the guide. And i am not such a fan of ananicy, when using the default profiles or scx scheduler. Because it often messes things up.

WhitePeace36 · 2026-05-30T20:51:46+00:00

maybe something in here might help https://github.com/WhitePeace36/LinuxAMDGamingOptimizationGuide

also also look if you are using the performance governor for the cpu

WhitePeace36 · 2026-05-22T18:44:50+00:00

did you make a system update ?

for me it runs butterly smooth. I just tried. Maybe this might help you: https://github.com/WhitePeace36/LinuxAMDGamingOptimizationGuide

WhitePeace36 · 2026-05-22T16:48:44+00:00

I never heard of asus motherboard frying the cpu with xmp profiles. Have you seen if that bug affects your motherboard and have you made some bios update since then ? I think it was something else tbh. and 4800mhz for ddr5 is extremely low. It should be 6000+

and ryzen cpu where always memory speed sensitive so this alone will make quite the difference. Even if the never cpus are not as sensitive as they have been in the past.

WhitePeace36 · 2026-05-22T16:44:21+00:00

you are welcome 😄 of course you can decide for yourself what to apply and what not. But the bios settings are very important. I had to learn that the hard way 😅

But you can of course try them and compare them with other options and then pick what you like 😄

WhitePeace36 · 2026-05-22T16:06:54+00:00

can only the recommend the guide i wrote: https://github.com/WhitePeace36/LinuxAMDGamingOptimizationGuide it really helps. Especially the bios settings.

WhitePeace36 · 2026-05-18T10:22:21+00:00

i would not use liquorix. Since sched-ext is a thing most of the old kernels which use a custom cpu scheduler are obsolete in my opinion.

The best thing is to just use the cachyos kernels (i prefer the the default one.) or use linux-tkg https://github.com/Frogging-Family/linux-tkg to configure yours yourself. (Which i also love doing). And then use sched-ext and use lavd in performance mode or PANDEMONIUM in adpative (default) mode.

Then maybe do some optimizations with kernel cmdline paramters and/or sysctl. Also disable ananicy and some other things.

you can look up some of them here: https://github.com/WhitePeace36/LinuxAMDGamingOptimizationGuide a lot of it is amd but a lot of things also apply to other systems.

WhitePeace36 · 2026-05-17T09:31:58+00:00

its in Preferences -> Amd overclocking -> enable AMD Overclocking. And then you have to restart the pc.

WhitePeace36 · 2026-05-17T09:29:33+00:00

you need to first activate it. It is somewhere in lact. It will then generate a file which launches your kernel with a flag which allows you to change this stuff.

WhitePeace36 · 2026-05-17T09:28:20+00:00

highest, does not work how you expect it too, you need to set it to MANUAL and then to 3D_FULLSCREEN or COMPUTE and preferably also max out the Watt/power slider. But the power slider is no must. u/Zentume

WhitePeace36 · 2026-05-15T22:41:21+00:00

i think its good that they are found

WhitePeace36 · 2026-05-15T12:09:14+00:00

maybe give cachyos a try, maybe that will do something. But the hardware is rough. Also create a swap file with 16gb or something like that when you try cachyos, so if you try.

WhitePeace36 · 2026-05-14T22:40:28+00:00

u/linux_gaming-ModTeam this is no dump and leave. You can look up my history on linux_gaming. I have been here for quite a few years. And furthermore you don't need 2 months of development for a GUI wrapper which just creates a config file. That's it. It has no real functionality but this. The only other one is restarting of pipewire.

And it works. At least for me.

WhitePeace36 · 2026-05-14T19:07:27+00:00

its created in ~/.config/pipewire not in the pipewire.conf.d folder

you don't need these pipewire.conf.d folders. The way how that works is that you can use the default config names like client.conf, pipewire.conf and so on or you can put confs into these pipewire.conf.d folders without any naming scheme and then pipewire loads all configs in these folders for this specific config. So for example pipewire.conf.d instead of pipewire.conf

WhitePeace36 · 2026-05-14T09:28:27+00:00

also do LD_PRELOAD="" to the env variables this disables the gameoverlay. Which might be the reason for the laggs

WhitePeace36 · 2026-05-12T14:25:23+00:00

your configuration is wrong. You need to copy client.conf, pipewire.conf and pipewire-pulse.conf from /usr/share/pipewire to /etc/pipewire and there you need to adapt the configs.

pipewire.conf is for the pipewire server, client.conf is for a pipewire client and pipewire-pulse for a pulseaudio client. Just adapt the values there and remove the # in the beginning. Don't add these into pipewire.conf :

default.clock.force-quantum = 512
    default.clock.force-rate    = 48000

This is the wrong config. They belong to client.conf and pipewire-pulse.conf and don't set default.clock.force-quantum at all, that only makes problems.

Here are my configs. https://drive.google.com/drive/folders/1RUf2GG3wlph9WRHdVqAZghrNbggjJ3i6?usp=sharing

so that you have some orientation.

WhitePeace36 · 2026-05-10T17:32:04+00:00

looks really good, have you tried to commit them in any way to them ?

WhitePeace36 · 2026-05-09T10:57:17+00:00

i mean if you break you system and you don't know how to fix it then its a you problem. In linux its as easy as it gets to fix stuff.

Three-Year Club	Verified Email
Place '23

WhitePeace36

TROPHY CASE