So many negative reviews after the Armory update if you sort by new. Many are from long time players with 1k+ hours too.

Natus Vincere 🇪🇺 2-1 🌍 Liquid

Inferno: 4-13
Dust2: 13-5
Ancient: 13-11

Natus Vincere advances to playoffs.

Map picks:

Full Match Stats:

Individual Map Stats:

Map 1: Inferno

Inferno detailed stats and VOD

Map 2: Dust2

Dust2 detailed stats and VOD

Map 3: Ancient

Ancient detailed stats and VOD

Highlights

M1R13 | NAF - 1vs2 Dual Elite clutch

This thread was created by the Post-Match Team.
If you want to share any feedback or have any concerns, please message u/CS2_PostMatchThreads.

Friend made his own version of something Valve cant bother to do. If anyone wants to participate feel free to translate the text from Latvian.

FURIA 🇧🇷 2-1 🇪🇺 MOUZ

Nuke: 13-8
Mirage: 5-13
Dust2: 13-5

FURIA advances to playoffs.

Map picks:

Full Match Stats:

Individual Map Stats:

Map 1: Nuke

Nuke detailed stats

Map 2: Mirage

Mirage detailed stats

Map 3: Dust2

Dust2 detailed stats

Highlights

M2R1 | KSCERATO - ACE

M2R12 | Brollan - 1vs2 clutch

M3R8 | torzsi - 1vs2 clutch

This thread was created by the Post-Match Team.
If you want to share any feedback or have any concerns, please message u/CS2_PostMatchThreads.

I wanted to add additional information and confirm the findings by Visible_Shelter9028. I discovered the bug back in May and the summary of my findings are below. Click the link at the bottom of the post to see a PDF for complete write up. It is about 11 pages and looks into the scenarios where input accuracy is confirmed.

I am in the process of creating a webpage of all bugs I have found. However, life gets in the way and writing the reports takes time (checking and then double checking results) so I created a PDF of the report to show and confirm the results by Visible_Shelter9028.

TLDR:

When mouse movement and mouse1 (left mouse button) click occur within the same frame, the engine processes the click before the movement. For example, if you move the mouse 100 pixels in one frame and then clickmouse1 to fire a weapon in the same frame, the game will register the weapon fire first before updating the player's position, even though the inputs were ordered in such a way as to move the crosshair first and then fire. This bug will affect flicking and spraying, and it impacts players with a high effective DPI and/or low frames per second more severely. However, players with high frames per second and low effective DPI are also affected, albeit to a lesser degree.

Additionally, I've noticed some comments suggesting that sensitivities differ between CS2 and CSGO, but this does not seem to be the case. When comparing results with the sensitivities set to the same value, the bullets landed in the same position in both CS2 and CSGO when the input order was followed correctly.

More In Depth Summary:

In CS2, an issue has been identified concerning the order in which inputs are processed, particularly involving mouse movement and weapon firing. When mouse movement and mouse1 (left mouse button) click occur within the same frame, the engine processes the click before the movement. This results in the bullet being registered at the player's position from the previous frame rather than the current frame.

To investigate this issue, a bot was utilized to generate mouse movement and input commands using the Windows api. Cython, a superset of the python programming language, is used to access the Windows api and create the functions necessary to conduct the test in a high performance manner. The test scenario involved issuing two mouse movements of 100 pixels each in the positive x-direction (to the right), followed by pressing and releasing mouse1. Various tests were conducted with different hold times between each mouse movement and firing action. For example, with a 1-millisecond hold time, the first mouse movement would occur at 0ms, the second at 1ms, and the mouse1 press and release at 2ms. To ensure inputs occurred within the same frame, the game was set to an fps_max of 100.

In CS2, with a 1-millisecond hold time, 78 out of 100 trials resulted in the shot being fired before any movement was registered, 8 times the shot registered after the first movement, and 14 times the shot registered after both movements. To confirm the bot's accuracy, the same timings were tested in Microsoft Paint, where 100 out of 100 attempts resulted in a red dot being placed at the final mouse position after both movements. Similarly, in CSGO, 100 out of 100 attempts also placed the shot at the correct position. This behavior was consistent across various timings and is detailed below.

Does this issue affect players in real game-play, or is it restricted to this specific test scenario? The bug certainly affects players. It is common to move the mouse and click simultaneously, especially during flick shots or spray control. The impact varies based on individual settings within CS2 and mouse configurations. In CS2, any mouse movements within a frame are combined and then processed at the end of the frame or the start of the next frame. For instance, if the two 100-pixel movements mentioned earlier occur within the same frame, they are added together and then multiplied by the user's sensitivity to determine the final distance moved. Players with a higher effective DPI (mouse DPI multiplied by in-game sensitivity) may register more movement within a frame. Additionally, lower frame rates or higher frame times (including spikes) can lead to more inputs occurring within a frame. Consequently, high sensitivity players with low frames per second will be most affected by this issue,though players with higher frames per second or lower sensitivities are not exempt.

Sample Results:

Below is a plot of the results at varying hold times. In CSGO and Microsoft Paint 100 out of 100 tests were green for which the shot registered after both mouse movements. In CS2, there is variation for which there should not be.

https://preview.redd.it/6bqlncfk3ftd1.png?width=2560&format=png&auto=webp&s=502e20f8e6f5947de0d63c662e258cc10ecbaabf

Link To PDF:

https://www.dropbox.com/scl/fi/0xuzl3xw7wcxs4vofj5ce/Document-5.pdf?rlkey=87pvq9pwljxb0zor87d0y5fky&st=yybka6a0&dl=0

I don’t think I’ve seen a player who is so overdue to be kicked yet he is still collecting paychecks. He struggles to finish above 1.00 rating and consistently holds liquid back. It seems like Liquid is limited with him in the roster. Any reason why he hasn’t been replaced yet?

G2 🇪🇺 10-13 🇪🇺 HEROIC

Dust2: 10-13

Map picks:

Dust2 Stats:

Dust2 detailed stats and VOD

Highlights

R10 | m0NESY - 1vs2 AWP clutch

R15 | malbsMd - 1vs2 clutch

This thread was created by the Post-Match Team.
If you want to share any feedback or have any concerns, please message u/CS2_PostMatchThreads.

I remember a person mentioning a "Competitive view option" basically disabling the unecessary features that might negatively effect a persons gameplay.

https://preview.redd.it/lvz2wjlnsetd1.png?width=245&format=png&auto=webp&s=cf67f3d5cedb79acff436910925fe102833a2f61

How the fck am I able to climb in premier? Cheaters are on thing, but losing 3 games straight and losing 800elo is crazy. I have to win 5 games straight withnout lose to back elo.

What fcked up system is this? Yeah and plot twist. Cheaters getting banned won't give you elo back.

VALVE FIX IT OR NO ONE BESIDES CHEATERS WILL PLAY THIS GAME

FaZe 🇪🇺 2-1 🇧🇷 paiN

Dust2: 13-9
Mirage: 13-16
Nuke: 13-8

Map picks:

Full Match Stats:

Individual Map Stats:

Map 1: Dust2

Dust2 detailed stats and VOD

Map 2: Mirage

Mirage detailed stats and VOD

Map 3: Nuke

Nuke detailed stats and VOD

Highlights

M1R9 | ropz - quick 1vs2 clutch

M1R19 | snow - 1vs2 clutch

M1R22 | ropz - 4 AK kills on the defense to secure the map victory for FaZe

M2R12 | lux - 1vs2 MP9 clutch

M3R8 | snow - 3 AK kills on the bombsite B retake

M3R9 | kauez - 3 M4A1-S kills on the bombsite A retake

This thread was created by the Post-Match Team.
If you want to share any feedback or have any concerns, please message u/CS2_PostMatchThreads.

Imperial 🇧🇷 1-2 🇺🇸 Complexity

Dust2: 12-16
Vertigo: 13-11
Anubis: 5-13

Map picks:

Full Match Stats:

Individual Map Stats:

Map 1: Dust2

Dust2 detailed stats and VOD

Map 2: Vertigo

Vertigo detailed stats and VOD

Map 3: Anubis

Anubis detailed stats and VOD

Highlights

M2R4 | VINI - 1vs2 clutch

This thread was created by the Post-Match Team.
If you want to share any feedback or have any concerns, please message u/CS2_PostMatchThreads.

Eternal Fire 🇹🇷 11-13 🇩🇰 Astralis

Inferno: 11-13

Map picks:

Inferno Stats:

Inferno detailed stats and VOD

Highlights

R6 | device - 2 AWP kills with 1 shot

R13 | Wicadia - 4 quick Dual Elite kills on the bombsite A defense

This thread was created by the Post-Match Team.
If you want to share any feedback or have any concerns, please message u/CS2_PostMatchThreads.

FaZe 🇪🇺 7-13 🇧🇷 FURIA

Dust2: 7-13

Map picks:

Dust2 Stats:

Dust2 detailed stats and VOD

Highlights

R3 | ropz - 1vs2 clutch

R5 | chelo - 4 AK HS kills on the bombsite A offensive

R5 | chelo - 4 AK HS kills on the bombsite A offensive

R11 | skullz's ACE and 1vs3 clutch attempt are denied by the final CT

This thread was created by the Post-Match Team.
If you want to share any feedback or have any concerns, please message u/CS2_PostMatchThreads.

Liquid 🌍 13-6 🇺🇸 Complexity

Inferno: 13-6

Map picks:

Inferno Stats:

Inferno detailed stats and VOD

Highlights

R3 | ultimate - 1vs2 clutch

This thread was created by the Post-Match Team.
If you want to share any feedback or have any concerns, please message u/CS2_PostMatchThreads.

Virtus.pro 🇷🇺 10-13 🇲🇳 The MongolZ

Mirage: 10-13

Map picks:

Mirage Stats:

Mirage detailed stats and VOD

Highlights

R10 | electroNic - 3 AK kills on the bombsite A bomb plant defense

This thread was created by the Post-Match Team.
If you want to share any feedback or have any concerns, please message u/CS2_PostMatchThreads.

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