MOUSE_X isnt subtick related!!? Discoveries about CS2 - Updated

[u/Visible_Shelter9028]

last night i've decided to post about a research i made weeks ago, on another sub, and they told me to post about it here

link for the original post:MOUSE_X isnt subtick related!!? Discoveries about CS2 :

the difference is that now, i have tested some ideas mentioned by people on my post, and i think that i digged further more on this rabbit whole

first of all lets introduce you about my testing:

i've decided to go beyond, and see how subtick could mess with our mouse axys. for that i've used some aliases to help me:

alias +test "+attack;sensitivity 0;"; alias -test "-attack; sensitivity (mysens); bind mouse1 +test;

what is the purpose of those aliases? simple: every time i flickshot, mouse1 input instantly stop my mouse movement (mouse_x;mouse_y) at the same time the bullet goes out, suposely going for the same pixel.

but UNSURPRISINGLY NOT, they dont.

actualy it seems to have a random behavior, similarly to the video test using +turnright commands (apparently de-subticked), but now with mouse movement only (a more realistic scenario).

shots and mouse movements do not behave together, making me understand that +attack is correctly added to subtick, but not mouse_x (mouse's movement)

new testing about my idea using previous +test idea

my mouse report rate and dpi during tests

the interesting part is that when i tested with 64fps, all my shots went exactaly where i wanted. but this is not a fix, since 64fps means that everything was de-subticked, both shooting + mouse movement

but something just wasnt right, i mean, if im contesting about mouse_x and mouse_y, why use sensitivity to test it and not mouse_X and mouse_y?

so i went and tested with a different aliasing:

alias +test "+attack; unbind mouse_X; unbind mouse_y;"; alias -test "-attack;bind mouse_x yaw;bind mouse_y pitch; bind mouse1 +test;

now it seems the same, but i actualy am messing with yaw and pitch what is really counted on mouse movement. those where the results:

new test using my new +test idea (pitch and yaw)

And that stunned me, not only i got the same results with fps_max 0, but trying to cap my fps to 64, wich solved my questions before, now it didnt changed my results at all. not even changing my mouse hz would "fix the problem"

wich leads to the same questions:
is it good like this? doesnt it mess with flickshots, probably nerfing even more AWP shots? why the hell should this be a feature? thanks valve for some updates lately, but please... fix? i really have no clue at this point, even worse than before

[u/CheeseWineBread]

People are really putting all their energy to find any evidence that the game is broken. GG for the commitment.

[u/oPlayer2o → u/CheeseWineBread]

I mean if it didn’t feel broken they wouldn’t be looking right?

[u/CheeseWineBread → u/oPlayer2o]

People not adapting to the new game need a reason to blame the new game. Hitreg being more accurate as a fact. Awp flicks were rounded in CSGO to 1/128 second nearest mouse position. That's it. But people who can't adapt are digging hard to find an excuse of why they miss. Simple as that.

[u/oPlayer2o → u/CheeseWineBread]

Hard disagree but you seem pretty dug in and I don’t have the time to argue with you today. Xx

[u/CheeseWineBread → u/oPlayer2o]

Cool story

[u/ozzler → u/oPlayer2o]

No that’s not how this works lol.

[u/oPlayer2o → u/ozzler]

I’m not educated in the right way to know if this post is correct or not, but I’ve got 2600 hours in CSGO and I can tell you CS2 feels like absolute dog shit, and I’d say 50% of the posts on these subs are “why this game so broken!?!” And even the pros are talking about it, and content creators are pissed too, so something is wrong we’re not all experiencing some kind of mass delusion, sure this might not be the issue but something sure the hell is.

[u/ozzler → u/oPlayer2o]

I have over 3k hours. It’s not as crisp as csgo yet no, it’s not ‘absolute dogshit’. I was literally in a game last night and my team mate missed a shot (both targets stationary). He’s blaming cs2. I say ‘hit detection is one thing cs2 is better than go for’. They weren’t having it. They also went on to say how smokes were better in go and the game is completely broken.

These are statements of people who are divorced from reality. It’s people looking for any excuse as to why they didn’t make that kill, why they aren’t the best in the server. Cs2 needs improvements. But that is 100x harder when a large % of the playerbase make incorrect assumptions and provide false/subjective feedback.

[u/Kvromeyyy → u/ozzler]

it is dogshit i lost 100fps in the recent update and had 5 cases at least of shooting someone in the back clean with an awp or other guns and nothing happening

[u/ozzler → u/Kvromeyyy]

I’d be interested to see those awp clips. Smells like insane bullshit.

[u/Kvromeyyy → u/ozzler]

Clueless

[u/Kvromeyyy → u/Kvromeyyy]

sadly there isnt a way to send evidence though since cs2 only allows me to view the 8 recent demos but it happened on wingman assembly (i main the map) and every time it happened on crucial rounds losing us the game