Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crouch Jumping causes movement hiccup until DuckSpeed ( time ) is over. #1512

Closed
Acecool opened this issue Sep 24, 2014 · 3 comments
Closed
Assignees

Comments

@Acecool
Copy link

Acecool commented Sep 24, 2014

A friend of mine asked me a question a while back regarding his BHop server. He told me that when crouch jumping onto some object higher than ground-level causes the player to stop moving momentarily. I was having trouble reproducing it.

He asked me again a few hours ago if I had made any progress on it, so I came up with a theory... My assumption was that when moving into crouch, all works fine, but when jumping onto an object that is higher up, the player "lands" on the higher-up object but they aren't fully "touching" the ground / new object until the duck-time is up.

He tested my theory by setting DuckSpeed to 0 and it fixed the issue. The player no longer gets stuck / stopped from moving when crouch-jumping. I'm reporting this because it seems strange that DuckSpeed would cause this issue.

@MagentaIris
Copy link

I think its because the players hull doesn't gradually change between the speed, But is instantly set, As the player un-ducks at certain places (which is very rare in my case) the setups allow you to un-duck, So once the timer is over the hull is changed, thus sticking the player in the object by about 1-2 hammer units.

I've managed to reproduce this kinda problem tons of times on S-Ents and things like that with relative ease.

@Acecool
Copy link
Author

Acecool commented Oct 6, 2014

Yeah; this may stem from that fix Garry had to implement because crouch-jumping when in a crouched-only spot caused you to move through the map. I wonder if the fix involved forcing velocity to 0 and setting pos.... If so, that needs to be changed.

@willox willox self-assigned this Apr 7, 2016
@willox
Copy link
Contributor

willox commented Apr 15, 2016

Happens once curtime is a big number

@willox willox closed this as completed May 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants