CS1.6 related changes for TAS Optimizer

[khanghugo]

Hmmm, it doesn't look up to standard from my standard.

[khanghugo]

bxt-rs/bxt-strafe/src/steps.rs

Lines 730 to 732 in 576e012

	// Duck()
	if state.player.ducking || (parameters.ducktap_slow && (state.player.in_duck_animation || input.duck)) {
	state.wish_speed *= 0.333;

state.player.in_duck_animation condition does not work (as in doing nothing) for CS1.6 duck tap slow but I just want to keep it on parity with BunnymodXT. More or less, it is just a condition that does nothing but only input.duck is responsible for that. I am unaware if it does cause any problems.

There is an issue with lgagst being weird every 1/1000 bhop block where it refuses to jump with dbg/dbc and keeps on walking in duck unless lgagst is toggled off. It happens with prediction but second game simulator corrects it just fine. I am not sure if this could be the cause. When I encounter that occurrence, I might just try out and see and I hope that is isn't. I guess this is unrelated. And fixed.

[YaLTeR]

Looks good, but needs a few improvements.

[khanghugo]

Thanks, this seems reasonable. Let me do that.

[khanghugo]

This has all the changes except the unresolved one, not sure how it would proceed 👍

[YaLTeR]

I see BXT uses GetClientMaxspeed() for this. I'm not sure using pmove is equivalent, isn't it one frame off? Since pmove is only filled/updated later in the frame.

[khanghugo]

I am not aware of it being one frame off. It does sync well on my end. If it is one frame off then it would be one frame off the very first frame of the TAS as weapon speed would be the same the whole run.

[khanghugo]

Also, it is in the bind, so I just use whatever is there.

[YaLTeR]

Thanks!