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
I've noticed that running continuousCollide with the same pre-allocated ContinuousCollisionResult struct will have result.is_collide stuck on true after it is used with colliding inputs. Without diving too much into the details of the "real" implementation, it seems that at least the code for the naive solution doesn't make any effort to clear the results struct (i.e. set is_collide = false). Is this intended behaviour?
The text was updated successfully, but these errors were encountered:
I've noticed that running
continuousCollide
with the same pre-allocatedContinuousCollisionResult
struct will haveresult.is_collide
stuck ontrue
after it is used with colliding inputs. Without diving too much into the details of the "real" implementation, it seems that at least the code for the naive solution doesn't make any effort to clear the results struct (i.e. setis_collide = false
). Is this intended behaviour?The text was updated successfully, but these errors were encountered: