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 Interact Use script was emitting two unuse events because the
Interact Use script calls StopUsing on the Interactable Object and
the Interactable Object script calls ForceResetUsing on the
Interact Use script, which would then in turn emit the unuse event
before the original StopUsing routine had finished. This would
result in two unuse events being emitted.
The fix for this is to add another check into the Interactable Object
StopUsing method that can be used to bypass the ForceResetUsing call
as it's not needed to reset the Interact Use object if the StopUsing
on the Interact Use has been called as it will already reset the state
anyway.
/// The StopUsing method is called automatically when the object has stopped being used. It is also a virtual method to allow for overriding in inherited classes.
422
422
/// </summary>
423
423
/// <param name="previousUsingObject">The object that was previously using this object.</param>
Copy file name to clipboardExpand all lines: DOCUMENTATION.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3456,12 +3456,13 @@ The Ungrabbed method is called automatically when the object has stopped being g
3456
3456
3457
3457
The StartUsing method is called automatically when the object is used initially. It is also a virtual method to allow for overriding in inherited classes.
0 commit comments