Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
the weird issue regarding netcode at the moment wouldn't be an issue at lan when everyone effectively has a ping of 0.
I’m running a i9 9900k 4070 32gb ddr4 ram on a sea gate barracuda hdd with 5140x1440 on 250 fps top avg 200 with max settings except msaa
I’m on a driver from a few version ago gpu
this one is more accurate
https://www.youtube.com/live/iUz6OF6mg2k?si=r2v6tvA8UiXJCiSL
in CS2 since subtick now processes EVERY input it also includes your own inconsistency.
so it comes down to do you train out your own inconsistency with inputs
or
you can use alias commands in cs2 to make the game process inputs only during a tick like in csgo but valve may fix this as its technically a bug,
basically since you can now die between ticks according to the server.
you can now move away from a peeker but the server waits until the next tick to tell you that you already died leading to the visual of death behing a wall but in reality according the server you died a few miliseconds before hand.
or case 2 the server decided to rollback and kill you to make the game somewhat more fair for a higher latency player.