Anyone thoughts on safety with vkbasalt enabled? Usually anti-cheat systems that don't block the DLL don't punish you for using ReShade on Windows, but EAC/BattleEye do block it.

View this comment - View article - View full comments

British government should buy ads in the game to find potential lorry drivers.
Though Central Russia might be more attractive. :whistle:

No hard feelings. :heart:

View this comment - View article - View full comments

Big fan of RNNoise in Mumble, works much better than Nvidia's crazy proprietary bloat that slows down your GPU.

View this comment - View article - View full comments

Quoting: CreakThe Battle(non)sense from the blog post is super interesting! Apparently, limiting your framerate has a better impact on the input lag than these algorithms:
https://www.youtube.com/watch?v=7CKnJ5ujL_Q [External Link]

That is true with some, but not all in-game fps limiters. Also, when even dropping slightly below the limit, the lag ~instantly goes back to full blown rubberband. With LatencyFlex, you don't need to worry about dropping below the limit anymore.

View this comment - View article - View full comments

Quoting: WORMI played deathmatch on all the maps I normally play and now I almost never stutter. Anyone know where the shader cache is stored? Multiple accounts on shared PC means re-caching all the shaders from scratch :sad:

Search file system for "csgo_linux64.dxvk-cache", it should be buried somewhere in Steam folder. DXVK_STATE_CACHE_PATH env also still works like with DXVK build as DLL. No idea if setting it can interfere with Steam shader pre-caching, but I found it handy to have all state caches at one path in order to create backups.

Silly CS:GO Linux build once again randomly crashes at launch or during loading for me. Valve, seriously...

View this comment - View article - View full comments

Hardware cursor on Xorg is mostly (entirely?) unaffected by DE specifics.

View this comment - View article - View full comments

DEs shouldn't consume any CPU time while idle or gaming. If they do, something probably is bugged. Doesn't happen for me. MangoHUD frame time graph also says everything is alright. "KDE has bad gaming performance" is not sustainable as a general statement.

View this comment - View article - View full comments

Quoting: FredrikWell it might be a hardware thing, with a Nvidia card kde is way slower when gaming, also on my work computer with an i3 and integrated graphics kde is way slower then gnome for gaming.

No, sorry. There is no performance hit by Plasma with compositing suspended. It is simply ~impossible. It doesn't turn off (reliably and) automatically in some cases, in which you need to do it manually via shift + alt + f12. Sucks (will be better on Wayland), but at least compositing can be forced off and on that way. There haven been cases where fullscreen unredirect was unreliable with Gnome Mutter, be it not turning off in games or not staying on with browser in fullscreen.

Quoting: Fredrikand overall kde with nvidia on wayland is way to buggy, gnome is fine, but I find games to be buggier on wayland so I usually run x11. At work I now use wayland with sway since the computer only have 4gb ram, it works pretty good.

Plasma works fine with Nvidia, I don't find any compositor/DE to work better (only worse, e.g. Mutter when moving multiple windows).
Without Akonadi/Kmail, plasma also consumes only <500MB of RAM. Works fine on my 4GB device.

View this comment - View article - View full comments

Quoting: FredrikI really doubt it, its way to buggy and slow compared to gnome atm, they where catching up, but then gnome released gnome 41 and its even faster then xfce. Since I am a gamer I always look for the desktop that runs the best with games, it used to be xfc but now its gnome, on my machine at home the difference is small but its there, at work on a slow i3 with integrated graphics gnome is way faster then kde in games.

Sorry, but no. I'm writing this on an ultra slow Gemini Lake device with Arch, and Gnome 41 performance makes it completely unusable on both Xorg and Wayland. Plasma Wayland is far, far better optimized.
Wayland gaming is not yet a thing, as buffer modifier issues currently prevent direct scanout from working. On Xorg, you can just disable KWin compositing entirely and any game is 0 affected by Plasma.

View this comment - View article - View full comments

Quoting: GuestIt's quite a non-committal answer, the sort you get from politicians.

Diplomats can also be politicians and I think it was a polite way of saying that half-a**ed Linux ports with stupid restrictions for crosss-play etc. are not the way to go.

View this comment - View article - View full comments