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

trigger_push bug #1

Closed
sneak-it opened this issue Oct 6, 2018 · 1 comment
Closed

trigger_push bug #1

sneak-it opened this issue Oct 6, 2018 · 1 comment

Comments

@sneak-it
Copy link

sneak-it commented Oct 6, 2018

Hey rio! Seems as though an odd bug was discovered with rngfix:

https://www.youtube.com/watch?v=M6bftPeqjGA

Map is surf_proximity_final on CS:GO, apparently the same issue occurs on the same map in CS:S. As you can see, disabling rngfix takes care of the issue. I'm assuming it has something to do with upwards slope logic overriding the push speed.

@jason-e
Copy link
Owner

jason-e commented Oct 9, 2018

I've determined this is caused by an interaction between rngfix and some pushfix implementations. The offending code in pushfix is:

if(vecAbsDir[2] > 0.0 && GetEntityFlags(other) & FL_ONGROUND)
{
	SetEntPropEnt(other, Prop_Data, "m_hGroundEntity", -1);
	origin[2] += 1.0;
}

To anyone with a pushfix implementation that has that behavior, I would recommend removing that block both to fix this interaction, and because that behavior appears to actually be detrimental to the operation of pushfix itself. SlidyBat has updated his implementation shared here to account for this.

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

2 participants