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
In some places, parry uses the FeatureId enum, but TrackedContent uses a plain u32 for its feature IDs. This is also easily confused with the subshape u32s in ContactManifold, which identify logical shapes but not individual geometric features of a single shape (i.e. not necessarily a specific face, edge, or vertex). It's also unclear whether feature IDs in contact manifolds are scoped to shapes or subshapes, whereas FeatureIds necessarily must be shape-scoped since they're e.g. returned by PointQuery.
In some places, parry uses the
FeatureId
enum, butTrackedContent
uses a plainu32
for its feature IDs. This is also easily confused with the subshapeu32
s inContactManifold
, which identify logical shapes but not individual geometric features of a single shape (i.e. not necessarily a specific face, edge, or vertex). It's also unclear whether feature IDs in contact manifolds are scoped to shapes or subshapes, whereasFeatureId
s necessarily must be shape-scoped since they're e.g. returned byPointQuery
.See also Discord discussion. Opening an issue for tracking purposes.
The text was updated successfully, but these errors were encountered: