-
Notifications
You must be signed in to change notification settings - Fork 598
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
Weapons sometimes simulate double fires #1691
Comments
This even happens with a fresh copy of the source code. Is this a bug in this version of the source code? |
Sounds to me like the event is firing twice. Does your code check if g_runfuncs is 1 before running client side simulation? If not, it could be triggering events during a second run of the same frame. You could try using event_api_s::EV_KillEvents to remove any pending events for the weapon from the event queue. If the event is already in the queue multiple times when the first one is executed, that will remove them and stop the double fire. You'll still have to figure out where the event is coming from, but you'll know that that's what's happening. |
I had this happenning in the latest Steam version, no idea what it's about thought. |
I have already reported that issue (see #1621), I think it's related to "client prediction" because if you disable "CLIENT_WEAPONS" in both projects; you won't see that issue. |
@kisak-valve Duplicate of #1621. |
Thanks @agrastiOs, closing as a duplicate. |
This is an annoying bug i keep experiencing. With most automatic weapons, I experience a double-fire event. It fires a bullet twice and ejects a shell as if i was shooting a normal bullet. Except it doesn't take it out of the magazine? I have searched around and no one has encountered this bug. It's really annoying as it is not coming from the weapon cpp itself. However i did create a new fire event for the Glock to have a rapid secondary fire and that is working correctly. How ever it uses the exact same code that the primary slower rate of fire uses.
Has anyone got an idea on what may be causing this? I recompile cl and normal dlls every time i test. debug and dev mode are activated also.
The text was updated successfully, but these errors were encountered: