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
tf_viewmodel entities don't render correctly when the server changes their model to anything other than the one the client expects for a given class
#3545
Closed
triggerhurt opened this issue
Apr 26, 2021
· 1 comment
I tried using the in-game bug reporter, not sure if those actually go through or not so I'm submitting it here as well. Apologies if this is redundant.
If the tf_viewmodel's model is changed to literally any other model (regardless of validity), three odd behaviors occur:
The original viewmodel arms and animations will display for a single frame at the start (end?) of each animation cycle
Animations stop blending whatsoever when the action related to that animation ends, causing the motion to snap instead of blending like it does when no change occurs (this is best demonstrated with melee weapons, which rely on that smooth transition to look correct)
Despite the change taking place server-side, the sequence order is not updated (correctly?), because the client will display animations with matching numbers on the new model, even if the activities are different.
I believe this may be related to prediction because the first two issues don't occur when spectating other players in first person; to my knowledge, the client does not (and cannot) predict the viewmodel of other players, only their own.
Many sendprops that should be inherited from CBaseAnimating appear to be missing, at least server-side. Possibly related?
The text was updated successfully, but these errors were encountered:
Recent tf2 update added a solution to this problem via m_nCustomViewmodelModelIndex; technically the issue of changing the model index directly still exists, but this new sendprop allows you to avoid doing that in the first place, therein solving the problem.
I tried using the in-game bug reporter, not sure if those actually go through or not so I'm submitting it here as well. Apologies if this is redundant.
If the tf_viewmodel's model is changed to literally any other model (regardless of validity), three odd behaviors occur:
I believe this may be related to prediction because the first two issues don't occur when spectating other players in first person; to my knowledge, the client does not (and cannot) predict the viewmodel of other players, only their own.
Many sendprops that should be inherited from CBaseAnimating appear to be missing, at least server-side. Possibly related?
The text was updated successfully, but these errors were encountered: