Just saw this video, and wanted to post this. See that you posted this 23min ago :D Question, since you have to use other bind methods (alias and cfg execs) in cs2. Could this possibly not create a level of 'lag'/delay with the testing? Would it not have been better to use the same bind method in CSGO to see if it works the same there?
I was just about to correct you on that one, it doesn't really matter though, your theory might be close to what's actually happening though. I'm sure valve's servers are powerful enough to handle the load, BUT we're currently in beta testing which means valve are logging absolutely everything happening all the time which puts a ton of strain on the servers. The subtick system would be amazing for lan or very low ping games 5-10 on all players, higher ping makes it a mess though, I surely hope they have an idea of how to compensate that. Great video.
the only 2 flaws that ive found were about: 1 subtick partially uses 64 tick rate for things that are less demanding live grenade trajectory, that why on 128 tick even on cs2 lineups are diferente. and 2 that the sub tick need to register every movement that ur mouse does, it doenst need to process every thing, just the position of your cursor on the fire.
Valve never said subtick sends server requests dynamically, and it would be pretty hard to implement something like that because the server won't have a good trigger for when it updates the clients, since it has to update them all. It's more likely subtick is just timestamped event data being sent on a fixed tick rate so teh server can theoretically simulate the events more accurately
I thought the client sent the tickrate right away, that's the point, not because the shots were not accurately registered in time but the objective is the faster validation and display back to the client, so we're supposed to see less missed shots that were displayed locally (happens often) or maybe as often but the false impact will disappear faster.
so subtick is only a minor deconfliction improvement but if the mouse pos is not updated as often, it's limited in its positive effects, maybe it shouldn't have been inflated by the valve communications @@cicolas_nage
correction: if i understood correctly, subtick doesn't stress servers any more than normal tickrate as it just registers all inputs between ticks and executes them at that place and moment when the next tick comes instead of waiting for the next tick to execute all of that (for example, if in between ticks 1 and 2, a player was in the center of your crosshair and you fired, but then moves out of your aim when tick 2 arrives, subtick would know that and register it as a hit instead of a miss)
I don't think this is a server stress problem, but instead, a display problem - human baseline reaction time is around 10milisecond, which actually coincides with the 15ms 64 tick rate in CSGO, that is why it feels natural to most players when they flick shot timing, or even spraying because it's only after we see and register in our brain (which doesn't have sub tick lol ;) ) ak-47 start to shoot sideways that we adjust by a counter-motion using a mouse to spray control. But that doesn't explain why the macro this guy used to stop and shoot at the same time will cause the crosshair to not be on the shothole - but you can apply a similar theory, most gaming keyboards have an input latency of 1-2milisecond, and the receiver (PC) + loading into CS2 software will up this to around 5-15 ms depending on your specs. Since this issue doesn't always occur (sometimes the crosshair is on the shothole), in science, we call this unreliable, so there 'must' be a random error that is causing a disconnect between what "you see and what you get", and I suspect that sub-tick is working compartmentalized for single actions such as shooting (aim) or movement keys, but not calibrated to work well when together. You might argue that sub-tick shouldn't cause this issue (which is what Valve is insinuating), but from a practical perspective counting units such as ticks is incredibly important when trying to achieve replicable results (which is a fancy way to say reliable results). For example, if you have a ruler with millimeter units and ask 10 people to measure the length of a 4.25mm string, they are most likely going to give results such as 4mm, or 4.5mm because your measuring equipment is not accurate enough to give more decimal places, so you naturally just round to a nicer number like a half. If we do the experiment again with a ruler with a mix of units such as mm, cm, micrometer, and nanometre (to emulate how sub-tick tries to get every input in between ticks) and then ask 10 people to measure the same string, some people won't try hard to measure and just go with 4mm, some people will use the smaller units and try to get 4.2mm or even more extreme some people will attempt to go 4.2479...mm, now you have a wider array of numbers as results which represents the inconsistency that you feel, and amplify that with so many actions that you are doing in CS2, it's more likely than not that errors will occur - and reasonable that we have this problem.
Makes so much sense, I feel like something has been fundamentally wrong since the beginning, awping feels off with flicks and so does spray control with rifles, good video man! To be fair I think this does make it unplayable to a degree, with peek advantage being so heavy at the moment everyone is trying to wiggle peek or re peek for advantage so most of us are moving, if you sit and try to hold an angle half the time you will die simply from behind a wall without seeing the other player.
literally. i've gone from hitting the majority of my flicks, to the bullet always going to the left/right of a player. It is actually game breaking. Raw accel also doesn't see to work so my sens is fixed unlike in csgo
Awp feels of because in CSGO when you flicked the bullet would slingshot to the position you flicked after your shot, like a string attached to the bullet and cursor, in CS2 the awp shots perfect, to perfect. the bullet will land exactly where you shot and not travel with your flick cursor thats why people missing a lot now. As a awp main i noticed that too that i sometimes shot like silver 1 in CS2
@@ownagebox how can you say in ''cs2 the awp shots perfect, to perfec, the bullet will land exactly where you shot'' When the video, CLEARLY, shows that it doesnt
@@cuppavids you can clearly see hes always barely moving after the shot in CS2 most visible with awp and auto the bullet holes are exactly where he triggers not where the cursor ends. I had some other article about this with a were the shots where scripted points, maybe i can find it
Question is, WHEN do you click? In CS2, when you click, it remembers the exact position/rotation and that's where your bullet starts of from. In CSGO, your click is queued for the next tick and THEN it looks at rotation etc, so there is a random delay between clicking and the click taking effect. Therefore it's possible in CSGO to click->move mouse and the shot fires from the new position and not from where you clicked. In CS2 it will fire from where you clicked, being more precise. What you observe right now, is that the animation is still tick and not subtick dependend so it fires on the next tick, while the actual shot got prepared on the subtick precision and therefore it feels off. The click for the shot probably happens a few moments before the rotation ends. In CSGO everything was on tick so it was executed when the rotation ends. In CS2 it's now "off" because the action is registered more precicely.
This is correct actually. It makes sense. It was actually the animation and the scope that stopped later, rather than the shot being off or registered earlier. So even if it seems off, it’s actually more accurate. It’s kinda confusing :))
Be careful with the assumption that your mouse movement input is sent to the server immediately. The subtick system just receives the input with a timestamp, indicating how far into the tick the action happened. Games can handle high polling rates, but for online games they have to linearly interpolate between frames to keep Internet traffic of inputs at a manageable level. Source: I've been programming 2d and 3d applications for about 6 years now and I'm working on a small game engine of my own. Valve will come up with a solution for this. Since this is not an easy problem to fix, it might take them some time, but they will come up with an acceptable solution
Is this even an problem lol? People got used to press fire a dozen miliseconds before stopping crosshair at the target, and the game registered it at the end of the tick. Simply muscle memory issue. Now it shows off as people's shots appear before the crosshair stop. Edit: Shots are still processed when the tick ends, it's that now they appear accordingly to input time. Maybe they make a line between 2 crosshair positions, and, let's say if you pressed at 0,5s after previous tick, shot will appear between 2 positions.
This is all because of the subtick system, in csgo there is server compensation but in cs2 it registers 2 things, where shot started, where shot should end, immediately due to subtick. For me personally this feels really bad. After playing cs2 for a week i went on to play csgo again and god the shooting felt like a breeze of cold wind on a sunny day.
I wanted free leetify premium for a day, so I changed my tag within csgo and had to play a game. God damn is it such a crisp game when you put it up next to cs2. I'm really enjoying cs2. I can see the promise in it, but it needs so much work. I think Valve has no choice but to delay or fix this fast.
Exactly, for some reason the shooting in CS2 feels just weird and I could tell that almost immediately. Then I tried to go back to CSGO and man it feels so much better.
@@Kylo_tonny I think it will be many fixes over the next year. I think we get a slight delay while they iron out the worst of it, but this is a new CS game on a new engine. It'll probably take time to fix like csgo did.
I think that bullet goes exactly where You clicked Your mouse. Animation and console command processing probably is still in ticked system. This way bullet goes where you shot, but the unscope animation and stop rotation are still processed on the end of tick. This is why it's sometimes close to the crosshair (You shoot and send stop rotation command close to the end of tick, so You stop rotation almost immediately) or really far away (you shoot on the beginning of tick and move till the end of it, so You have almost 1 tick of discrepancy (15ms) between shot and stop). This is also why it feels of, we have lagless shooting, where bullet's can go back in time to be resolved, cause they have timestamps, but rest of the game - is still bound to the ticked system. Where in CS:GO - everything was resolved on the end of the tick. And as I always say about those things - in games we can pretty easily accommodate to latency as long as it's stable (that's why we can play games in 30fps as long as it's locked, and we get new frames in stable manner) - but when latency starts to fluctuate - it fucks our gameplay. And that's why game feels bad when it dropps frames from 300 to 150 (where on stable 150 it would be playable AF for anyone after some accommodation period) and this is why shooting feels of as You can't accommodate for the lag that fluctuates between 0 and 15 ms.
yeah this is what it is and why spraying feels a bit off. the shot is perfectly on your crosshair at the time you shoot because that’s the whole point of sub tick the animations are just a tiny bit delayed. still feels jank because it’s out of sync but i feel like videos like this should have almost any amount of research behind them lmao
If you have so much knowledge why aren't you a game developer? What you're saying sounds like a bunch of word salad, he tested on CS:GO first for a reason to show that 64 tick is more stable using this option.
@@scambaitspidey3470 he is literally right, 64 tick system wasnt more stable, it just sent everything a the end of the tick, making it so that if you pressed in the middle of a tick, the bullet would go where the crosshair was at the end of the tick, because this state was the one sent to the server.
Actually the bullets hit right where you click them thanks to subtick but the visual representation of it is only rendered at the next tick. That is the reason why they are in sync in CS:GO but in fact the shot in CS:GO is delayed until the next tick and NOT hitting the spot where you clicked. This is also the reason 128 tick in CSGO feels so much better than 64 because ticks are only half as long and your shots are then hitting closer to where you actually clicked. With subtick though it registers at that exact same moment of the click but the shooting animation comes 1-16ms after depending where you shot between the ticks and the bullet hole is represented where it is according to the subtick/where you clicked. This means it would still yield you a kill if you clicked on the enemys head even though at the time of the tick the enemy might already be away from your crosshair. When you understand how the engine works in CS2 this is actually a good thing. They just need to adjust the visual part of it to match better with the client side actions.
The red and blue are where the client and server thought the shots hit because he is shooting and stopping instantly thats where he was aiming at the time and yet the shots are not going in the same place so if it is just a visual representation and not shots lagging behind why when he is stopping spinning are the shots still behind?
I think your theory is right. Assume you have 0 ping and say you shoot at exactly the start of second 1 of the server's time, the mouse updates 1000 times a second, therefore, the server receives the shot at 1/1000 of second 1 but cannot send it back until at least 16/1000 of second 1 because the server is still running on 64 tick. Introduce 30+ ping and you're now waiting at least 30+30+16=76ms until your shot is sent back from the server. Do this same test with 100 or 200 ping and the distance from the shot on the wall to the crosshair should be even greater. If someone did that then it would confirm this theory. In CS:GO this shouldn't be a problem since the client and server both run on 64 tick, so they know exactly when the shot happened and if they agree, then that's it, it just gets received the same way it was sent out.
@@Tricker1266 Actually in CSGO the shot will just completely miss solely due to the delay of 64 tick when ever the click has happened just after a tick.
I saw a video that was posted on Reddit recently where someone made a macro that would move the mouse to one side and then in less than 1 frame would flick to a target, fire, then move off the target (Sub-frame mouse input, or why flicks feel different in CS2 by MrPyber). In CSGO the shot would be fired at the same location as the next rendered frame, but in CS2 the shot was fired exactly where the mouse was when the input was received. I can't claim to know what's going on here, but it could be that while shooting is recorded at the exact ms the input is received, the visual updates like unscoping don't occur until the next frame. As for the spin test I don't have a guess. As far as how many mouse inputs CS2 needs to handle, USB mice can only send inputs to Windows at up to 1000hz independent of the DPI. Some USB mice can "pretend" to be multiple devices in Windows and feature 4000hz polling or more, but the highest I've seen is 8000hz. Maybe now that CS2's mouse inputs aren't capped at your frame rate, ultra high polling mice will explode in popularity.
I think this is arguably the best explanation as to why this is a thing. The subtick system works in-between frames - and as a result even with the most precise of slow motion recording - itll still seem like it didnt hit the same frame granted it tracks the time you hit your mouse without account for frames. If your mouse's polling rate is moved down to your monitor refresh rate (144hz, 60hz, etc) you'd likely see the bullets hitting in their exact positions similar to CSGO. Could be wrong though.
I keep my mouse at 2000 MHz polling rate, but shooting still feels off...not to mention spraying is the worst thing in the game atm. Will try 4k polling rate to see if it feels better
This is the real explanation. It isn't that the shooting uses the mouse position form the last tick but that the unscoping/movement stopping only happens on the next tick. I.e. the movement stops late which makes it look like the shot hit too early
He probably sends mouse events using native code to the window. Instead of moving the mouse along a spline which sends a mouse event for every coordinate on the spline he hops the mouse from coordinate to coordinate. hop(500, 500), leftclick(), hop(1000, 1000) for instance. Doing this you can basically do all the 3 actions in a time frame of 1ms. I thought CS2 used timestamps which normally uses nanosecond precision. Or maybe Valve is cheap on the data traffic and uses millisecond precision since 64 tick is 15,625ms/tick .
It occurred to me that in cs2 i miss a lot of flicks, most of the time when it happened on cs:go I could recognize that I simply missed it, while on cs2 it happens VERY often that I genuinely say "wtf?" Since I'm pretty sure I should've hit that But I'm always too unsure to say "It's cause of new bs valve made" and most of the time I simply justify it with "I'm bad bruh"
@@StarComet7 From my understanding it's not exactly like that but feel free to correct me if I'm wrong; don't want to go around spreading misinformation From what I understood if we were to take 1 singular tick and divide it in 100 fragments, no matter if you shot it in the 64th or 99th of a tick, it will be registered as if you shot it at the very start of a tick (1/100) So (impossibile example but exaggerating things help out understanding) if I were to move my crosshair 500 pixel away from the registered position where my crosshair previously was, then my shot would be registered as 500 pixel before my current position Again, I'm not 100% sure I understood correctly so if I'm wrong please correct me
@@whitinnn what you described is actually how csgo calculates. In cs2 the tick would carry the timestamp of you click and the server would register a better guess of you crosshair position inside the tick.
The reason this feels so wrong is because Sub-Tick is working properly, you DID actually click at those locations but the kicker is your gun didnt shoot till the actual tick update making your shot look delayed to where your bullets are actually going.
no, the point is that the animation of the shot and tracer happens on the next tick. wheres your shot calculation is sub-tick. So it will look like you're shooting later than you actually are, and later than when the server calculates your shot. hence, the actual shot is more accurate than the animation and tracer. @@PultsMoizer
@@PultsMoizer its not, there are other videos that perfectly show that where you shoot is pretty much where the bullet lands, the animation is just very delayed
This video is great! I do have one comment. I could be wrong but I think your reasoning is a bit off. Cs2 servers are still 64 tick. Originally in csgo your inputs would be registered every tick. The subtick system in cs2 now LOCALLY saves your inputs between ticks with timestamps. When your computer communicates with the server on the next tick, it will register your shot to where you ACTUALLY clicked the mouse because it has a timestamp associated with the input. The important thing about this system is this: MOVEMENT IS NOT INCLUDED IN THE SUBTICK SYSTEM. The reason it's not included is simple. Visuals are updated locally before they are updated to the server. If it wasn't, it would be the equivalent of playing the game in 64 fps. If visuals were included in the subtick system, your crosshair would flick back to where your bullet was shot on the next tick. This is a glaring fundamental flaw with the subtick system. I think it is the cause of this problem along with other issues in CS2 including the "Peek advantage" issues. Overall, I'm not certain of this theory but I am pretty confident. If this is correct, the subtick system is working as planned... it was just a bad plan.
Quick fyi on how source/S2 networking works- the game is “simulated” at whatever tickrate it has (which is why nade lineups were different in GO). The game also sends packets every time it simulates. The current working theory for subtick is that every input is timestamped as best as possible relative to whatever frames it happens between. Additionally, chances are, they’re not recording each louse movement. They just check your mouse movement every frame and send that to the server, and then also log your mouse movement every time a shot happens, so that the shot isn’t misaligned.
bro! the fact that this is your first youtube video, it is doing so good! the content you provide is better then most. keep up the good work and let this channel grow huge! and thank you for making this video, it explains why so many of my awp flicks miss😂
the DPI part is wrong to an extend. what you're saying is right but its not the DPI that determines how many inputs/sec your mouse sends. Its the hz of the mouse. The DPI determines how many counts (also called counts per inch) your sensor does when you move your mouse. the updaterate which sends this data to your computer is hz. so for a 1000hz mouse that is 1000 updates/second and it doesn't matter whether you move your mouse or not. the data will get sent anyways. i personally use a 8k hz mouse and 8k hz in cs2 feels a lot more reliable than 1000hz is all i can say. this is most likely because the 8k hz sends the data earlier (because sending more often/sec = sending earlier to the actual position of the mouse). To sum it up: DPI determines how finely-grained the mouse's sensitivity to movement is, the polling rate measures how often the mouse checks its sensors for changes.
no he's as right as you in a way, the mouse do not sent an move event when not moving, the maximum rate of change for the mouse is when the sensor detect any movement at each mouse refresh tick, if some tick don't contain any movement, there is no event. So the refresh rate is the maximum event rate, and the actual rate depends partially on the DPI and movement speed of the mouse as well as the resolution, I'm sure cs or the mouse driver don't consider a mouse position change until it's bigger than a pixel. What is wrong here is the scale of the argument, imagine you move half of the screen in one sec (approx 1000 px for full hd) you already max out the fastest mouse out there (1000 Hz), and a half screen flick is not uncommon and often way faster than 1 sec, so most of the quick movements will absolutely max out the refresh rate. If you play 800 600 and you have the speed of a snail, then the mouse events will be a lot less frequent.
wow thx, this really explain how my awp shot somehow missed with me flicking right on the body. I was so confused since I missed like 2 shot that feels like should have hit, to the point I just stopped picking up the awp
I guess it makes sense. I'm one of those guys that when I pick up the awp I flick crazy fast like I'm trying to break my wrist, and I've struggled adjusting to cs2. My other friends who use a more passive / slow style rarely flick fast and have much more easily adjusted to it.
Same, I'm not flicking all the time, but I do flick, I need it for no scopes for example or if the enemy wasn't in the side I thought he was then I flick to shot him.
Subtick is a clientside feature. The server still operates at 64 tick. The only thing that subtick means in the end is, that it has certain actions that send updates to the server at any time, not bound to a tick. Regardless, you have a very interesting find there. I hope valve sees this video. The reason why this is happening is hard to figure out from the outside.
its the opposite, the one validating your shots with the perfect timestamps is the server, not your pc, if not, hacker would validade shots however they wanted
@@nexuhs. yes but the client will send the stamp to the server and the server will decide. but it isnt working properly. lag, performance, latency and other issues are favouring better systems and ping
It doesn't even send updates to the server at any time. It is still sent in packets every 1/64 second. It's just that some actions are now time stamped, so the server can more accurately calculate when something happened and in which order.
The worse your ping the more you see and feel this effect. Even now. You can still see this problem in community servers that you have 60 or higher ping in, joining a closer one feels drastically different
CS2 still runs on ticks, you can verify this because the game will send 2 data packets to the server 64 times per second. That makes 128 packets which they need to send because the subtick system really just adds metadata to each event, the metadata makes the packet too large for a single packet so two are sent. It could still be related to the subtick system but not in the way you suggest.
my main reason for commenting and liking is to boost your video. Your explanation seems on the money. And its frankly stupid that they never added a tick update for firing the weapon. The subtick system is probably quite difficult to code around.
I've seen someone that explained that in csgo the bullet goes to where your crosshair is when the animation happens. But, in cs2 the bullet goes to where was your crosshair at the moment you clicked your mouse. Im not a game developer either and no absolutely nothing but i think its a fair summary.
Easily my fav part of the video is the humility and reminding everyone that this isn’t some kind of confirmation of fact, and just a test. Love to see that
Cs2 is a mess and valve doesnt have any competent developers working on anything but dota and steam. Theyll kill this game if they keep going like this
Awesome video. You showcased the bullet inaccuracy really well, and I hope Valve looks into it. I do want to mention however that the part where you mention 160,000 updates isn't quite right. The server will only update 64 times per second. If you move your mouse 1 pixel, or 1,000 pixels, it doesn't matter. After 15.625 milliseconds the server will see your new mouse position, and your character model's view angles will be sent to all other players on that single tick. I don't know exactly how sub-tick updates work, but if I had to guess I would say all commands (or inputs) are marked by a clock independent of actual game ticks. The clock can be used to see when, within a single tick, a command was issued. For example, if the game is on let's say tick 1000 (since the map started) then the games clock would be 15.625 seconds (yes, seconds), which means tick 1001 will occur at 15.640625 seconds. Now if you send a command such as +attack in the middle of tick 1000, the clock would read 15.6328125 seconds. By marking the player's command +attack with that specific time value, when tick 1001 finally occurs, the command will go through, but not before taking that clock value into account. For example, if two players fire their weapons on tick 1000, we can determine who actually shot first by examining both of their clock values for each of their +attack commands. That would be one use case for a sub-tick clock assuming my guess is accurate. It could be used further to determine all sorts of data such as view angles between ticks, when a command occurred. It's hard to say exactly what's going on at the moment, but take my theory with a grain of salt.
Bullet inaccuracy? What? No. It's you who is inaccurate. Gone are the times when you guys rely on luck to hit flicks that doesn't make sense. Imagine in real life you pull the trigger and then you flick and that's only when it fires. Doesn't make sense right? This is the accurate way.
in fact locally on your client, the render will show the last local mouse position, if you get 300 fps and your mouse is 500 Hz, the view angle will be updated 300 times a second using a position which is max 3/5 of a frame old (I did the math at random), so the test he's doing is comparing this local position to what ever position gets recorded by the server prior to validating the shot and then displayed at the next tick when the server response gets used locally. It means that what he is showing is comparing the shift between server shots and local shots, for instance in a game, some shots seems straight, display impact, then disappear and completely missed, because the client must display something temporarily before updating with the latest info from the server. The servers send an updates every bunch of frames at the 64 tick rate, the diff between csgo and cs2 is how much the position changes. Subtick means that between ticks, the clients send more often update potentially, because it sends right away key press. Mouse events while rotating are at the max FPS (I don't think cs registers position multiple times between frames, all the code is frame based). If the subtick was triggered even for mouse events, the number of events received will be enormous (I'm all for it even then) so the cost for the servers will rise, it could improve the shift but I don't think it's even that, because csgo does better at 64 ticks without subticks, so I'm sure it's related to another difference, like the server deconfliction policies and even it could be caused by some random bugs in the new code used in cs2 (I'm sure they finally rewrote core stuff)
@@raph151515 "It means that what he is showing is comparing the shift between server shots and local shots" The problem is that he is using sv_showimpacts 1 which shows local bullet prediction as well as server prediction. If there was a shift between client and server we would see the blue and red boxes misaligned greatly every time. "Subtick means that between ticks, the clients send more often update potentially, because it sends right away key press." This doesn't appear to be the case. A RU-vidr named MrMaxim performed a Wireshark analysis of game packets months ago which showed that there were no additional packets being sent. Something worth considering is that Valve cannot afford to congest the network in a fast-paced game like CS2. Fewer smaller packets is the best way to ensure low bandwidth. It's also the reason why they use UDP packets for speed. 160,000 packets per second has the potential to literally knock people offline. In MrMaxim's video, Valve's official 64-tick server transferred 64 packets per second. This is why I believe that sub-tick doesn't literally mean sending data during world update deltas.
It definitely makes sense based on my experience. And the bit at the end about your crosshair rarely moving while you shoot, I’m not so sure. A lot of times you are making microadjustments to move to your opponent’s head as you click, in a 1v1 fight
there's this "flickshot" thing... It's just stupid that the speed of your mouse matters now, esp because csgo had some of the best flickshots/qs mechanics
I was a pro player in a former lifetime (meaning 20 years ago) but I still dabble once in a while. My only way of awp'ing was flicking, and I could usually pwn a DM server easily in GO after a little warmup. Now I cannot hit with awp/scout AT ALL. I hope this get fixed so I don't have to change my playstyle at an age of 41.
It's because you have to actually time your firing perfectly. This video is nonsense. In csgo the animations like bullet holes were client side, but in actuality the hitreg was way less precise. When you flick and shot in csgo if you shot early but ended on target. The shot would connect This is because the server only knows you fired between tick x and tick y, and that you were on target between tick x and tick y. So your shot just hits. In cs2 the shot goes exactly where you were aiming, thanks to subtick if you shoot early you actually miss, because the server can tell exactly when you fired. Most og players got used to how easy csgo aim was and so cs2 feels like it has worse hitreg, when in reality it just exposes their aim was never really that good tl;dr skill issue
well the reality was that while subtick registers your mouse click at the exact moment you clicked and sends it to the server, it has to wait until the next tick arrives (yeah servers still run at 64 tick) and server confirms that the shot was made. because the other person you shot may have shot you before you click. if this confirmation was removed, you would see that the animation happens and player gets killed then the next tick arrives and server denies your click request because other player clicked before you did and all of a sudden you die even when it looks like the other person should i still think my guess was really great, even though *its not correct:* about how the game works, actually tickrate is still 64, but on each packet sent to the server, client attaches a timestamp with the packet. when server has to do a tick, server reads each packet and merges them in order accordingly to the timestamp they have. after this, server sends the data to all player on that tick. i agree on you that this is about subtick system because as you said, the distance from the real shot and the correct shot is random, its probably not random and probably about how far you are to a game tick. my guess is that server merges packets in the wrong order even though i make games i don't work at valve and just making an educated guess*
I'm not an expert either but the dpi I think it relates to the mouse sensor capability to scan the surface and the rate of transmitting these info relates to the polling rate of the mouse.
I grew up on cs 1.6, was lvl 10faceit, Radiant in Valorant, and honest to god, ive never felt like something was so off about a game like i do in cs2. I like to 1tap, it keeps me focused and stops me from going for bad sprays, and ever since CSGO came out, it was possible to do it consistently. Valorant obviously made it even easier with their upgrades to hit reg and servers, so you could legit never miss if you had the aim. But then CS2 came out, and I was so hyped to get back into the faster paced gunfights of CS, now with fixed hit regs and servers, but holy shit, the game is not just buggy, its unplayable. There is no way you can ever get a 1tap, the same shit happens to rifles as it does to the awp, I tested it out on some bot games where id flick onto their heads and shoot 1 bullet, and the bullet literally ended up where my mouse was a millisecond ago. Spraying has never been this bad, even cs 1.6 had more consisten spraying it feels like. Just disappointing how the core of the entire game will never be on the level as Valorants, cause I really do miss CS, its simpler and more fast paced, which is honestly more fun if done well, its just the fact that your shots dont go to where your aiming, or your opponents body isnt actually where its showing to you, making the bullets miss again. Its been an issue for 15years we har CS:GO, very weird how they still havent come up with a real solution whilst their competitors have.
I played a lot CS2 and wondered why my AWP flicks aren't hitting anymore. Ich changed my dpi and aim speed several times but it's still a pain to hit shots right. THEN yesterday I played CS:GO with a friend without access to cs2 and instantly my shots were accurate again. I got really nice frags again and was unhappy about cs2
brooooooo i face same prblmm everdayyy i think at everynight when i go for sleep that i am became noob then i saw ur comment and now i feel that i am wrong bcz i eliminatedd many pro playerss in cs goo cs 2 is very baddd
as a gamedev i have to say, that the mouse dpi doenst affect the tickrate. in games you just get the mouse axis, x and y and then you rotate the player based on that value. (0f-1f)
I saw something about jump-throw binds being inconsistent, but setting up an alias for them first and then binding that alias made it perfectly consistent. Do you think it's possible something like that is coming into play here? (i.e. Create an alias for shooting, then binding mouse1 to that alias)
You might not be far off, I was working a a fps shooter and what I think they did is now the fire angles arent sent when you shoot anymore which means that when you shoot you only send a shoot command and not your view angles. This means whatever last view angle the server has is the view angle that procesees the shot, so when youre moving your crosshair, it may still be sending a new view angle while you are shooting. And that view angle would not be processed by the server causing that issue. Albeit there are definitely some problems with hitboxes too so I dont think its only that, but it could definitely explain the desync between shots.
You should have used the exec cfg method in csgo as well instead of aliasing. Probably doesn't matter but there could be some minor overhead on executing multiple commands via a file instead of with aliases, it's good practice to eliminate unnecessary variables.
it does feel like ur right, on csgo the ssg 08 feels much snappier when moving ur crosshair around, but on cs2 you have to stop right before shooting to actually hit something
When you combine this with the input lag being 2x and the other netcode issues that are also present it does become "literally unplayable" as far as I'm concerned. The entire game feels completely off when you play it and I personally wont bother till these issues are ironed out.
idk why everybody discussing 'new cs2 problems' but i actually gets perfect glock shots VS compare to csgo where i was complete noob on first round as Terr, i still have questions for scout fast stooting but meanwhile awp is just fine for me.
@@BriJeeTVGameDev Yes tap firing is more accurate than ever in CS2 but with that also comes the horrendous downside of spraying being completely screwed up and flick shots also being screwed up. The core of the issue right now is the lag between subtick and server tick. When you fire a shot subtick instantly registers it but then the server, which is 64tick, updates like 15ms later and since the weapon animations are tied to the server tickrate it means the bullets you're shooting happen way earlier (15ms is a lot for these things) then the actual animation of the gun. Search on RU-vid "MrMaxim Is this why shooting feels off in CS2?" and you'll understand, it has a visual demonstration.
I knew the awp flicks were broken as hell and i didn't see many people talking about it. Also i didn't notice it was the same case for every gun. Glad i came across this vid
This is actually a problem with csgo. There the info of your bullet is only registered at the next tick with the firing animation, so they are in sync. Therefore the bullet, firing animation and crosshair are all a bit too far. In cs2 the bullet info is saved immidiately and sent to the server on the next tick at the same time as the animation. This sub-tick info is then applied, so the bullet shows where it should, but the crosshair placement and animation dont have subtick so they travel too far. IMO this is better than your bullet going too far as well
Broooooooooooooooo I just downloaded CS back and my aim SUCKS!!! I remember I was dominating in CSGO and somehow so bad in CS2. I only manage to get average 10+ kills in a match when I always get 20+ before!!! What is wrong???? Counter strafing sucks so bad. My crosshair is small which helps me aim but the bullets doesn't go to where I'm aiming!!! ARGHHH!!!!
It doesn't make the game unplayable, but it does turn the game into whoever is luckier with landing their shots. And idk, I don't think cs is a game of luck
@@samsharma3216 5028 hrs deep. Now im quiting because of this stupid chit. Movement is a big deal now im realising aim is affected too. They killed cs:go
@@altaccount2179 I couldn't agree more, 3k hours been playing from 8 years. When I started playing CS2 it's like I forgot how to play at all, sure some shots connect but many don't. They've made everything worst that can be no wonder 75% of the player base has moved to something better.
The fix you proposed sounds just like what sub-ticks are supposed to be. Also, we should remember that if something is simple, it would already be fixed in the first place (not really in this case since it's a beta). Also the "they did us dirty with the 64 ticks" doesn't make sense since Valve's server (not communities') is 64 ticks in csgo. I'd say that nobody in the community can make an accurate idea of what is the problem since here it's about sending/receiving data (except for the one with a degree in it I guess). It's not like the issue with spraying which is visible (the tracers aren't accurate to the actual bullets). Here it requires a deeper knowledge and we do not have the source code to understand what's happening behind. Remember that it is a beta so if there is an issue, send an email to them explaining the issue with the most precision you can.
Sub-tick is basically interpolation of an action in between two ticks - specifically shooting and WASD-movement (as stated in the valve video) which, unlike mouse movements, don't have thousands of inputs per second. Let's imagine a very minuscule moment in a game where the server tick-rate is on tick#30 and proceeding to tick#31, a span of 15.625 milliseconds. The player, while quickly swiping their mouse, points at direction XYZ and clicks their mouse button 10.000ms after the instant tick#30 was processed. The game records that the player shot their weapon at that point in time, and tells the server "This player shot at direction XYZ 10.000ms after tick#30". The server will then use that information to create the effects of such an action upon the rest of the game upon the arrival of tick#31. However, there are still 5.625ms remaining until tick#31 arrives, and because your mouse is capable of inputting to your game thousands of times per second, it has moved to direction ABC during the 5.625ms remaining until tick#31 begins. So once the final results of what happened during tick#30 are processed and presented by the server, your shot will have arrived at direction XYZ but your mouse will now be facing direction ABC, which will create the exact same discrepancy showcased in this video. What this means is that in CS2, all of your shots will go in the exact direction you shot them at regardless of tick-rate, although that exact direction is so precise to the point where it's happening in-between what is perceivable by the server's tick-rate. This is different from CSGO where your shots will only go where your mouse is pointing at upon the moment a tick arrives, which means your mouse's direction is only recorded at tick#30 and tick#31 and never anywhere in-between. So CS2's sub-tick system is definitely far more precise than anything a higher tick-rate could achieve in the most literal sense, but it also means that what you're being shown on your screen is ever so slightly different from what you're inputting into the server because you now have the freedom to input actions in between what you can perceive. In fact, it's almost like CS2 has removed the tiny input lag that is present between you inputting an action and the server's tick-rate trying to follow up with your input, but everyone's used to being dependent on the tick-rate which makes the new tick-rate-independent system feel awkward as a result.
Just to add on about the proposed solution at the end of the video, making the mouse position be sent to the point of fire will probably make things feel even worse because that's essentially preventing your mouse from moving for the remainder of that tick, which means you won't be allowed to move your mouse for upwards of ~15ms in the worst case scenario and ~8ms on average. This probably won't have too much of an impact on tap-firing, but it's gonna be super noticeable during spray-downs if your mouse is being frozen in place after every shot.
The more I've been playing CS2, the more I feel like subtick is a solution to a problem we didn't actually have. If they spent whatever $ it cost to develop this 'tech' on 128 tick servers everyone would be having a much better time lol
I have an awping style thats incredibly flicky and aggressive, similar to broky, all today and yesterday ive noticed my shots with my awp and ak just missing or seemingly going through heads almost 30% of the time. it really feels like if youre not just preaiming your opponent everytime youre just taking a dice roll on whether youll kill them or not.
Here is my take sense you requested them in the video (this is my interpretation that I think is more accurate). I'm sure some other comments have also brought this up. I don't think the server cares about the polling rate of your mouse, it just gets the players position and rotation every so often (probably once per tick) and interpolates that information for others to see. As for why the bullets don't line up, on the old tick rate system, all events that happened during a tick get pushed back to the end of the tick and happen at the same time. That is why the bullet lines up with where your crosshair stops. You may have fired your gun a few milliseconds before the tick ended, but you stopped rotating and fired at the end of the tick. On the new subtick system, a fixed 64 tickrate still exists, but events that happen are essentially timestamped with a delta time between ticks. At the end of the tick, the server looks at that delta time and does the math to find out where you were looking at the exact time you fired. Your cursor is in a new position, but the bullet is going to the spot you were looking at that exact moment a few milliseconds prior. Technically the new subtick is more accurate, but there is a perceivable difference when slowed down that you observed in this video.
The mouse polling rate is just providing insight into exactly when the event occurred. They still get processed at tick time. Therefore no, they don’t need to 1000 tick to handle 1000hz polling rate. 1000hz just gives more potential resolution (in terms of time) in which you can get an accurate time for the event start.
