You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The bullet hit sounds don't work in HL25 multiplayer regardless if the hitbox or bounding box was hit, and the current SDK code doesn't reflect whatever changes cause this issue. Please correct this and publish any SDK changes needed to make it work.
This is related to the HL25 patch note:
Improved client-side prediction to reduce "ghost shots". Like Counter-Strike, consider hitboxes and not just bounding boxes for hits on the client.
The following behavior is what happens when shooting either at and/or near a player with videos below:
HL25 Multiplayer: No flesh hit sounds at all.
HL25 Singleplayer: Correctly plays flesh hit sounds only when the NPC will take damage.
steam_legacy Multiplayer: Plays flesh hit sounds on hits and missed shots.
steam_legacy Singleplayer: No flesh hit sounds at all.
HLSDK Multiplayer on HL25: The same behavior as steam_legacy, regardless if the following line
uses PM_STUDIO_BOX or PM_NORMAL (likely involved in the change in some way). The video demonstration for the SDK behavior uses this code in place of the above line:
The bullet hit sounds don't work in HL25 multiplayer regardless if the hitbox or bounding box was hit, and the current SDK code doesn't reflect whatever changes cause this issue. Please correct this and publish any SDK changes needed to make it work.
This is related to the HL25 patch note:
The following behavior is what happens when shooting either at and/or near a player with videos below:
halflife/cl_dll/ev_hldm.cpp
Line 403 in c7240b9
PM_STUDIO_BOX
orPM_NORMAL
(likely involved in the change in some way). The video demonstration for the SDK behavior uses this code in place of the above line:The issue occurs regardless if it's a listen server or HLDS.
HL25-MP.mp4
HL25-SP.mp4
steamlegacy-MP.mp4
steamlegacy-SP.mp4
HLSDK-hl25-MP.mp4
The text was updated successfully, but these errors were encountered: