[BHaType]

Originally Posted by blueblur Hi, I would like to request a feature for this extension: Could we resolve the collision between the wandering witch and infected? Running infected who collide with witch will push witch with an extra speed, which looks like the witch is "shifting away".

All common infected and witches collisions are handled by "NextBotGroundLocomotion::ResolveZombieCollis ions" so just disabling this feature for witches would "fix" the issue. However, the actual problem lies here. The locomotion system sets momentum based on how much the position has changed since the last update and adds velocity accordingly. The gained velocity should decay over time due to friction but this doesn't happen because for some reason forward friction is disabled by default (nb_friction_forward) and even if you enable it, it only works when your actual velocity is in the opposite direction of the desired velocity.

Originally Posted by blueblur But I don't think it is a nice way. If we start from the collision itself, what would be the better way to neutralize the collision?

I think the best way to try to fix it is to enable forward friction and patch the check but this would probably be time consuming and I don't know why it was implemented this way.
Using SetAbsVelocity is probably the most efficient approach, imo.

[blueblur]

Originally Posted by BHaType However, the actual problem lies here.

Yeah I see.

Originally Posted by BHaType I think the best way to try to fix it is to enable forward friction and patch the check but this would probably be time consuming and I don't know why it was implemented this way.

Agree that rebuild the whole function is indeed time consuming.

Originally Posted by BHaType The gained velocity should decay over time due to friction but this doesn't happen because for some reason forward friction is disabled by default (nb_friction_forward) and even if you enable it, it only works when your actual velocity is in the opposite direction of the desired velocity.

It seems that it only operates if the actual velocity is in an angle that is greater than 90 degrees between the move vector. So probably it is fine to not to patch it? (Not tested, if the actual behavior is differed than the desired behavior then it is indeed needed to be patched.)

Originally Posted by BHaType Using SetAbsVelocity is probably the most efficient approach, imo.

I had a thought on this, truth that this is the most efficient way, but eventually to make it looks more natural on the collision velocity, we still have to implement a better algorithm on the forward friction and the forward speed check. But yeah that is something huge work to replenish a tiny issue, resulting that I am reluctant to do so too.

[zuaLdakid05]

Random crashes sometimes happen when i loaded my server with this, i don't know why. Please update

[BHaType]

Originally Posted by zuaLdakid05 Random crashes sometimes happen when i loaded my server with this, i don't know why. Please update

Windows or Linux?
if windows then test the attached version

[zuaLdakid05]

Originally Posted by BHaType Windows or Linux? if windows then test the attached version

Yes, i am using it on windows.
I've tested the version on your post and turns out great, no crash at all. Thank you so much!

[MoRanYue]

Originally Posted by BHaType Windows or Linux? if windows then test the attached version

is it a fix of the latest version or an old version achive?

[BHaType]

Originally Posted by MoRanYue is it a fix of the latest version or an old version achive?

It's the latest version but compiled without the optimization flag

[MoRanYue]

Originally Posted by BHaType It's the latest version but compiled without the optimization flag

thats so good, though the reason indicates those crashes problem still remains unknown