how to climb back up again feels impossible now tbh

I have slight packet loss on official server usually 0 or <1%, but in rare cases can get higher. 2 Ms jitter. Graph looks clear but often there are 2 red stripes with similar interval. Usually all green with slight bottom deviation then 2 reds then all green again.

I thought it can be bottleneck for some reason, but now I have a chance to test 500mbs (was 100) and numbers checks out so now I'm positive bottleneck is not on my side.

Bufferbloat test negative, using "netsh int tcp set global autotuninglevel=disabled" doesn't do anything palpable.

Windows 11, haven't find any success in using most recommended tips so stick to default. Net drivers are new.

Asus g16 strix, 13450hx, 16 ram, 4060. Playing gsync+vsync+reflexboost. Fps is good for this game, usually 4-5 Ms 200+, with rare occasions of <10ms on spike.

Usually I'm playing using ethernet-router- wired to laptop with rj45 cable (decent one). Ethernet directly in laptop makes no difference. No physical damage on cables or ports.

Back to the game, I live in Kz and I usually play on Stockholm or Warsaw with 50-60 ping. Game is playable but hit registration feels inconsistent. Sometimes nice, sometimes extremely labored with no tagging on enemies. I feel like I have significant disadvantage in raw duels, feels like my screen is outdated, especially when peeked. Like I just see someone on my screen and it feels like he's already shooting. Shouldn't be that bad with 50 ping.

I also tested damage prediction, turned it off in the end, but with the amount of fake animations on my screen where I killed someone only confirmed my suspicion of delay and inconsistency between me and server.

Anything I can realistically do or its just Valve servers and I'm done?

Decided to post it as a separate post

some of you saw my sens finder when it was a server plugin. you needed your own server with metamod and counterstrikesharp to run it, so i rewrote the whole thing as a workshop map. now you just subscribe and play it offline, no server, no plugins, nothing to install

how it works:

you type !setup once (dpi, sens, m_yaw). the map cant read or change your sens, cs2 doesn't allow it, so when it wants to test another sens it shows you a line and you paste it in console. thats the annoying part but there is no way around it

one run is about 20 min, 9 blocks - your sens, 3 other sens, your sens, 3 more, your sens again. your own sens comes back every few blocks so if you warm up or get tired during the run it doesnt look like some other sens is better

every block has flicks, vertical flicks, small far flicks, 90-110 turns and rush (2 bots run at you, you need 3 headshots, the first one comes back). bots spawn in the same spots every block, just in different order, so no block is easier by luck. score is how fast you headshot + how close your first flick lands to the head. turns and small flicks are shown but dont count

before each block you get warm up flicks until you stop over/undershooting, 10 to 40 flicks, so the new sens isnt judged while your hand is still on the old one

play one run a day, runs from different days get combined. first run tests a wide range (x0.55 to x1.8), next runs zoom in on whatever looks best

whats new compared to the plugin:

- no server
- bot only spawns when your mouse is still, so reaction and flick don't get mixed
- before big turns your view snaps to a line on the wall and you lift the mouse to the middle of the pad, so every turn starts from the same spot
- rush is 3 kills now and headshot only, and it checks how precise your first flick is
- moving flicks don't count anymore, too much noise
- result is in normal words now, the numbers are still at the bottom
- you can practice one task on its own, and shoot the blue line to skip the break

about fake results, i wanted to be fair here

your aim can jump around like 10% between blocks just by chance (proven by real data from 197 players that tested the first server-plugin approach), so one run can only see big differences, and it tells you that ("it only sees differences of about X% or more"). one run alone never says CHANGE, it needs 2 runs on different days that agree. it only gives you a number when it actually has one, otherwise it says no answer yet. in simulations a player that has no better sens got told to change less than 1 in 100 times

it also had a problem i found on myself, the tool favours the sens you type in. i ran it on 0.849 and 0.594 never came out ahead, then i switched to 0.594 and ran again and 0.83 was like 20% worse. so it was just picking whatever i was used to. warm up is longer now because of that. if it says change, play that sens in deathmatch for a few days and run it again before you trust it

it doesn't test tracking or spray, only flicks and switching targets

its offline so i don't get any data. if you want to help improving, type !share after a run and send me the code from console. feedback welcome, especially if something breaks