explorer 519d56c138 predicted chainsaw state 2/2
unfortunately there's no reliable way due to *::Deploy not being called in certain scenarios but that should serve as good foundation for later improvement.

minor precision loss possibly due to addition being replaced with multiplication (ie. cycle + rate * interval -> ticks * rate * interval)
2025-01-02 21:31:37 +03:00
2024-11-09 15:31:28 +03:00
2024-11-09 15:31:28 +03:00
2024-11-09 15:31:28 +03:00
2025-01-02 21:31:37 +03:00
2024-11-09 15:31:28 +03:00
2024-10-06 22:45:39 +03:00
2024-12-27 19:06:35 +03:00
2025-01-02 21:31:37 +03:00
2024-10-06 22:45:39 +03:00
2024-11-09 15:31:28 +03:00
2024-11-09 17:50:59 +03:00
2024-12-22 14:35:23 +03:00
2024-11-05 18:11:13 +03:00
2024-10-06 22:45:39 +03:00

to achieve least interpolation time: cl_updaterate 100;cl_interp_ratio 0;cl_interp 0
to queue extra commands: bind key +zoom

code: https://github.com/qwertyuiop3/Storm

credits:
me (for something)
noop (for being helpful, specifically on debugging and reversing)
d3x (for telling me that i don't have to bruteforce prediction frame)
polak (for strafe deltas)
ucuser0 (for his post regarding backup commands)
kamay (for crossproducts of movement)
deniz (for being friend)

songs:
david bowie - art decade
scratch acid - cannibal

edited by "obviously who"
Languages
C++ 100%