C++ Certified Professional Programmer
-
Автор темы
- #1
So basically it's not really "Resolver Ways" as the title says. I've been thinking a lot. Shouldnt there be a lot of new resolver logics etc. like lemme state some random shit, I have no clue if you can you use this.
(based on missedshots)
feetyaw = eyeangles.yaw + maxdesync; // 60 also works
feetyaw = eyeangles.yaw - maxdesync; // 60 also works
If I'm correct you'll miss 90% of times.
Then ofc you can use "setupvelocity" to calculate the desync side (not really a good way of resolving)
AnimationLayers can be easily broken.
What more ways is there to use?
(based on missedshots)
feetyaw = eyeangles.yaw + maxdesync; // 60 also works
feetyaw = eyeangles.yaw - maxdesync; // 60 also works
If I'm correct you'll miss 90% of times.
Then ofc you can use "setupvelocity" to calculate the desync side (not really a good way of resolving)
AnimationLayers can be easily broken.
What more ways is there to use?