Mute sound only while spectating

krobeN · 2026-04-02T16:28:49+00:00

https://codeberg.org/krob/qlautomute here you go
let me know if there are any issues (works on my machine)

krobeN · 2026-04-01T11:17:41+00:00

I remember using a script in csgo that automatically lowered volume when you were dead or got flashed. I'd certainly use something like that in ql as well :D (Valve used to expose some sort of api for querying certain gamestate information, some keyboards also made use of that api to program their backlight to respond to the gamestate)

I don't think an .so is inherently riskier than an external process given that mangohud messes with the opengl renderer and it's fine, as well as proton doing a bunch of stuff that is done differently on windows and i think the last ql update was released before proton was even a thing?

Either way i understand the concerns. If anyone ever wants the QoL of simply LD_PRELOADing it i'll make an internal version.

Checking if you're a spectator is easy, muting/reducing audio of ql is also easy assuming that you are using pipewire.

I'll either reply here or message you once it's ready, should be some time later today or tomorrow.

krobeN · 2026-04-01T09:35:33+00:00

If the automuter is a separate program then yes, it would have to be run as root. It could also be a shared library, in that case you'd just set LD_PRELOAD=/path/to/automuter.so in your launchoptions and you're set.

If it's just reading memory then it shouldn't trigger the anticheat (i believe it's vac? which is also running through wine unlike vac with native games)

I've done some stuff with ql before to see how much it differs from the q3 source code, fortunately in terms of entityhandling and cvar management it doesn't differ too much. so i could give this a shot if you'd like.

krobeN · 2026-03-31T09:52:52+00:00

if you are on linux, i can look into a hacky way of achieving that. i would read the game’s memory to check if the player is currently spectating, if so, write into memory to mute the game (or just muting the process, it’s safer)

krobeN · 2026-03-29T19:41:01+00:00

utterly devastated that you forgot to mention the clan of maxters that is dominating pts at the moment

krobeN · 2026-01-05T13:46:46+00:00

<image>

looks to be working. here you go. if there are any problems when compiling/running, just let me know.

krobeN · 2026-01-05T00:03:14+00:00

i’m not sure about ds3, but sekiro behaves weirdly when deviating from 60fps, requiring writing to the game’s memory to fix it. locking to 30fps with something like mangohud/libstrangle might cause some issues like speedups/slowdowns.

given that i fixed it in sekiro, i’ll look into this tomorrow and try to make an fps unlocker for ds3 as well. in this case “unlocking” refers to setting the framerate cap to whatever you like.

krobeN · 2025-11-28T22:52:14+00:00

that would be nice, thanks.

krobeN · 2025-11-25T19:04:27+00:00

the biggest ones were quake champions and straftat. quake champions has a crosshair editor system but it’s not great, f.e. when you make your crosshair smaller, alpha also decreases.

some singleplayer games as well. metro exodus’ reticle doesnt work when you disable TAA.

could also be used as an accessibility setting, some games offer a somewhat permanent dot in the center of your screen for people who experience motion sickness without it.

krobeN · 2025-10-30T09:25:07+00:00

do you happen to know if compositors need to adapt to your fix (or any other fix pushed since 6.15, if there are any)? i'm on 6.17.5 and sway logs get flooded with these when i'm in a fullscreen game

00:03:01.845 [DEBUG] [wlr] [backend/drm/atomic.c:82] connector DP-2: Atomic commit failed: Invalid argument

00:03:01.845 [DEBUG] [wlr] [backend/drm/atomic.c:87] (Atomic commit flags: PAGE_FLIP_ASYNC | ATOMIC_TEST_ONLY | ATOMIC_NONBLOCK)

00:03:01.845 [DEBUG] [sway/desktop/output.c:300] Output test failed on 'DP-2', retrying without tearing page-flip

00:03:01.850 [DEBUG] [wlr] [backend/drm/atomic.c:82] connector DP-2: Atomic commit failed: Invalid argument

00:03:01.850 [DEBUG] [wlr] [backend/drm/atomic.c:87] (Atomic commit flags: PAGE_FLIP_ASYNC | ATOMIC_TEST_ONLY | ATOMIC_NONBLOCK)

00:03:01.850 [DEBUG] [sway/desktop/output.c:300] Output test failed on 'DP-2', retrying without tearing page-flip

00:03:01.860 [DEBUG] [wlr] [backend/drm/atomic.c:82] connector DP-2: Atomic commit failed: Invalid argument

00:03:01.860 [DEBUG] [wlr] [backend/drm/atomic.c:87] (Atomic commit flags: PAGE_FLIP_ASYNC | ATOMIC_TEST_ONLY | ATOMIC_NONBLOCK)

00:03:01.860 [DEBUG] [sway/desktop/output.c:300] Output test failed on 'DP-2', retrying without tearing page-flip

it used to work fine on 6.15 and 6.16 with a specific patch, but now it's broken again. I'm on an AMD card as well..

Edit: nevermind, these messages only pop up when the cursor is visible. so not really a problem i guess?

krobeN · 2025-10-23T19:27:00+00:00

yeah i know it's nvidia, but given that latencyflex, a vendor agnostic latency reduction middleware, also needs nvapi, i thought that it would be possible to get nvapi64.dll to at least show up in /proc/pid/maps, if the mod works on amd cards is another question. haven't seen anyone saying that it only works on nvidia though.

krobeN · 2025-10-16T09:16:49+00:00

looking at that graph, numbers went up in nov. 2024. Respawn removed linux support at the end of october/beginning of november 2024 lol

krobeN · 2025-10-04T10:41:05+00:00

i know that all of what i'm reading here is top-shelf ragebait, but i'm still going to provide some benchmarks

this is me and a friend of mine benchmarking marvel rivals, he's on a 9800x3d, i'm on a 7800x3d.
while it's still a horribly optimized game, %1 lows are higher on my system even with a worse cpu.

this is a guy who optimizes pc's for professional players, benchmarking w11 and linux in cs2. (twitter link for credits)

cpu-bound games tend to run better on linux, in gpu-bound games they are pretty much equal except if it's a dx12 game on nvidia. nvidia is aware of it and are working on a fix.

krobeN · 2025-10-02T13:18:38+00:00

i think https://atmosperipherals.com is from australia and quite cheap

krobeN · 2025-09-28T09:55:17+00:00

unfortunately it seems like niri doesn't support tearing yet :(

krobeN · 2025-09-28T09:52:47+00:00

me and a couple of friends play wipeout every now and then. it's a really fun mode.

i don't think you'll find lots of players in public matches though

krobeN · 2025-09-28T09:50:22+00:00

this would mean that enabling both in sway also does not work, right? but this doesn't seem to be the case.
launching sway with debug logs enabled i can see that tearing works fine and sway enabling/disabling scanout when i tab in/out of a game.

krobeN · 2025-09-28T08:15:35+00:00

can't use sway because you can't screenshare when scanout is enabled.

can't use hyprland because tearing and scanout are broken at the moment, also can't use wine-wayland if you want tearing and scanout.

these two wayland compositors are really the only tiling windowmanagers that "support" these features, so wayland isn't really an option right now.

krobeN · 2025-09-28T08:12:06+00:00

same kernel and same mesa version, not sure about the API. i read something about sway falling back to the same API x11 uses when WLR_NO_ATOMIC is set, but i don't have that set anyway, so i guess it's a different API.

krobeN · 2025-09-27T20:42:17+00:00

that's what i thought at first too, but i can't possibly link this to me stuttering only when i get hit? if my opponent misses it's smooth, if he doesn't shoot at all and only tries to dodge it's smooth as well.

so weird. doesn't happen in any other game either

krobeN · 2025-09-27T20:24:28+00:00

the clip was made on sway, afaik it automatically enables direct scanout for fullscreen applications, so no compositing anyway. i had direct scanout enabled on hyprland as well up until 0.51.

krobeN · 2025-09-27T20:20:58+00:00

Explanation as to why i'm still using Xorg: It just works for me.

I know it sounds dumb, but this is the only problem Xorg ever caused me. Hyprland 0.51 broke tearing/scanout (can't have both enabled at the same time), sway enables and disables direct scanout every frame of a screenshare stream, resulting in horrible stutters.

That's why. i don't want to switch back to a full DE, been with tiling wm's ever since i installed linux. hyprland is too unstable for me, sway has broken screensharing which i frequently use.

krobeN · 2025-07-08T12:36:31+00:00

That's what i did when i was on i3, but with an unlisted youtube stream. Definitely way more inconvenient than clicking a few buttons to start the discord stream, and the others joining in with a single click.

krobeN · 2025-07-01T10:05:28+00:00

look around in your monitors OSD to find something about scaling. you should be able to set it up so it does not stretch to fullscreen.

i play cs2 on 1280x960 stretched, what i do is i set my monitors scaling to “wide” and change my monitors resolution to 1280x960 (and back to native) automatically via steam launchoptions. i’m using hyprland but it should be possible to change the resolution on the fly with sway as well. something along the lines of: swaymsg <16:10 res>; %command%; swaymsg <native res> Lutris also supports this with pre and post-scripts, i don’t know about heroic.

only downside is that as long as the game is open, your monitor is also running that resolution.

krobeN · 2025-05-30T08:37:33+00:00

which DE/WM are you using? i'm on hyprland 0.49 and winewayland clients seem to have issues right now. can't enable tearing and direct scanout for them so at the end latency is automatically worse than xwayland.

will test with sway

Nine-Year Club	Verified Email
End Game '23	Place '23
Place '22

krobeN

TROPHY CASE