/// <summary>Create a C++ proxy callback which will forward contact events to `Callback`. The returned pointer must be freed by calling `destroy_contact_callback` when done using.</summary>
/// <summary>Override the default filter shader in the scene with a custom function. If call_default_filter_shader_first is set to true, this will first call the built-in PhysX filter (that matches Physx 2.8 behavior) before your callback.</summary>
/// <summary>Allocates size bytes of memory, which must be 16-byte aligned. This method should never return NULL. If you run out of memory, then you should terminate the app or take some other appropriate action. Threading: This function should be thread safe as it can be called in the context of the user thread and physics processing thread(s). The allocated block of memory.</summary>
/// <summary>Frees memory previously allocated by allocate(). Threading: This function should be thread safe as it can be called in the context of the user thread and physics processing thread(s).</summary>
/// <summary>Destroys the instance it is called on. The operation will fail, if there are still modules referencing the foundation object. Release all dependent modules prior to calling this method.</summary>
/// <summary>Set if allocation names are being passed to allocator callback. Enabled by default in debug and checked build, disabled by default in profile and release build.</summary>
/// <summary>Creates an instance of the foundation class The foundation class is needed to initialize higher level SDKs. There may be only one instance per process. Calling this method after an instance has been created already will result in an error message and NULL will be returned. Foundation instance on success, NULL if operation failed</summary>
/// <summary>Copies the bytes of one memory block to another. The memory blocks must not overlap. Use [`PxMemMove`] if memory blocks overlap. Pointer to destination memory block</summary>
/// <summary>Copies the bytes of one memory block to another. The memory blocks can overlap. Use [`PxMemCopy`] if memory blocks do not overlap. Pointer to destination memory block</summary>
/// <summary>Mark a specified amount of memory with 0xcd pattern. This is used to check that the meta data definition for serialized classes is complete in checked builds.</summary>
/// <summary>normalizes the vector in place. Does nothing if vector magnitude is under PX_NORMALIZATION_EPSILON. Returns vector magnitude if >= PX_NORMALIZATION_EPSILON and 0.0f otherwise.</summary>
/// <summary>Default constructor, not performing any initialization for performance reason. Use empty() function below to construct empty bounds.</summary>
/// <summary>gets the transformed bounds of the passed AABB (resulting in a bigger AABB). Calling this method for empty bounds leads to undefined behavior. Use [`transformSafe`]() instead.</summary>
/// <summary>gets the transformed bounds of the passed AABB (resulting in a bigger AABB). Calling this method for empty bounds leads to undefined behavior. Use [`transformSafe`]() instead.</summary>
/// <summary>fattens the AABB in all 3 dimensions by the given distance. Calling this method for empty bounds leads to undefined behavior. Use [`fattenSafe`]() instead.</summary>
/// <summary>Finds the closest point in the box to the point p. If p is contained, this will be p, otherwise it will be the closest point on the surface of the box.</summary>
/// <summary>Allocates size bytes of memory, which must be 16-byte aligned. This method should never return NULL. If you run out of memory, then you should terminate the app or take some other appropriate action. Threading: This function should be thread safe as it can be called in the context of the user thread and physics processing thread(s). The allocated block of memory.</summary>
/// <summary>Frees memory previously allocated by allocate(). Threading: This function should be thread safe as it can be called in the context of the user thread and physics processing thread(s).</summary>
/// <summary>write to the stream. The number of bytes written may be less than the number sent. the number of bytes written to the stream by this call.</summary>
/// <summary>finds the shortest rotation between two vectors. a rotation about an axis normal to the two vectors which takes one to the other via the shortest path</summary>
/// <summary>creates a transform from the endpoints of a segment, suitable for an actor transform for a PxCapsuleGeometry A PxTransform which will transform the vector (1,0,0) to the capsule axis shrunk by the halfHeight</summary>
/// <summary>creates a transform from a plane equation, suitable for an actor transform for a PxPlaneGeometry a PxTransform which will transform the plane PxPlane(1,0,0,0) to the specified plane</summary>
/// <summary>Spherical linear interpolation of two quaternions. Returns left when t=0, right when t=1 and a linear interpolation of left and right when 0 < t < 1. Returns angle between -PI and PI in radians</summary>
/// <summary>Compute the closest point on an 2d ellipse to a given 2d point. Returns the 2d position on the surface of the ellipse that is closest to point.</summary>
/// <summary>Compute from an input quaternion q a pair of quaternions (swing, twist) such that q = swing * twist with the caveats that swing.x = twist.y = twist.z = 0.</summary>
/// <summary>Compute three normalized vectors (dir, right and up) that are parallel to (dir) and perpendicular to (right, up) the normalized direction vector (p1 - p0)/||p1 - p0||.</summary>
/// <summary>Wait on the object for at most the given number of ms. Returns true if the object is signaled. Sync::waitForever will block forever or until the object is signaled.</summary>
/// <summary>Registers a reference value corresponding to a PxBase object. This method is assumed to be called in the implementation of PxSerializer::registerReferences for serialized references that need to be resolved on deserialization. A reference needs to be associated with exactly one PxBase object in either the collection or the external references collection. Different kinds of references are supported and need to be specified. In the most common case (PX_SERIAL_REF_KIND_PXBASE) the PxBase object matches the reference value (which is the pointer to the PxBase object). Integer references maybe registered as well (used for internal material indices with PX_SERIAL_REF_KIND_MATERIAL_IDX). Other kinds could be added with the restriction that for pointer types the kind value needs to be marked with the PX_SERIAL_REF_KIND_PTR_TYPE_BIT.</summary>
/// <summary>Serializes object data and object extra data. This function is assumed to be called within the implementation of PxSerializer::exportData and PxSerializer::exportExtraData.</summary>
/// <summary>Aligns the serialized data. This function is assumed to be called within the implementation of PxSerializer::exportData and PxSerializer::exportExtraData.</summary>
/// <summary>Helper function to write a name to the extraData if serialization is configured to save names. This function is assumed to be called within the implementation of PxSerializer::exportExtraData.</summary>
/// <summary>Retrieves a pointer to a deserialized PxBase object given a corresponding deserialized reference value This method is assumed to be called in the implementation of PxSerializer::createObject in order to update reference values on deserialization. To update a PxBase reference the corresponding deserialized pointer value needs to be provided in order to retrieve the location of the corresponding deserialized PxBase object. (PxDeserializationContext::translatePxBase simplifies this common case). For other kinds of references the reverence values need to be updated by deduction given the corresponding PxBase instance. PxBase object associated with the reference value</summary>
/// <summary>Helper function to read a name from the extra data during deserialization. This function is assumed to be called within the implementation of PxSerializer::createObject.</summary>
/// <summary>Function to align the extra data stream to a power of 2 alignment This function is assumed to be called within the implementation of PxSerializer::createObject.</summary>
/// <summary>Unregister a serializer for a concrete type, and retrieves the corresponding serializer object. Unregistered serializer corresponding to type, NULL for types for which no serializer has been registered.</summary>
/// <summary>Unregister a RepX serializer for a concrete type, and retrieves the corresponding serializer object. Unregistered PxRepxSerializer corresponding to type, NULL for types for which no RepX serializer has been registered.</summary>
/// <summary>Releases PxSerializationRegistry instance. This unregisters all PhysX and PhysXExtension serializers. Make sure to unregister all custom type serializers before releasing the PxSerializationRegistry.</summary>
/// <summary>Adds a PxBase object to the collection. Adds a PxBase object to the collection. Optionally a PxSerialObjectId can be provided in order to resolve dependencies between collections. A PxSerialObjectId value of PX_SERIAL_OBJECT_ID_INVALID means the object remains without id. Objects can be added regardless of other objects they require. If the object is already in the collection, the ID will be set if it was PX_SERIAL_OBJECT_ID_INVALID previously, otherwise the operation fails.</summary>
/// <summary>Adds an id to a member PxBase object. If the object is already associated with an id within the collection, the id is replaced. May only be called for objects that are members of the collection. The id needs to be unique within the collection.</summary>
/// <summary>Adds all PxBase objects and their ids of collection to this collection. PxBase objects already in this collection are ignored. Object ids need to be conflict free, i.e. the same object may not have two different ids within the two collections.</summary>
/// <summary>Removes all PxBase objects of collection from this collection. PxBase objects not present in this collection are ignored. Ids of objects which are removed are also removed.</summary>
/// <summary>Copies member PxBase pointers to a user specified buffer. number of members PxBase objects that have been written to the userBuffer</summary>
/// <summary>Looks for a PxBase object given a PxSerialObjectId value. If there is no PxBase object in the collection with the given id, NULL is returned. PxBase object with the given id value or NULL</summary>
/// <summary>Copies member PxSerialObjectId values to a user specified buffer. number of members PxSerialObjectId values that have been written to the userBuffer</summary>
/// <summary>Gets the PxSerialObjectId name of a PxBase object within the collection. The PxBase object needs to be a member of the collection. PxSerialObjectId name of the object or PX_SERIAL_OBJECT_ID_INVALID if the object is unnamed</summary>
/// <summary>Deletes a collection object. This function only deletes the collection object, i.e. the container class. It doesn't delete objects that are part of the collection.</summary>
/// <summary>Creates a collection object. Objects can only be serialized or deserialized through a collection. For serialization, users must add objects to the collection and serialize the collection as a whole. For deserialization, the system gives back a collection of deserialized objects to users. The new collection object.</summary>
/// <summary>Whether the object is subordinate. A class is subordinate, if it can only be instantiated in the context of another class. Whether the class is subordinate</summary>
/// <summary>Returns the reference count of the object. At creation, the reference count of the object is 1. Every other object referencing this object increments the count by 1. When the reference count reaches 0, and only then, the object gets destroyed automatically. the current reference count.</summary>
/// <summary>Acquires a counted reference to this object. This method increases the reference count of the object by 1. Decrement the reference count by calling release()</summary>
/// <summary>Adds required objects to the collection. This method does not add the required objects recursively, e.g. objects required by required objects.</summary>
/// <summary>Whether the object is subordinate. A class is subordinate, if it can only be instantiated in the context of another class. Whether the class is subordinate</summary>
/// <summary>Create object at a given address, resolve references and import extra data. Created PxBase pointer (needs to be identical to address before increment).</summary>
/// <summary>Called by the TaskManager when a task is to be queued for execution. Upon receiving a task, the dispatcher should schedule the task to run. After the task has been run, it should call the release() method and discard its pointer.</summary>
/// <summary>Returns the number of available worker threads for this dispatcher. The SDK will use this count to control how many tasks are submitted. By matching the number of tasks with the number of execution units task overhead can be reduced.</summary>
/// <summary>The user-implemented run method where the task's work should be performed run() methods must be thread safe, stack friendly (no alloca, etc), and must never block.</summary>
/// <summary>Return a user-provided task name for profiling purposes. It does not have to be unique, but unique names are helpful. The name of this task</summary>
/// <summary>Implemented by derived implementation classes A task may assume in its release() method that the task system no longer holds references to it - so it may safely run its destructor, recycle itself, etc. provided no additional user references to the task exist</summary>
/// <summary>Initialize this task and specify the task that will have its ref count decremented on completion. Submission is deferred until the task's mRefCount is decremented to zero. Note that we only use the PxTaskManager to query the appropriate dispatcher.</summary>
/// <summary>Initialize this task and specify the task that will have its ref count decremented on completion. This overload of setContinuation() queries the PxTaskManager from the continuation task, which cannot be NULL.</summary>
/// <summary>Returns true if the geometry is valid. True if the current settings are valid A valid box has a positive extent in each direction (halfExtents.x > 0, halfExtents.y > 0, halfExtents.z > 0). It is illegal to call PxRigidActor::createShape and PxPhysics::createShape with a box that has zero extent in any direction.</summary>
/// <summary>Frustum culling test against a BVH. This is similar in spirit to an overlap query using a convex object around the frustum. However this specialized query has better performance, and can support more than the 6 planes of a frustum, which can be useful in portal-based engines. On the other hand this test only returns a conservative number of bounds, i.e. some of the returned bounds may actually be outside the frustum volume, close to it but not touching it. This is usually an ok performance trade-off when the function is used for view-frustum culling. false if query has been aborted</summary>
/// <summary>Returns the number of bounds in the BVH. You can use [`getBounds`]() to retrieve the bounds. These are the user-defined bounds passed to the BVH builder, not the internal bounds around each BVH node. Number of bounds in the BVH.</summary>
/// <summary>Retrieve the read-only bounds in the BVH. These are the user-defined bounds passed to the BVH builder, not the internal bounds around each BVH node.</summary>
/// <summary>Retrieve the bounds in the BVH. These bounds can be modified. Call refit() after modifications are done. These are the user-defined bounds passed to the BVH builder, not the internal bounds around each BVH node.</summary>
/// <summary>Refit the BVH. This function \"refits\" the tree, i.e. takes the new (leaf) bounding boxes into account and recomputes all the BVH bounds accordingly. This is an O(n) operation with n = number of bounds in the BVH. This works best with minor bounds modifications, i.e. when the bounds remain close to their initial values. With large modifications the tree quality degrades more and more, and subsequent query performance suffers. It might be a better strategy to create a brand new BVH if bounds change drastically. This function refits the whole tree after an arbitrary number of bounds have potentially been modified by users (via getBoundsForModification()). If you only have a small number of bounds to update, it might be more efficient to use setBounds() and partialRefit() instead.</summary>
/// <summary>Update single bounds. This is an alternative to getBoundsForModification() / refit(). If you only have a small set of bounds to update, it can be inefficient to call the refit() function, because it refits the whole BVH. Instead, one can update individual bounds with this updateBounds() function. It sets the new bounds and marks the corresponding BVH nodes for partial refit. Once all the individual bounds have been updated, call partialRefit() to only refit the subset of marked nodes. true if success</summary>
/// <summary>Refits subset of marked nodes. This is an alternative to the refit() function, to be called after updateBounds() calls. See updateBounds() for details.</summary>
/// <summary>Generic BVH traversal function. This can be used to implement custom BVH traversal functions if provided ones are not enough. In particular this can be used to visualize the tree's bounds. false if query has been aborted</summary>
/// <summary>Returns true if the geometry is valid. True if the current settings are valid. A valid capsule has radius > 0, halfHeight >= 0. It is illegal to call PxRigidActor::createShape and PxPhysics::createShape with a capsule that has zero radius or height.</summary>
/// <summary>Returns the mass properties of the mesh assuming unit density. The following relationship holds between mass and volume: mass = volume * density The mass of a unit density mesh is equal to its volume, so this function returns the volume of the mesh. Similarly, to obtain the localInertia of an identically shaped object with a uniform density of d, simply multiply the localInertia of the unit density mesh by d.</summary>
/// <summary>This method decides whether a convex mesh is gpu compatible. If the total number of vertices are more than 64 or any number of vertices in a polygon is more than 32, or convex hull data was not cooked with GPU data enabled during cooking or was loaded from a serialized collection, the convex hull is incompatible with GPU collision detection. Otherwise it is compatible. True if the convex hull is gpu compatible</summary>
/// <summary>Returns true if combination of negative scale components will cause the triangle normal to flip. The SDK will flip the normals internally.</summary>
/// <summary>Returns true if the geometry is valid. True if the current settings are valid for shape creation. A valid convex mesh has a positive scale value in each direction (scale.x > 0, scale.y > 0, scale.z > 0). It is illegal to call PxRigidActor::createShape and PxPhysics::createShape with a convex that has zero extent in any direction.</summary>
/// <summary>Returns true if the geometry is valid. True if the current settings are valid A valid sphere has radius > 0. It is illegal to call PxRigidActor::createShape and PxPhysics::createShape with a sphere that has zero radius.</summary>
/// <summary>Returns true if the geometry is valid. True if the current settings are valid for shape creation. A valid triangle mesh has a positive scale value in each direction (scale.scale.x > 0, scale.scale.y > 0, scale.scale.z > 0). It is illegal to call PxRigidActor::createShape and PxPhysics::createShape with a triangle mesh that has zero extents in any direction.</summary>
/// <summary>Returns true if the geometry is valid. True if the current settings are valid A valid height field has a positive scale value in each direction (heightScale > 0, rowScale > 0, columnScale > 0). It is illegal to call PxRigidActor::createShape and PxPhysics::createShape with a height field that has zero extents in any direction.</summary>
/// <summary>Returns true if the geometry is valid. True if the current settings are valid for shape creation. A valid tetrahedron mesh has a positive scale value in each direction (scale.scale.x > 0, scale.scale.y > 0, scale.scale.z > 0). It is illegal to call PxRigidActor::createShape and PxPhysics::createShape with a tetrahedron mesh that has zero extents in any direction.</summary>
/// <summary>For raycast hits: true for shapes overlapping with raycast origin. For sweep hits: true for shapes overlapping at zero sweep distance.</summary>
/// <summary>Return custom type. The type purpose is for user to differentiate custom geometries. Not used by PhysX. Unique ID of a custom geometry type. User should use DECLARE_CUSTOM_GEOMETRY_TYPE and IMPLEMENT_CUSTOM_GEOMETRY_TYPE intead of overwriting this function.</summary>
/// <summary>Raycast test against a geometry object. All geometry types are supported except PxParticleSystemGeometry, PxTetrahedronMeshGeometry and PxHairSystemGeometry. Number of hits between the ray and the geometry object</summary>
/// <summary>Overlap test for two geometry objects. All combinations are supported except: PxPlaneGeometry vs. {PxPlaneGeometry, PxTriangleMeshGeometry, PxHeightFieldGeometry} PxTriangleMeshGeometry vs. PxHeightFieldGeometry PxHeightFieldGeometry vs. PxHeightFieldGeometry Anything involving PxParticleSystemGeometry, PxTetrahedronMeshGeometry or PxHairSystemGeometry. True if the two geometry objects overlap</summary>
/// <summary>Sweep a specified geometry object in space and test for collision with a given object. The following combinations are supported. PxSphereGeometry vs. {PxSphereGeometry, PxPlaneGeometry, PxCapsuleGeometry, PxBoxGeometry, PxConvexMeshGeometry, PxTriangleMeshGeometry, PxHeightFieldGeometry} PxCapsuleGeometry vs. {PxSphereGeometry, PxPlaneGeometry, PxCapsuleGeometry, PxBoxGeometry, PxConvexMeshGeometry, PxTriangleMeshGeometry, PxHeightFieldGeometry} PxBoxGeometry vs. {PxSphereGeometry, PxPlaneGeometry, PxCapsuleGeometry, PxBoxGeometry, PxConvexMeshGeometry, PxTriangleMeshGeometry, PxHeightFieldGeometry} PxConvexMeshGeometry vs. {PxSphereGeometry, PxPlaneGeometry, PxCapsuleGeometry, PxBoxGeometry, PxConvexMeshGeometry, PxTriangleMeshGeometry, PxHeightFieldGeometry} True if the swept geometry object geom0 hits the object geom1</summary>
/// <summary>Compute minimum translational distance (MTD) between two geometry objects. All combinations of geom objects are supported except: - plane/plane - plane/mesh - plane/heightfield - mesh/mesh - mesh/heightfield - heightfield/heightfield - anything involving PxParticleSystemGeometry, PxTetrahedronMeshGeometry or PxHairSystemGeometry The function returns a unit vector ('direction') and a penetration depth ('depth'). The depenetration vector D = direction * depth should be applied to the first object, to get out of the second object. Returned depth should always be positive or null. If objects do not overlap, the function can not compute the MTD and returns false. True if the MTD has successfully been computed, i.e. if objects do overlap.</summary>
/// <summary>Computes distance between a point and a geometry object. Currently supported geometry objects: box, sphere, capsule, convex, mesh. For meshes, only the BVH34 midphase data-structure is supported. Square distance between the point and the geom object, or 0.0 if the point is inside the object, or -1.0 if an error occured (geometry type is not supported, or invalid pose)</summary>
/// <summary>Writes out the sample data array. The user provides destBufferSize bytes storage at destBuffer. The data is formatted and arranged as PxHeightFieldDesc.samples. The number of bytes written.</summary>
/// <summary>Replaces a rectangular subfield in the sample data array. The user provides the description of a rectangular subfield in subfieldDesc. The data is formatted and arranged as PxHeightFieldDesc.samples. True on success, false on failure. Failure can occur due to format mismatch. Modified samples are constrained to the same height quantization range as the original heightfield. Source samples that are out of range of target heightfield will be clipped with no error. PhysX does not keep a mapping from the heightfield to heightfield shapes that reference it. Call PxShape::setGeometry on each shape which references the height field, to ensure that internal data structures are updated to reflect the new geometry. Please note that PxShape::setGeometry does not guarantee correct/continuous behavior when objects are resting on top of old or new geometry.</summary>
/// <summary>Retrieves the offset in bytes between consecutive samples in the array. The offset in bytes between consecutive samples in the array.</summary>
/// <summary>Retrieves the flags bits, combined from values of the enum ::PxHeightFieldFlag. The flags bits, combined from values of the enum ::PxHeightFieldFlag.</summary>
/// <summary>Retrieves the height at the given coordinates in grid space. The height at the given coordinates or 0 if the coordinates are out of range.</summary>
/// <summary>Returns material table index of given triangle This function takes a post cooking triangle index. Material table index, or 0xffff if no per-triangle materials are used</summary>
/// <summary>Returns a triangle face normal for a given triangle index This function takes a post cooking triangle index. Triangle normal for a given triangle index</summary>
/// <summary>Returns the number of times the heightfield data has been modified This method returns the number of times modifySamples has been called on this heightfield, so that code that has retained state that depends on the heightfield can efficiently determine whether it has been modified. the number of times the heightfield sample data has been modified.</summary>
/// <summary>Retrieves triangle data from a triangle ID. This function can be used together with [`findOverlapTriangleMesh`]() to retrieve triangle properties. This function will flip the triangle normal whenever triGeom.scale.hasNegativeDeterminant() is true.</summary>
/// <summary>Retrieves triangle data from a triangle ID. This function can be used together with [`findOverlapHeightField`]() to retrieve triangle properties. This function will flip the triangle normal whenever triGeom.scale.hasNegativeDeterminant() is true. TriangleIndex is an index used in internal format, which does have an index out of the bounds in last row. To traverse all tri indices in the HF, the following code can be applied: for (PxU32 row = 0; row < (nbRows - 1); row++) { for (PxU32 col = 0; col < (nbCols - 1); col++) { for (PxU32 k = 0; k < 2; k++) { const PxU32 triIndex = 2 * (row*nbCols + col) + k; .... } } }</summary>
/// <summary>Find the mesh triangles which touch the specified geometry object. For mesh-vs-mesh overlap tests, please use the specialized function below. Returned triangle indices can be used with [`getTriangle`]() to retrieve the triangle properties. Number of overlaps found, i.e. number of elements written to the results buffer</summary>
/// <summary>Find the height field triangles which touch the specified geometry object. Returned triangle indices can be used with [`getTriangle`]() to retrieve the triangle properties. Number of overlaps found, i.e. number of elements written to the results buffer</summary>
/// <summary>Sweep a specified geometry object in space and test for collision with a set of given triangles. This function simply sweeps input geometry against each input triangle, in the order they are given. This is an O(N) operation with N = number of input triangles. It does not use any particular acceleration structure. True if the swept geometry object hits the specified triangles Only the following geometry types are currently supported: PxSphereGeometry, PxCapsuleGeometry, PxBoxGeometry If a shape from the scene is already overlapping with the query shape in its starting position, the hit is returned unless eASSUME_NO_INITIAL_OVERLAP was specified. This function returns a single closest hit across all the input triangles. Multiple hits are not supported. Supported hitFlags are PxHitFlag::eDEFAULT, PxHitFlag::eASSUME_NO_INITIAL_OVERLAP, PxHitFlag::ePRECISE_SWEEP, PxHitFlag::eMESH_BOTH_SIDES, PxHitFlag::eMESH_ANY. ePOSITION is only defined when there is no initial overlap (sweepHit.hadInitialOverlap() == false) The returned normal for initially overlapping sweeps is set to -unitDir. Otherwise the returned normal is the front normal of the triangle even if PxHitFlag::eMESH_BOTH_SIDES is set. The returned PxGeomSweepHit::faceIndex parameter will hold the index of the hit triangle in input array, i.e. the range is [0; triangleCount). For initially overlapping sweeps, this is the index of overlapping triangle. The inflation parameter is not compatible with PxHitFlag::ePRECISE_SWEEP.</summary>
/// <summary>Returns all mesh vertices for modification. This function will return the vertices of the mesh so that their positions can be changed in place. After modifying the vertices you must call refitBVH for the refitting to actually take place. This function maintains the old mesh topology (triangle indices). inplace vertex coordinates for each existing mesh vertex. It is recommended to use this feature for scene queries only. Size of array returned is equal to the number returned by getNbVertices(). This function operates on cooked vertex indices. This means the index mapping and vertex count can be different from what was provided as an input to the cooking routine. To achieve unchanged 1-to-1 index mapping with orignal mesh data (before cooking) please use the following cooking flags: eWELD_VERTICES = 0, eDISABLE_CLEAN_MESH = 1. It is also recommended to make sure that a call to validateTriangleMesh returns true if mesh cleaning is disabled.</summary>
/// <summary>Refits BVH for mesh vertices. This function will refit the mesh BVH to correctly enclose the new positions updated by getVerticesForModification. Mesh BVH will not be reoptimized by this function so significantly different new positions will cause significantly reduced performance. New bounds for the entire mesh. For PxMeshMidPhase::eBVH34 trees the refit operation is only available on non-quantized trees (see PxBVH34MidphaseDesc::quantized) PhysX does not keep a mapping from the mesh to mesh shapes that reference it. Call PxShape::setGeometry on each shape which references the mesh, to ensure that internal data structures are updated to reflect the new geometry. PxShape::setGeometry does not guarantee correct/continuous behavior when objects are resting on top of old or new geometry. It is also recommended to make sure that a call to validateTriangleMesh returns true if mesh cleaning is disabled. Active edges information will be lost during refit, the rigid body mesh contact generation might not perform as expected.</summary>
/// <summary>Returns the triangle indices. The indices can be 16 or 32bit depending on the number of triangles in the mesh. Call getTriangleMeshFlags() to know if the indices are 16 or 32 bits. The number of indices is the number of triangles * 3. array of triangles</summary>
/// <summary>Returns the triangle remapping table. The triangles are internally sorted according to various criteria. Hence the internal triangle order does not always match the original (user-defined) order. The remapping table helps finding the old indices knowing the new ones: remapTable[ internalTriangleIndex ] = originalTriangleIndex the remapping table (or NULL if 'PxCookingParams::suppressTriangleMeshRemapTable' has been used)</summary>
/// <summary>Returns material table index of given triangle This function takes a post cooking triangle index. Material table index, or 0xffff if no per-triangle materials are used</summary>
/// <summary>Sets whether this mesh should be preferred for SDF projection. By default, meshes are flagged as preferring projection and the decisions on which mesh to project is based on the triangle and vertex count. The model with the fewer triangles is projected onto the SDF of the more detailed mesh. If one of the meshes is set to prefer SDF projection (default) and the other is set to not prefer SDF projection, model flagged as preferring SDF projection will be projected onto the model flagged as not preferring, regardless of the detail of the respective meshes. Where both models are flagged as preferring no projection, the less detailed model will be projected as before.</summary>
/// <summary>Returns the mass properties of the mesh assuming unit density. The following relationship holds between mass and volume: mass = volume * density The mass of a unit density mesh is equal to its volume, so this function returns the volume of the mesh. Similarly, to obtain the localInertia of an identically shaped object with a uniform density of d, simply multiply the localInertia of the unit density mesh by d.</summary>
/// <summary>Returns the tetrahedron indices. The indices can be 16 or 32bit depending on the number of tetrahedrons in the mesh. Call getTetrahedronMeshFlags() to know if the indices are 16 or 32 bits. The number of indices is the number of tetrahedrons * 4. array of tetrahedrons</summary>
/// <summary>Returns the tetrahedra remapping table. The tetrahedra are internally sorted according to various criteria. Hence the internal tetrahedron order does not always match the original (user-defined) order. The remapping table helps finding the old indices knowing the new ones: remapTable[ internalTetrahedronIndex ] = originalTetrahedronIndex the remapping table (or NULL if 'PxCookingParams::suppressTriangleMeshRemapTable' has been used)</summary>
/// <summary>Deletes the actor. Do not keep a reference to the deleted instance. If the actor belongs to a [`PxAggregate`] object, it is automatically removed from the aggregate.</summary>
/// <summary>Sets a name string for the object that can be retrieved with getName(). This is for debugging and is not used by the SDK. The string is not copied by the SDK, only the pointer is stored. Default: NULL</summary>
/// <summary>Retrieves the axis aligned bounding box enclosing the actor. It is not allowed to use this method while the simulation is running (except during PxScene::collide(), in PxContactModifyCallback or in contact report callbacks). The actor's bounding box.</summary>
/// <summary>Raises or clears a particular actor flag. See the list of flags [`PxActorFlag`] Sleeping: Does NOT wake the actor up automatically.</summary>
/// <summary>Assigns dynamic actors a dominance group identifier. PxDominanceGroup is a 5 bit group identifier (legal range from 0 to 31). The PxScene::setDominanceGroupPair() lets you set certain behaviors for pairs of dominance groups. By default every dynamic actor is created in group 0. Default: 0 Sleeping: Changing the dominance group does NOT wake the actor up automatically.</summary>
/// <summary>Returns the owner client that was specified at creation time. This value cannot be changed once the object is placed into the scene.</summary>
/// <summary>Retrieves the aggregate the actor might be a part of. The aggregate the actor is a part of, or NULL if the actor does not belong to an aggregate.</summary>
/// <summary>Deletes the aggregate object. Deleting the PxAggregate object does not delete the aggregated actors. If the PxAggregate object belongs to a scene, the aggregated actors are automatically re-inserted in that scene. If you intend to delete both the PxAggregate and its actors, it is best to release the actors first, then release the PxAggregate when it is empty.</summary>
/// <summary>Adds an actor to the aggregate object. A warning is output if the total number of actors is reached, or if the incoming actor already belongs to an aggregate. If the aggregate belongs to a scene, adding an actor to the aggregate also adds the actor to that scene. If the actor already belongs to a scene, a warning is output and the call is ignored. You need to remove the actor from the scene first, before adding it to the aggregate. When a BVH is provided the actor shapes are grouped together. The scene query pruning structure inside PhysX SDK will store/update one bound per actor. The scene queries against such an actor will query actor bounds and then make a local space query against the provided BVH, which is in actor's local space.</summary>
/// <summary>Removes an actor from the aggregate object. A warning is output if the incoming actor does not belong to the aggregate. Otherwise the actor is removed from the aggregate. If the aggregate belongs to a scene, the actor is reinserted in that scene. If you intend to delete the actor, it is best to call [`PxActor::release`]() directly. That way the actor will be automatically removed from its aggregate (if any) and not reinserted in a scene.</summary>
/// <summary>Adds an articulation to the aggregate object. A warning is output if the total number of actors is reached (every articulation link counts as an actor), or if the incoming articulation already belongs to an aggregate. If the aggregate belongs to a scene, adding an articulation to the aggregate also adds the articulation to that scene. If the articulation already belongs to a scene, a warning is output and the call is ignored. You need to remove the articulation from the scene first, before adding it to the aggregate.</summary>
/// <summary>Removes an articulation from the aggregate object. A warning is output if the incoming articulation does not belong to the aggregate. Otherwise the articulation is removed from the aggregate. If the aggregate belongs to a scene, the articulation is reinserted in that scene. If you intend to delete the articulation, it is best to call [`PxArticulationReducedCoordinate::release`]() directly. That way the articulation will be automatically removed from its aggregate (if any) and not reinserted in a scene.</summary>
/// <summary>Returns the number of actors contained in the aggregate. You can use [`getActors`]() to retrieve the actor pointers. Number of actors contained in the aggregate.</summary>
/// <summary>Retrieve all actors contained in the aggregate. You can retrieve the number of actor pointers by calling [`getNbActors`]() Number of actor pointers written to the buffer.</summary>
/// <summary>Pre-simulation data preparation when the constraint is marked dirty, this function is called at the start of the simulation step for the SDK to copy the constraint data block.</summary>
/// <summary>Constraint release callback When the SDK deletes a PxConstraint object this function is called by the SDK. In general custom constraints should not be deleted directly by applications: rather, the constraint should respond to a release() request by calling PxConstraint::release(), then wait for this call to release its own resources. This function is also called when a PxConstraint object is deleted on cleanup due to destruction of the PxPhysics object.</summary>
/// <summary>Center-of-mass shift callback This function is called by the SDK when the CoM of one of the actors is moved. Since the API specifies constraint positions relative to actors, and the constraint shader functions are supplied with coordinates relative to bodies, some synchronization is usually required when the application moves an object's center of mass.</summary>
/// <summary>Origin shift callback This function is called by the SDK when the scene origin gets shifted and allows to adjust custom data which contains world space transforms. If the adjustments affect constraint shader data, it is necessary to call PxConstraint::markDirty() to make sure that the data gets synced at the beginning of the next simulation step.</summary>
/// <summary>Obtain a reference to a PxBase interface if the constraint has one. If the constraint does not implement the PxBase interface, it should return NULL.</summary>
/// <summary>Allocates constraint data. It is the application's responsibility to release this memory after PxSolveConstraints has completed. The allocated memory. This address must be 16-byte aligned.</summary>
/// <summary>Allocates friction data. Friction data can be retained by the application for a given pair and provided as an input to PxSolverContactDesc to improve simulation stability. It is the application's responsibility to release this memory. If this memory is released, the application should ensure it does not pass pointers to this memory to PxSolverContactDesc. The allocated memory. This address must be 4-byte aligned.</summary>
/// <summary>Sets the spring rest length for the sub-tendon from the root to this leaf attachment. Setting this on non-leaf attachments has no effect.</summary>
/// <summary>Sets the low and high limit on the length of the sub-tendon from the root to this leaf attachment. Setting this on non-leaf attachments has no effect.</summary>
/// <summary>Gets the low and high limit on the length of the sub-tendon from the root to this leaf attachment. Struct with the low and high limit.</summary>
/// <summary>Gets the attachment coefficient. The scale that the distance between this attachment and its parent is multiplied by when summing up the spatial tendon's length.</summary>
/// <summary>Indicates that this attachment is a leaf, and thus defines a sub-tendon from the root to this attachment. True: This attachment is a leaf and has zero children; False: Not a leaf.</summary>
/// <summary>Releases the attachment. Releasing the attachment is not allowed while the articulation is in a scene. In order to release the attachment, remove and then re-add the articulation to the scene.</summary>
/// <summary>Sets the tendon joint coefficient. RecipCoefficient is commonly expected to be 1/coefficient, but it can be set to different values to tune behavior; for example, zero can be used to have a joint axis only participate in the length computation of the tendon, but not have any tendon force applied to it.</summary>
/// <summary>Gets the articulation link. The articulation link (and its incoming joint in particular) that this tendon joint is associated with.</summary>
/// <summary>Releases a tendon joint. Releasing a tendon joint is not allowed while the articulation is in a scene. In order to release the joint, remove and then re-add the articulation to the scene.</summary>
/// <summary>Sets the limit stiffness term acting on the tendon's length limits. For spatial tendons, this parameter applies to all its leaf attachments / sub-tendons.</summary>
/// <summary>Gets the limit stiffness term acting on the tendon's length limits. For spatial tendons, this parameter applies to all its leaf attachments / sub-tendons. The limit stiffness term.</summary>
/// <summary>Sets the length offset term for the tendon. An offset defines an amount to be added to the accumulated length computed for the tendon. It allows the application to actuate the tendon by shortening or lengthening it.</summary>
/// <summary>Releases a tendon to remove it from the articulation and free its associated memory. When an articulation is released, its attached tendons are automatically released. Releasing a tendon is not allowed while the articulation is in a scene. In order to release the tendon, remove and then re-add the articulation to the scene.</summary>
/// <summary>Creates an articulation attachment and adds it to the list of children in the parent attachment. Creating an attachment is not allowed while the articulation is in a scene. In order to add the attachment, remove and then re-add the articulation to the scene. The newly-created attachment if creation was successful, otherwise a null pointer.</summary>
/// <summary>Fills a user-provided buffer of attachment pointers with the set of attachments. The number of attachments that were filled into the user buffer.</summary>
/// <summary>Creates an articulation tendon joint and adds it to the list of children in the parent tendon joint. Creating a tendon joint is not allowed while the articulation is in a scene. In order to add the joint, remove and then re-add the articulation to the scene. The newly-created tendon joint if creation was successful, otherwise a null pointer. - The axis motion must not be configured as PxArticulationMotion::eLOCKED. - The axis cannot be part of a fixed joint, i.e. joint configured as PxArticulationJointType::eFIX.</summary>
/// <summary>Fills a user-provided buffer of tendon-joint pointers with the set of tendon joints. The number of tendon joints filled into the user buffer.</summary>
/// <summary>Sets the spring rest length of the tendon. The accumulated \"length\" of a fixed tendon is a linear combination of the joint axis positions that the tendon is associated with, scaled by the respective tendon joints' coefficients. As such, when the joint positions of all joints are zero, the accumulated length of a fixed tendon is zero. The spring of the tendon is not exerting any force on the articulation when the rest length is equal to the tendon's accumulated length plus the tendon offset.</summary>
/// <summary>Sets the low and high limit on the length of the tendon. The limits, together with the damping and limit stiffness parameters, act on the accumulated length of the tendon.</summary>
/// <summary>Releases the sensor. Releasing a sensor is not allowed while the articulation is in a scene. In order to release a sensor, remove and then re-add the articulation to the scene.</summary>
/// <summary>Returns the spatial force in the local frame of the sensor. The spatial force. This call is not allowed while the simulation is running except in a split simulation during [`PxScene::collide`]() and up to #PxScene::advance(), and in PxContactModifyCallback or in contact report callbacks.</summary>
/// <summary>Returns the relative pose between this sensor and the body frame of the link that the sensor is attached to. The link body frame is at the center of mass and aligned with the principal axes of inertia, see PxRigidBody::getCMassLocalPose. The transform link body frame -> sensor frame.</summary>
/// <summary>Sets the relative pose between this sensor and the body frame of the link that the sensor is attached to. The link body frame is at the center of mass and aligned with the principal axes of inertia, see PxRigidBody::getCMassLocalPose. Setting the sensor relative pose is not allowed while the articulation is in a scene. In order to set the pose, remove and then re-add the articulation to the scene.</summary>
/// <summary>Returns the index of this sensor inside the articulation. The return value is only valid for sensors attached to articulations that are in a scene. The low-level index, or 0xFFFFFFFF if the articulation is not in a scene.</summary>
/// <summary>Sets a flag of the sensor. Setting the sensor flags is not allowed while the articulation is in a scene. In order to set the flags, remove and then re-add the articulation to the scene.</summary>
/// <summary>Sets the solver iteration counts for the articulation. The solver iteration count determines how accurately contacts, drives, and limits are resolved. Setting a higher position iteration count may therefore help in scenarios where the articulation is subject to many constraints; for example, a manipulator articulation with drives and joint limits that is grasping objects, or several such articulations interacting through contacts. Other situations where higher position iterations may improve simulation fidelity are: large mass ratios within the articulation or between the articulation and an object in contact with it; or strong drives in the articulation being used to manipulate a light object. If intersecting bodies are being depenetrated too violently, increase the number of velocity iterations. More velocity iterations will drive the relative exit velocity of the intersecting objects closer to the correct value given the restitution. This call may not be made during simulation.</summary>
/// <summary>Returns true if this articulation is sleeping. When an actor does not move for a period of time, it is no longer simulated in order to save time. This state is called sleeping. However, because the object automatically wakes up when it is either touched by an awake object, or a sleep-affecting property is changed by the user, the entire sleep mechanism should be transparent to the user. An articulation can only go to sleep if all links are ready for sleeping. An articulation is guaranteed to be awake if at least one of the following holds: The wake counter is positive (see [`setWakeCounter`]()). The linear or angular velocity of any link is non-zero. A non-zero force or torque has been applied to the articulation or any of its links. If an articulation is sleeping, the following state is guaranteed: The wake counter is zero. The linear and angular velocity of all links is zero. There is no force update pending. When an articulation gets inserted into a scene, it will be considered asleep if all the points above hold, else it will be treated as awake. If an articulation is asleep after the call to [`PxScene::fetchResults`]() returns, it is guaranteed that the poses of the links were not changed. You can use this information to avoid updating the transforms of associated objects. True if the articulation is sleeping. This call may only be made on articulations that are in a scene, and may not be made during simulation, except in a split simulation in-between [`PxScene::fetchCollision`] and #PxScene::advance.</summary>
/// <summary>Sets the mass-normalized energy threshold below which the articulation may go to sleep. The articulation will sleep if the energy of each link is below this threshold. This call may not be made during simulation.</summary>
/// <summary>Sets the mass-normalized kinetic energy threshold below which the articulation may participate in stabilization. Articulations whose kinetic energy divided by their mass is above this threshold will not participate in stabilization. This value has no effect if PxSceneFlag::eENABLE_STABILIZATION was not enabled on the PxSceneDesc. Default: 0.01 * PxTolerancesScale::speed * PxTolerancesScale::speed This call may not be made during simulation.</summary>
/// <summary>Returns the mass-normalized kinetic energy below which the articulation may participate in stabilization. Articulations whose kinetic energy divided by their mass is above this threshold will not participate in stabilization. The energy threshold for participating in stabilization.</summary>
/// <summary>Sets the wake counter for the articulation in seconds. - The wake counter value determines the minimum amount of time until the articulation can be put to sleep. - An articulation will not be put to sleep if the energy is above the specified threshold (see [`setSleepThreshold`]()) or if other awake objects are touching it. - Passing in a positive value will wake up the articulation automatically. Default: 0.4s (which corresponds to 20 frames for a time step of 0.02s) This call may not be made during simulation, except in a split simulation in-between [`PxScene::fetchCollision`] and #PxScene::advance.</summary>
/// <summary>Returns the wake counter of the articulation in seconds. The wake counter of the articulation in seconds. This call may not be made during simulation, except in a split simulation in-between [`PxScene::fetchCollision`] and #PxScene::advance.</summary>
/// <summary>Wakes up the articulation if it is sleeping. - The articulation will get woken up and might cause other touching objects to wake up as well during the next simulation step. - This will set the wake counter of the articulation to the value specified in [`PxSceneDesc::wakeCounterResetValue`]. This call may only be made on articulations that are in a scene, and may not be made during simulation, except in a split simulation in-between [`PxScene::fetchCollision`] and #PxScene::advance.</summary>
/// <summary>Forces the articulation to sleep. - The articulation will stay asleep during the next simulation step if not touched by another non-sleeping actor. - This will set any applied force, the velocity, and the wake counter of all bodies in the articulation to zero. This call may not be made during simulation, and may only be made on articulations that are in a scene.</summary>
/// <summary>Sets the limit on the magnitude of the linear velocity of the articulation's center of mass. - The limit acts on the linear velocity of the entire articulation. The velocity is calculated from the total momentum and the spatial inertia of the articulation. - The limit only applies to floating-base articulations. - A benefit of the COM velocity limit is that it is evenly applied to the whole articulation, which results in fewer visual artifacts compared to link rigid-body damping or joint-velocity limits. However, these per-link or per-degree-of-freedom limits may still help avoid numerical issues. This call may not be made during simulation.</summary>
/// <summary>Gets the limit on the magnitude of the linear velocity of the articulation's center of mass. The maximal linear velocity magnitude.</summary>
/// <summary>Sets the limit on the magnitude of the angular velocity at the articulation's center of mass. - The limit acts on the angular velocity of the entire articulation. The velocity is calculated from the total momentum and the spatial inertia of the articulation. - The limit only applies to floating-base articulations. - A benefit of the COM velocity limit is that it is evenly applied to the whole articulation, which results in fewer visual artifacts compared to link rigid-body damping or joint-velocity limits. However, these per-link or per-degree-of-freedom limits may still help avoid numerical issues. This call may not be made during simulation.</summary>
/// <summary>Gets the limit on the magnitude of the angular velocity at the articulation's center of mass. The maximal angular velocity magnitude.</summary>
/// <summary>Adds a link to the articulation with default attribute values. The new link, or NULL if the link cannot be created. Creating a link is not allowed while the articulation is in a scene. In order to add a link, remove and then re-add the articulation to the scene.</summary>
/// <summary>Releases the articulation, and all its links and corresponding joints. Attached sensors and tendons are released automatically when the articulation is released. This call may not be made during simulation.</summary>
/// <summary>Returns the set of links in the articulation in the order that they were added to the articulation using createLink. The number of links written into the buffer.</summary>
/// <summary>Sets a name string for the articulation that can be retrieved with getName(). This is for debugging and is not used by the SDK. The string is not copied by the SDK, only the pointer is stored.</summary>
/// <summary>Returns the axis-aligned bounding box enclosing the articulation. The articulation's bounding box. It is not allowed to use this method while the simulation is running, except in a split simulation during [`PxScene::collide`]() and up to #PxScene::advance(), and in PxContactModifyCallback or in contact report callbacks.</summary>
/// <summary>Returns the aggregate the articulation might be a part of. The aggregate the articulation is a part of, or NULL if the articulation does not belong to an aggregate.</summary>
/// <summary>Returns the total number of joint degrees-of-freedom (DOFs) of the articulation. - The six DOFs of the base of a floating-base articulation are not included in this count. - Example: Both a fixed-base and a floating-base double-pendulum with two revolute joints will have getDofs() == 2. - The return value is only valid for articulations that are in a scene. The number of joint DOFs, or 0xFFFFFFFF if the articulation is not in a scene.</summary>
/// <summary>Creates an articulation cache that can be used to read and write internal articulation data. - When the structure of the articulation changes (e.g. adding a link or sensor) after the cache was created, the cache needs to be released and recreated. - Free the memory allocated for the cache by calling the release() method on the cache. - Caches can only be created by articulations that are in a scene. The cache, or NULL if the articulation is not in a scene.</summary>
/// <summary>Returns the size of the articulation cache in bytes. - The size does not include: the user-allocated memory for the coefficient matrix or lambda values; the scratch-related memory/members; and the cache version. See comment in [`PxArticulationCache`]. - The return value is only valid for articulations that are in a scene. The byte size of the cache, or 0xFFFFFFFF if the articulation is not in a scene.</summary>
/// <summary>Zeroes all data in the articulation cache, except user-provided and scratch memory, and cache version. This call may only be made on articulations that are in a scene.</summary>
/// <summary>Applies the data in the cache to the articulation. This call wakes the articulation if it is sleeping, and the autowake parameter is true (default) or: - a nonzero joint velocity is applied or - a nonzero joint force is applied or - a nonzero root velocity is applied This call may only be made on articulations that are in a scene, and may not be made during simulation.</summary>
/// <summary>Copies internal data of the articulation to the cache. This call may only be made on articulations that are in a scene, and may not be made during simulation.</summary>
/// <summary>Converts maximal-coordinate joint DOF data to reduced coordinates. - Indexing into the maximal joint DOF data is via the link's low-level index minus 1 (the root link is not included). - The reduced-coordinate data follows the cache indexing convention, see PxArticulationCache::jointVelocity. The articulation must be in a scene.</summary>
/// <summary>Converts reduced-coordinate joint DOF data to maximal coordinates. - Indexing into the maximal joint DOF data is via the link's low-level index minus 1 (the root link is not included). - The reduced-coordinate data follows the cache indexing convention, see PxArticulationCache::jointVelocity. The articulation must be in a scene.</summary>
/// <summary>Prepares common articulation data based on articulation pose for inverse dynamics calculations. Usage: 1. Set articulation pose (joint positions and base transform) via articulation cache and applyCache(). 1. Call commonInit. 1. Call inverse dynamics computation method. This call may only be made on articulations that are in a scene, and may not be made during simulation.</summary>
/// <summary>Computes the joint DOF forces required to counteract gravitational forces for the given articulation pose. - Inputs - Articulation pose (joint positions + base transform). - Outputs - Joint forces to counteract gravity (in cache). - The joint forces returned are determined purely by gravity for the articulation in the current joint and base pose, and joints at rest; i.e. external forces, joint velocities, and joint accelerations are set to zero. Joint drives are also not considered in the computation. - commonInit() must be called before the computation, and after setting the articulation pose via applyCache(). This call may only be made on articulations that are in a scene, and may not be made during simulation.</summary>
/// <summary>Computes the joint DOF forces required to counteract Coriolis and centrifugal forces for the given articulation state. - Inputs - Articulation state (joint positions and velocities (in cache), and base transform and spatial velocity). - Outputs - Joint forces to counteract Coriolis and centrifugal forces (in cache). - The joint forces returned are determined purely by the articulation's state; i.e. external forces, gravity, and joint accelerations are set to zero. Joint drives and potential damping terms, such as link angular or linear damping, or joint friction, are also not considered in the computation. - Prior to the computation, update/set the base spatial velocity with PxArticulationCache::rootLinkData and applyCache(). - commonInit() must be called before the computation, and after setting the articulation pose via applyCache(). This call may only be made on articulations that are in a scene, and may not be made during simulation.</summary>
/// <summary>Computes the joint DOF forces required to counteract external spatial forces applied to articulation links. - Inputs - External forces on links (in cache), articulation pose (joint positions + base transform). - Outputs - Joint forces to counteract the external forces (in cache). - Only the external spatial forces provided in the cache and the articulation pose are considered in the computation. - The external spatial forces are with respect to the links' centers of mass, and not the actor's origin. - commonInit() must be called before the computation, and after setting the articulation pose via applyCache(). This call may only be made on articulations that are in a scene, and may not be made during simulation.</summary>
/// <summary>Computes the joint accelerations for the given articulation state and joint forces. - Inputs - Joint forces (in cache) and articulation state (joint positions and velocities (in cache), and base transform and spatial velocity). - Outputs - Joint accelerations (in cache). - The computation includes Coriolis terms and gravity. However, joint drives and potential damping terms are not considered in the computation (for example, linear link damping or joint friction). - Prior to the computation, update/set the base spatial velocity with PxArticulationCache::rootLinkData and applyCache(). - commonInit() must be called before the computation, and after setting the articulation pose via applyCache(). This call may only be made on articulations that are in a scene, and may not be made during simulation.</summary>
/// <summary>Computes the joint forces for the given articulation state and joint accelerations, not considering gravity. - Inputs - Joint accelerations (in cache) and articulation state (joint positions and velocities (in cache), and base transform and spatial velocity). - Outputs - Joint forces (in cache). - The computation includes Coriolis terms. However, joint drives and potential damping terms are not considered in the computation (for example, linear link damping or joint friction). - Prior to the computation, update/set the base spatial velocity with PxArticulationCache::rootLinkData and applyCache(). - commonInit() must be called before the computation, and after setting the articulation pose via applyCache(). This call may only be made on articulations that are in a scene, and may not be made during simulation.</summary>
/// <summary>Compute the dense Jacobian for the articulation in world space, including the DOFs of a potentially floating base. This computes the dense representation of an inherently sparse matrix. Multiplication with this matrix maps joint space velocities to world-space linear and angular (i.e. spatial) velocities of the centers of mass of the links. This call may only be made on articulations that are in a scene, and may not be made during simulation.</summary>
/// <summary>Computes the coefficient matrix for contact forces. - The matrix dimension is getCoefficientMatrixSize() = getDofs() * getNbLoopJoints(), and the DOF (column) indexing follows the internal DOF order, see PxArticulationCache::jointVelocity. - Each column in the matrix is the joint forces effected by a contact based on impulse strength 1. - The user must allocate memory for PxArticulationCache::coefficientMatrix where the required size of the PxReal array is equal to getCoefficientMatrixSize(). - commonInit() must be called before the computation, and after setting the articulation pose via applyCache(). This call may only be made on articulations that are in a scene, and may not be made during simulation.</summary>
/// <summary>Computes the lambda values when the test impulse is 1. - The user must allocate memory for PxArticulationCache::lambda where the required size of the PxReal array is equal to getNbLoopJoints(). - commonInit() must be called before the computation, and after setting the articulation pose via applyCache(). True if convergence was achieved within maxIter; False if convergence was not achieved or the operation failed otherwise. This call may only be made on articulations that are in a scene, and may not be made during simulation.</summary>
/// <summary>Compute the joint-space inertia matrix that maps joint accelerations to joint forces: forces = M * accelerations. - Inputs - Articulation pose (joint positions and base transform). - Outputs - Mass matrix (in cache). commonInit() must be called before the computation, and after setting the articulation pose via applyCache(). This call may only be made on articulations that are in a scene, and may not be made during simulation.</summary>
/// <summary>Returns the required size of the coefficient matrix in the articulation. Size of the coefficient matrix (equal to getDofs() * getNbLoopJoints()). This call may only be made on articulations that are in a scene.</summary>
/// <summary>Sets the root link transform (world to actor frame). - For performance, prefer PxArticulationCache::rootLinkData to set the root link transform in a batch articulation state update. - Use updateKinematic() after all state updates to the articulation via non-cache API such as this method, in order to update link states for the next simulation frame or querying. This call may not be made during simulation.</summary>
/// <summary>Returns the root link transform (world to actor frame). For performance, prefer PxArticulationCache::rootLinkData to get the root link transform in a batch query. The root link transform. This call is not allowed while the simulation is running except in a split simulation during [`PxScene::collide`]() and up to #PxScene::advance(), and in PxContactModifyCallback or in contact report callbacks.</summary>
/// <summary>Sets the root link linear center-of-mass velocity. - The linear velocity is with respect to the link's center of mass and not the actor frame origin. - For performance, prefer PxArticulationCache::rootLinkData to set the root link velocity in a batch articulation state update. - The articulation is woken up if the input velocity is nonzero (ignoring autowake) and the articulation is in a scene. - Use updateKinematic() after all state updates to the articulation via non-cache API such as this method, in order to update link states for the next simulation frame or querying. This call may not be made during simulation, except in a split simulation in-between [`PxScene::fetchCollision`] and #PxScene::advance.</summary>
/// <summary>Gets the root link center-of-mass linear velocity. - The linear velocity is with respect to the link's center of mass and not the actor frame origin. - For performance, prefer PxArticulationCache::rootLinkData to get the root link velocity in a batch query. The root link center-of-mass linear velocity. This call is not allowed while the simulation is running except in a split simulation during [`PxScene::collide`]() and up to #PxScene::advance(), and in PxContactModifyCallback or in contact report callbacks.</summary>
/// <summary>Sets the root link angular velocity. - For performance, prefer PxArticulationCache::rootLinkData to set the root link velocity in a batch articulation state update. - The articulation is woken up if the input velocity is nonzero (ignoring autowake) and the articulation is in a scene. - Use updateKinematic() after all state updates to the articulation via non-cache API such as this method, in order to update link states for the next simulation frame or querying. This call may not be made during simulation, except in a split simulation in-between [`PxScene::fetchCollision`] and #PxScene::advance.</summary>
/// <summary>Gets the root link angular velocity. For performance, prefer PxArticulationCache::rootLinkData to get the root link velocity in a batch query. The root link angular velocity. This call is not allowed while the simulation is running except in a split simulation during [`PxScene::collide`]() and up to #PxScene::advance(), and in PxContactModifyCallback or in contact report callbacks.</summary>
/// <summary>Returns the (classical) link acceleration in world space for the given low-level link index. - The returned acceleration is not a spatial, but a classical, i.e. body-fixed acceleration (https://en.wikipedia.org/wiki/Spatial_acceleration). - The (linear) acceleration is with respect to the link's center of mass and not the actor frame origin. The link's center-of-mass classical acceleration, or 0 if the call is made before the articulation participated in a first simulation step. This call may only be made on articulations that are in a scene, and it is not allowed to use this method while the simulation is running except in a split simulation during [`PxScene::collide`]() and up to #PxScene::advance(), and in PxContactModifyCallback or in contact report callbacks.</summary>
/// <summary>Returns the GPU articulation index. The GPU index, or 0xFFFFFFFF if the articulation is not in a scene or PxSceneFlag::eSUPPRESS_READBACK is not set.</summary>
/// <summary>Creates a spatial tendon to attach to the articulation with default attribute values. The new spatial tendon. Creating a spatial tendon is not allowed while the articulation is in a scene. In order to add the tendon, remove and then re-add the articulation to the scene.</summary>
/// <summary>Creates a fixed tendon to attach to the articulation with default attribute values. The new fixed tendon. Creating a fixed tendon is not allowed while the articulation is in a scene. In order to add the tendon, remove and then re-add the articulation to the scene.</summary>
/// <summary>Creates a force sensor attached to a link of the articulation. The new sensor. Creating a sensor is not allowed while the articulation is in a scene. In order to add the sensor, remove and then re-add the articulation to the scene.</summary>
/// <summary>Returns the spatial tendons attached to the articulation. The order of the tendons in the buffer is not necessarily identical to the order in which the tendons were added to the articulation. The number of tendons written into the buffer.</summary>
/// <summary>Returns the fixed tendons attached to the articulation. The order of the tendons in the buffer is not necessarily identical to the order in which the tendons were added to the articulation. The number of tendons written into the buffer.</summary>
/// <summary>Returns the sensors attached to the articulation. The order of the sensors in the buffer is not necessarily identical to the order in which the sensors were added to the articulation. The number of sensors written into the buffer.</summary>
/// <summary>Update link velocities and/or positions in the articulation. For performance, prefer the PxArticulationCache API that performs batch articulation state updates. If the application updates the root state (position and velocity) or joint state via any combination of the non-cache API calls - setRootGlobalPose(), setRootLinearVelocity(), setRootAngularVelocity() - PxArticulationJointReducedCoordinate::setJointPosition(), PxArticulationJointReducedCoordinate::setJointVelocity() the application needs to call this method after the state setting in order to update the link states for the next simulation frame or querying. Use - PxArticulationKinematicFlag::ePOSITION after any changes to the articulation root or joint positions using non-cache API calls. Updates links' positions and velocities. - PxArticulationKinematicFlag::eVELOCITY after velocity-only changes to the articulation root or joints using non-cache API calls. Updates links' velocities only. This call may only be made on articulations that are in a scene, and may not be made during simulation.</summary>
/// <summary>Sets the joint type (e.g. revolute). Setting the joint type is not allowed while the articulation is in a scene. In order to set the joint type, remove and then re-add the articulation to the scene.</summary>
/// <summary>Sets the joint motion for a given axis. Setting the motion of joint axes is not allowed while the articulation is in a scene. In order to set the motion, remove and then re-add the articulation to the scene.</summary>
/// <summary>Sets the joint limits for a given axis. - The motion of the corresponding axis should be set to PxArticulationMotion::eLIMITED in order for the limits to be enforced. - The lower limit should be strictly smaller than the higher limit. If the limits should be equal, use PxArticulationMotion::eLOCKED and an appropriate offset in the parent/child joint frames. This call is not allowed while the simulation is running. For spherical joints, limit.min and limit.max must both be in range [-Pi, Pi].</summary>
/// <summary>Configures a joint drive for the given axis. See PxArticulationDrive for parameter details; and the manual for further information, and the drives' implicit spring-damper (i.e. PD control) implementation in particular. This call is not allowed while the simulation is running.</summary>
/// <summary>Sets the joint drive position target for the given axis. The target units are linear units (equivalent to scene units) for a translational axis, or rad for a rotational axis. This call is not allowed while the simulation is running. For spherical joints, target must be in range [-Pi, Pi]. The target is specified in the parent frame of the joint. If Gp, Gc are the parent and child actor poses in the world frame and Lp, Lc are the parent and child joint frames expressed in the parent and child actor frames then the joint will drive the parent and child links to poses that obey Gp * Lp * J = Gc * Lc. For joints restricted to angular motion, J has the form PxTranfsorm(PxVec3(PxZero), PxExp(PxVec3(twistTarget, swing1Target, swing2Target))). For joints restricted to linear motion, J has the form PxTransform(PxVec3(XTarget, YTarget, ZTarget), PxQuat(PxIdentity)). For spherical joints with more than 1 degree of freedom, the joint target angles taken together can collectively represent a rotation of greater than Pi around a vector. When this happens the rotation that matches the joint drive target is not the shortest path rotation. The joint pose J that is the outcome after driving to the target pose will always be the equivalent of the shortest path rotation.</summary>
/// <summary>Sets the joint drive velocity target for the given axis. The target units are linear units (equivalent to scene units) per second for a translational axis, or radians per second for a rotational axis. This call is not allowed while the simulation is running.</summary>
/// <summary>Sets the joint armature for the given axis. - The armature is directly added to the joint-space spatial inertia of the corresponding axis. - The armature is in mass units for a prismatic (i.e. linear) joint, and in mass units * (scene linear units)^2 for a rotational joint. This call is not allowed while the simulation is running.</summary>
/// <summary>Sets the joint friction coefficient, which applies to all joint axes. - The joint friction is unitless and relates the magnitude of the spatial force [F_trans, T_trans] transmitted from parent to child link to the maximal friction force F_resist that may be applied by the solver to resist joint motion, per axis; i.e. |F_resist| < coefficient * (|F_trans| + |T_trans|), where F_resist may refer to a linear force or torque depending on the joint axis. - The simulated friction effect is therefore similar to static and Coulomb friction. In order to simulate dynamic joint friction, use a joint drive with zero stiffness and zero velocity target, and an appropriately dimensioned damping parameter. This call is not allowed while the simulation is running.</summary>
/// <summary>Sets the maximal joint velocity enforced for all axes. - The solver will apply appropriate joint-space impulses in order to enforce the per-axis joint-velocity limit. - The velocity units are linear units (equivalent to scene units) per second for a translational axis, or radians per second for a rotational axis. This call is not allowed while the simulation is running.</summary>
/// <summary>Sets the joint position for the given axis. - For performance, prefer PxArticulationCache::jointPosition to set joint positions in a batch articulation state update. - Use PxArticulationReducedCoordinate::updateKinematic after all state updates to the articulation via non-cache API such as this method, in order to update link states for the next simulation frame or querying. This call is not allowed while the simulation is running. For spherical joints, jointPos must be in range [-Pi, Pi]. Joint position is specified in the parent frame of the joint. If Gp, Gc are the parent and child actor poses in the world frame and Lp, Lc are the parent and child joint frames expressed in the parent and child actor frames then the parent and child links will be given poses that obey Gp * Lp * J = Gc * Lc with J denoting the joint pose. For joints restricted to angular motion, J has the form PxTranfsorm(PxVec3(PxZero), PxExp(PxVec3(twistPos, swing1Pos, swing2Pos))). For joints restricted to linear motion, J has the form PxTransform(PxVec3(xPos, yPos, zPos), PxQuat(PxIdentity)). For spherical joints with more than 1 degree of freedom, the input joint positions taken together can collectively represent a rotation of greater than Pi around a vector. When this happens the rotation that matches the joint positions is not the shortest path rotation. The joint pose J that is the outcome of setting and applying the joint positions will always be the equivalent of the shortest path rotation.</summary>
/// <summary>Gets the joint position for the given axis, i.e. joint degree of freedom (DOF). For performance, prefer PxArticulationCache::jointPosition to get joint positions in a batch query. The joint position in linear units (equivalent to scene units) for a translational axis, or radians for a rotational axis. This call is not allowed while the simulation is running except in a split simulation during [`PxScene::collide`]() and up to #PxScene::advance(), and in PxContactModifyCallback or in contact report callbacks.</summary>
/// <summary>Sets the joint velocity for the given axis. - For performance, prefer PxArticulationCache::jointVelocity to set joint velocities in a batch articulation state update. - Use PxArticulationReducedCoordinate::updateKinematic after all state updates to the articulation via non-cache API such as this method, in order to update link states for the next simulation frame or querying. This call is not allowed while the simulation is running.</summary>
/// <summary>Gets the joint velocity for the given axis. For performance, prefer PxArticulationCache::jointVelocity to get joint velocities in a batch query. The joint velocity in linear units (equivalent to scene units) per second for a translational axis, or radians per second for a rotational axis. This call is not allowed while the simulation is running except in a split simulation during [`PxScene::collide`]() and up to #PxScene::advance(), and in PxContactModifyCallback or in contact report callbacks.</summary>
/// <summary>Decrements the reference count of a shape and releases it if the new reference count is zero. Note that in releases prior to PhysX 3.3 this method did not have reference counting semantics and was used to destroy a shape created with PxActor::createShape(). In PhysX 3.3 and above, this usage is deprecated, instead, use PxRigidActor::detachShape() to detach a shape from an actor. If the shape to be detached was created with PxActor::createShape(), the actor holds the only counted reference, and so when the shape is detached it will also be destroyed.</summary>
/// <summary>Adjust the geometry of the shape. The type of the passed in geometry must match the geometry type of the shape. It is not allowed to change the geometry type of a shape. This function does not guarantee correct/continuous behavior when objects are resting on top of old or new geometry.</summary>
/// <summary>Retrieve a reference to the shape's geometry. The returned reference has the same lifetime as the PxShape it comes from. Reference to internal PxGeometry object.</summary>
/// <summary>Retrieves the actor which this shape is associated with. The actor this shape is associated with, if it is an exclusive shape, else NULL</summary>
/// <summary>Sets the pose of the shape in actor space, i.e. relative to the actors to which they are attached. This transformation is identity by default. The local pose is an attribute of the shape, and so will apply to all actors to which the shape is attached. Sleeping: Does NOT wake the associated actor up automatically. Note: Does not automatically update the inertia properties of the owning actor (if applicable); use the PhysX extensions method [`PxRigidBodyExt::updateMassAndInertia`]() to do this. Default: the identity transform</summary>
/// <summary>Retrieves the pose of the shape in actor space, i.e. relative to the actor they are owned by. This transformation is identity by default. Pose of shape relative to the actor's frame.</summary>
/// <summary>Sets the user definable collision filter data. Sleeping: Does wake up the actor if the filter data change causes a formerly suppressed collision pair to be enabled. Default: (0,0,0,0)</summary>
/// <summary>Assigns material(s) to the shape. Will remove existing materials from the shape. Sleeping: Does NOT wake the associated actor up automatically.</summary>
/// <summary>Returns the number of materials assigned to the shape. You can use [`getMaterials`]() to retrieve the material pointers. Number of materials associated with this shape.</summary>
/// <summary>Retrieve all the material pointers associated with the shape. You can retrieve the number of material pointers by calling [`getNbMaterials`]() Note: The returned data may contain invalid pointers if you release materials using [`PxMaterial::release`](). Number of material pointers written to the buffer.</summary>
/// <summary>Retrieve material from given triangle index. The input index is the internal triangle index as used inside the SDK. This is the index returned to users by various SDK functions such as raycasts. This function is only useful for triangle meshes or heightfields, which have per-triangle materials. For other shapes or SDF triangle meshes, the function returns the single material associated with the shape, regardless of the index. Material from input triangle If faceIndex value of 0xFFFFffff is passed as an input for mesh and heightfield shapes, this function will issue a warning and return NULL. Scene queries set the value of PxQueryHit::faceIndex to 0xFFFFffff whenever it is undefined or does not apply.</summary>
/// <summary>Sets the contact offset. Shapes whose distance is less than the sum of their contactOffset values will generate contacts. The contact offset must be positive and greater than the rest offset. Having a contactOffset greater than than the restOffset allows the collision detection system to predictively enforce the contact constraint even when the objects are slightly separated. This prevents jitter that would occur if the constraint were enforced only when shapes were within the rest distance. Default: 0.02f * PxTolerancesScale::length Sleeping: Does NOT wake the associated actor up automatically.</summary>
/// <summary>Sets the rest offset. Two shapes will come to rest at a distance equal to the sum of their restOffset values. If the restOffset is 0, they should converge to touching exactly. Having a restOffset greater than zero is useful to have objects slide smoothly, so that they do not get hung up on irregularities of each others' surfaces. Default: 0.0f Sleeping: Does NOT wake the associated actor up automatically.</summary>
/// <summary>Sets the density used to interact with fluids. To be physically accurate, the density of a rigid body should be computed as its mass divided by its volume. To simplify tuning the interaction of fluid and rigid bodies, the density for fluid can differ from the real density. This allows to create floating bodies, even if they are supposed to sink with their mass and volume. Default: 800.0f</summary>
/// <summary>Sets torsional patch radius. This defines the radius of the contact patch used to apply torsional friction. If the radius is 0, no torsional friction will be applied. If the radius is > 0, some torsional friction will be applied. This is proportional to the penetration depth so, if the shapes are separated or penetration is zero, no torsional friction will be applied. It is used to approximate rotational friction introduced by the compression of contacting surfaces. Default: 0.0</summary>
/// <summary>Gets torsional patch radius. This defines the radius of the contact patch used to apply torsional friction. If the radius is 0, no torsional friction will be applied. If the radius is > 0, some torsional friction will be applied. This is proportional to the penetration depth so, if the shapes are separated or penetration is zero, no torsional friction will be applied. It is used to approximate rotational friction introduced by the compression of contacting surfaces. The torsional patch radius of the shape.</summary>
/// <summary>Sets minimum torsional patch radius. This defines the minimum radius of the contact patch used to apply torsional friction. If the radius is 0, the amount of torsional friction that will be applied will be entirely dependent on the value of torsionalPatchRadius. If the radius is > 0, some torsional friction will be applied regardless of the value of torsionalPatchRadius or the amount of penetration. Default: 0.0</summary>
/// <summary>Gets minimum torsional patch radius. This defines the minimum radius of the contact patch used to apply torsional friction. If the radius is 0, the amount of torsional friction that will be applied will be entirely dependent on the value of torsionalPatchRadius. If the radius is > 0, some torsional friction will be applied regardless of the value of torsionalPatchRadius or the amount of penetration. The minimum torsional patch radius of the shape.</summary>
/// <summary>Sets shape flags Sleeping: Does NOT wake the associated actor up automatically. Default: PxShapeFlag::eVISUALIZATION | PxShapeFlag::eSIMULATION_SHAPE | PxShapeFlag::eSCENE_QUERY_SHAPE</summary>
/// <summary>Sets a name string for the object that can be retrieved with [`getName`](). This is for debugging and is not used by the SDK. The string is not copied by the SDK, only the pointer is stored. Default: NULL</summary>
/// <summary>Deletes the rigid actor object. Also releases any shapes associated with the actor. Releasing an actor will affect any objects that are connected to the actor (constraint shaders like joints etc.). Such connected objects will be deleted upon scene deletion, or explicitly by the user by calling release() on these objects. It is recommended to always remove all objects that reference actors before the actors themselves are removed. It is not possible to retrieve list of dead connected objects. Sleeping: This call will awaken any sleeping actors contacting the deleted actor (directly or indirectly). Calls [`PxActor::release`]() so you might want to check the documentation of that method as well.</summary>
/// <summary>Returns the internal actor index. This is only defined for actors that have been added to a scene. The internal actor index, or 0xffffffff if the actor is not part of a scene.</summary>
/// <summary>Retrieves the actors world space transform. The getGlobalPose() method retrieves the actor's current actor space to world space transformation. It is not allowed to use this method while the simulation is running (except during PxScene::collide(), in PxContactModifyCallback or in contact report callbacks). Global pose of object.</summary>
/// <summary>Method for setting an actor's pose in the world. This method instantaneously changes the actor space to world space transformation. This method is mainly for dynamic rigid bodies (see [`PxRigidDynamic`]). Calling this method on static actors is likely to result in a performance penalty, since internal optimization structures for static actors may need to be recomputed. In addition, moving static actors will not interact correctly with dynamic actors or joints. To directly control an actor's position and have it correctly interact with dynamic bodies and joints, create a dynamic body with the PxRigidBodyFlag::eKINEMATIC flag, then use the setKinematicTarget() commands to define its path. Even when moving dynamic actors, exercise restraint in making use of this method. Where possible, avoid: moving actors into other actors, thus causing overlap (an invalid physical state) moving an actor that is connected by a joint to another away from the other (thus causing joint error) Sleeping: This call wakes dynamic actors if they are sleeping and the autowake parameter is true (default).</summary>
/// <summary>Attach a shape to an actor This call will increment the reference count of the shape. Mass properties of dynamic rigid actors will not automatically be recomputed to reflect the new mass distribution implied by the shape. Follow this call with a call to the PhysX extensions method [`PxRigidBodyExt::updateMassAndInertia`]() to do that. Attaching a triangle mesh, heightfield or plane geometry shape configured as eSIMULATION_SHAPE is not supported for non-kinematic PxRigidDynamic instances. Sleeping: Does NOT wake the actor up automatically. True if success.</summary>
/// <summary>Detach a shape from an actor. This will also decrement the reference count of the PxShape, and if the reference count is zero, will cause it to be deleted. Sleeping: Does NOT wake the actor up automatically.</summary>
/// <summary>Returns the number of shapes assigned to the actor. You can use [`getShapes`]() to retrieve the shape pointers. Number of shapes associated with this actor.</summary>
/// <summary>Retrieve all the shape pointers belonging to the actor. These are the shapes used by the actor for collision detection. You can retrieve the number of shape pointers by calling [`getNbShapes`]() Note: Removing shapes with [`PxShape::release`]() will invalidate the pointer of the released shape. Number of shape pointers written to the buffer.</summary>
/// <summary>Returns the number of constraint shaders attached to the actor. You can use [`getConstraints`]() to retrieve the constraint shader pointers. Number of constraint shaders attached to this actor.</summary>
/// <summary>Retrieve all the constraint shader pointers belonging to the actor. You can retrieve the number of constraint shader pointers by calling [`getNbConstraints`]() Note: Removing constraint shaders with [`PxConstraint::release`]() will invalidate the pointer of the released constraint. Number of constraint shader pointers written to the buffer.</summary>
/// <summary>Sets the pose of the center of mass relative to the actor. Changing this transform will not move the actor in the world! Setting an unrealistic center of mass which is a long way from the body can make it difficult for the SDK to solve constraints. Perhaps leading to instability and jittering bodies. Default: the identity transform</summary>
/// <summary>Sets the mass of a dynamic actor. The mass must be non-negative. setMass() does not update the inertial properties of the body, to change the inertia tensor use setMassSpaceInertiaTensor() or the PhysX extensions method [`PxRigidBodyExt::updateMassAndInertia`](). A value of 0 is interpreted as infinite mass. Values of 0 are not permitted for instances of PxArticulationLink but are permitted for instances of PxRigidDynamic. Default: 1.0 Sleeping: Does NOT wake the actor up automatically.</summary>
/// <summary>Sets the inertia tensor, using a parameter specified in mass space coordinates. Note that such matrices are diagonal -- the passed vector is the diagonal. If you have a non diagonal world/actor space inertia tensor(3x3 matrix). Then you need to diagonalize it and set an appropriate mass space transform. See [`setCMassLocalPose`](). The inertia tensor elements must be non-negative. A value of 0 in an element is interpreted as infinite inertia along that axis. Values of 0 are not permitted for instances of PxArticulationLink but are permitted for instances of PxRigidDynamic. Default: (1.0, 1.0, 1.0) Sleeping: Does NOT wake the actor up automatically.</summary>
/// <summary>Retrieves the diagonal inertia tensor of the actor relative to the mass coordinate frame. This method retrieves a mass frame inertia vector. The mass space inertia tensor of this actor. A value of 0 in an element is interpreted as infinite inertia along that axis.</summary>
/// <summary>Retrieves the diagonal inverse inertia tensor of the actor relative to the mass coordinate frame. This method retrieves a mass frame inverse inertia vector. A value of 0 in an element is interpreted as infinite inertia along that axis. The mass space inverse inertia tensor of this actor.</summary>
/// <summary>Sets the angular damping coefficient. Zero represents no damping. The angular damping coefficient must be nonnegative. Default: 0.05</summary>
/// <summary>Retrieves the linear velocity of an actor. It is not allowed to use this method while the simulation is running (except during PxScene::collide(), in PxContactModifyCallback or in contact report callbacks). The linear velocity of the actor.</summary>
/// <summary>Retrieves the angular velocity of the actor. It is not allowed to use this method while the simulation is running (except during PxScene::collide(), in PxContactModifyCallback or in contact report callbacks). The angular velocity of the actor.</summary>
/// <summary>Lets you set the maximum linear velocity permitted for this actor. With this function, you can set the maximum linear velocity permitted for this rigid body. Higher angular velocities are clamped to this value. Note: The angular velocity is clamped to the set value before the solver, which means that the limit may still be momentarily exceeded. Default: PX_MAX_F32</summary>
/// <summary>Lets you set the maximum angular velocity permitted for this actor. For various internal computations, very quickly rotating actors introduce error into the simulation, which leads to undesired results. With this function, you can set the maximum angular velocity permitted for this rigid body. Higher angular velocities are clamped to this value. Note: The angular velocity is clamped to the set value before the solver, which means that the limit may still be momentarily exceeded. Default: 100.0</summary>
/// <summary>Applies a force (or impulse) defined in the global coordinate frame to the actor at its center of mass. This will not induce a torque . ::PxForceMode determines if the force is to be conventional or impulsive. Each actor has an acceleration and a velocity change accumulator which are directly modified using the modes PxForceMode::eACCELERATION and PxForceMode::eVELOCITY_CHANGE respectively. The modes PxForceMode::eFORCE and PxForceMode::eIMPULSE also modify these same accumulators and are just short hand for multiplying the vector parameter by inverse mass and then using PxForceMode::eACCELERATION and PxForceMode::eVELOCITY_CHANGE respectively. It is invalid to use this method if the actor has not been added to a scene already or if PxActorFlag::eDISABLE_SIMULATION is set. The force modes PxForceMode::eIMPULSE and PxForceMode::eVELOCITY_CHANGE can not be applied to articulation links. if this is called on an articulation link, only the link is updated, not the entire articulation. see [`PxRigidBodyExt::computeVelocityDeltaFromImpulse`] for details of how to compute the change in linear velocity that will arise from the application of an impulsive force, where an impulsive force is applied force multiplied by a timestep. Sleeping: This call wakes the actor if it is sleeping, and the autowake parameter is true (default) or the force is non-zero.</summary>
/// <summary>Applies an impulsive torque defined in the global coordinate frame to the actor. ::PxForceMode determines if the torque is to be conventional or impulsive. Each actor has an angular acceleration and an angular velocity change accumulator which are directly modified using the modes PxForceMode::eACCELERATION and PxForceMode::eVELOCITY_CHANGE respectively. The modes PxForceMode::eFORCE and PxForceMode::eIMPULSE also modify these same accumulators and are just short hand for multiplying the vector parameter by inverse inertia and then using PxForceMode::eACCELERATION and PxForceMode::eVELOCITY_CHANGE respectively. It is invalid to use this method if the actor has not been added to a scene already or if PxActorFlag::eDISABLE_SIMULATION is set. The force modes PxForceMode::eIMPULSE and PxForceMode::eVELOCITY_CHANGE can not be applied to articulation links. if this called on an articulation link, only the link is updated, not the entire articulation. see [`PxRigidBodyExt::computeVelocityDeltaFromImpulse`] for details of how to compute the change in angular velocity that will arise from the application of an impulsive torque, where an impulsive torque is an applied torque multiplied by a timestep. Sleeping: This call wakes the actor if it is sleeping, and the autowake parameter is true (default) or the torque is non-zero.</summary>
/// <summary>Clears the accumulated forces (sets the accumulated force back to zero). Each actor has an acceleration and a velocity change accumulator which are directly modified using the modes PxForceMode::eACCELERATION and PxForceMode::eVELOCITY_CHANGE respectively. The modes PxForceMode::eFORCE and PxForceMode::eIMPULSE also modify these same accumulators (see PxRigidBody::addForce() for details); therefore the effect of calling clearForce(PxForceMode::eFORCE) is equivalent to calling clearForce(PxForceMode::eACCELERATION), and the effect of calling clearForce(PxForceMode::eIMPULSE) is equivalent to calling clearForce(PxForceMode::eVELOCITY_CHANGE). ::PxForceMode determines if the cleared force is to be conventional or impulsive. The force modes PxForceMode::eIMPULSE and PxForceMode::eVELOCITY_CHANGE can not be applied to articulation links. It is invalid to use this method if the actor has not been added to a scene already or if PxActorFlag::eDISABLE_SIMULATION is set.</summary>
/// <summary>Clears the impulsive torque defined in the global coordinate frame to the actor. ::PxForceMode determines if the cleared torque is to be conventional or impulsive. Each actor has an angular acceleration and a velocity change accumulator which are directly modified using the modes PxForceMode::eACCELERATION and PxForceMode::eVELOCITY_CHANGE respectively. The modes PxForceMode::eFORCE and PxForceMode::eIMPULSE also modify these same accumulators (see PxRigidBody::addTorque() for details); therefore the effect of calling clearTorque(PxForceMode::eFORCE) is equivalent to calling clearTorque(PxForceMode::eACCELERATION), and the effect of calling clearTorque(PxForceMode::eIMPULSE) is equivalent to calling clearTorque(PxForceMode::eVELOCITY_CHANGE). The force modes PxForceMode::eIMPULSE and PxForceMode::eVELOCITY_CHANGE can not be applied to articulation links. It is invalid to use this method if the actor has not been added to a scene already or if PxActorFlag::eDISABLE_SIMULATION is set.</summary>
/// <summary>Sets the impulsive force and torque defined in the global coordinate frame to the actor. ::PxForceMode determines if the cleared torque is to be conventional or impulsive. The force modes PxForceMode::eIMPULSE and PxForceMode::eVELOCITY_CHANGE can not be applied to articulation links. It is invalid to use this method if the actor has not been added to a scene already or if PxActorFlag::eDISABLE_SIMULATION is set.</summary>
/// <summary>Raises or clears a particular rigid body flag. See the list of flags [`PxRigidBodyFlag`] Default: no flags are set Sleeping: Does NOT wake the actor up automatically.</summary>
/// <summary>Sets the CCD minimum advance coefficient. The CCD minimum advance coefficient is a value in the range [0, 1] that is used to control the minimum amount of time a body is integrated when it has a CCD contact. The actual minimum amount of time that is integrated depends on various properties, including the relative speed and collision shapes of the bodies involved in the contact. From these properties, a numeric value is calculated that determines the maximum distance (and therefore maximum time) which these bodies could be integrated forwards that would ensure that these bodies did not pass through each-other. This value is then scaled by CCD minimum advance coefficient to determine the amount of time that will be consumed in the CCD pass. Things to consider: A large value (approaching 1) ensures that the objects will always advance some time. However, larger values increase the chances of objects gently drifting through each-other in scenes which the constraint solver can't converge, e.g. scenes where an object is being dragged through a wall with a constraint. A value of 0 ensures that the pair of objects stop at the exact time-of-impact and will not gently drift through each-other. However, with very small/thin objects initially in contact, this can lead to a large amount of time being dropped and increases the chances of jamming. Jamming occurs when the an object is persistently in contact with an object such that the time-of-impact is 0, which results in no time being advanced for those objects in that CCD pass. The chances of jamming can be reduced by increasing the number of CCD mass</summary>
/// <summary>Sets the maximum depenetration velocity permitted to be introduced by the solver. This value controls how much velocity the solver can introduce to correct for penetrations in contacts.</summary>
/// <summary>Returns the maximum depenetration velocity the solver is permitted to introduced. This value controls how much velocity the solver can introduce to correct for penetrations in contacts. The maximum penetration bias applied by the solver.</summary>
/// <summary>Sets a limit on the impulse that may be applied at a contact. The maximum impulse at a contact between two dynamic or kinematic bodies will be the minimum of the two limit values. For a collision between a static and a dynamic body, the impulse is limited by the value for the dynamic body.</summary>
/// <summary>Sets a distance scale whereby the angular influence of a contact on the normal constraint in a contact is zeroed if normal.cross(offset) falls below this tolerance. Rather than acting as an absolute value, this tolerance is scaled by the ratio rXn.dot(angVel)/normal.dot(linVel) such that contacts that have relatively larger angular velocity than linear normal velocity (e.g. rolling wheels) achieve larger slop values as the angular velocity increases.</summary>
/// <summary>Releases the link from the articulation. Only a leaf articulation link can be released. Releasing a link is not allowed while the articulation link is in a scene. In order to release a link, remove and then re-add the corresponding articulation to the scene.</summary>
/// <summary>Gets the number of degrees of freedom of the joint which connects this link to its parent. - The root link DOF-count is defined to be 0 regardless of PxArticulationFlag::eFIX_BASE. - The return value is only valid for articulations that are in a scene. The number of degrees of freedom, or 0xFFFFFFFF if the articulation is not in a scene.</summary>
/// <summary>Gets the low-level link index that may be used to index into members of PxArticulationCache. The return value is only valid for articulations that are in a scene. The low-level index, or 0xFFFFFFFF if the articulation is not in a scene.</summary>
/// <summary>Set the constraint-force-mixing scale term. The cfm scale term is a stabilization term that helps avoid instabilities with over-constrained configurations. It should be a small value that is multiplied by 1/mass internally to produce an additional bias added to the unit response term in the solver. Default: 0.025 Range: [0, 1] This call is not allowed while the simulation is running.</summary>
/// <summary>Get the linear velocity of the link. - The linear velocity is with respect to the link's center of mass and not the actor frame origin. - For performance, prefer PxArticulationCache::linkVelocity to get link spatial velocities in a batch query. - When the articulation state is updated via non-cache API, use PxArticulationReducedCoordinate::updateKinematic before querying velocity. The linear velocity of the link. This call is not allowed while the simulation is running except in a split simulation during [`PxScene::collide`]() and up to #PxScene::advance(), and in PxContactModifyCallback or in contact report callbacks.</summary>
/// <summary>Get the angular velocity of the link. - For performance, prefer PxArticulationCache::linkVelocity to get link spatial velocities in a batch query. - When the articulation state is updated via non-cache API, use PxArticulationReducedCoordinate::updateKinematic before querying velocity. The angular velocity of the link. This call is not allowed while the simulation is running except in a split simulation during [`PxScene::collide`]() and up to #PxScene::advance(), and in PxContactModifyCallback or in contact report callbacks.</summary>
/// <summary>Retrieve the constraint force most recently applied to maintain this constraint. It is not allowed to use this method while the simulation is running (except during PxScene::collide(), in PxContactModifyCallback or in contact report callbacks).</summary>
/// <summary>whether the constraint is valid. A constraint is valid if it has at least one dynamic rigid body or articulation link. A constraint that is not valid may not be inserted into a scene, and therefore a static actor to which an invalid constraint is attached may not be inserted into a scene. Invalid constraints arise only when an actor to which the constraint is attached has been deleted.</summary>
/// <summary>Set the break force and torque thresholds for this constraint. If either the force or torque measured at the constraint exceed these thresholds the constraint will break.</summary>
/// <summary>Set the minimum response threshold for a constraint row When using mass modification for a joint or infinite inertia for a jointed body, very stiff solver constraints can be generated which can destabilize simulation. Setting this value to a small positive value (e.g. 1e-8) will cause constraint rows to be ignored if very large changes in impulses will generate only small changes in velocity. When setting this value, also set PxConstraintFlag::eDISABLE_PREPROCESSING. The solver accuracy for this joint may be reduced.</summary>
/// <summary>Fetch external owner of the constraint. Provides a reference to the external owner of a constraint and a unique owner type ID. Reference to the external object which owns the constraint.</summary>
/// <summary>Get the face index with respect to the first shape of the pair for a specific contact point in the set. The face index of the first shape At the moment, the first shape is never a tri-mesh, therefore this function always returns PXC_CONTACT_NO_FACE_INDEX</summary>
/// <summary>Get the face index with respect to the second shape of the pair for a specific contact point in the set. The face index of the second shape</summary>
/// <summary>Alter the maximum impulse for a specific contact point in the set. Must be nonnegative. If set to zero, the contact point will be ignored</summary>
/// <summary>Ignore the contact point. If a contact point is ignored then no force will get applied at this point. This can be used to disable collision in certain areas of a shape, for example.</summary>
/// <summary>Returns the invMassScale of body 0 A value < 1.0 makes this contact treat the body as if it had larger mass. A value of 0.f makes this contact treat the body as if it had infinite mass. Any value > 1.f makes this contact treat the body as if it had smaller mass.</summary>
/// <summary>Returns the invMassScale of body 1 A value < 1.0 makes this contact treat the body as if it had larger mass. A value of 0.f makes this contact treat the body as if it had infinite mass. Any value > 1.f makes this contact treat the body as if it had smaller mass.</summary>
/// <summary>Returns the invInertiaScale of body 0 A value < 1.0 makes this contact treat the body as if it had larger inertia. A value of 0.f makes this contact treat the body as if it had infinite inertia. Any value > 1.f makes this contact treat the body as if it had smaller inertia.</summary>
/// <summary>Returns the invInertiaScale of body 1 A value < 1.0 makes this contact treat the body as if it had larger inertia. A value of 0.f makes this contact treat the body as if it had infinite inertia. Any value > 1.f makes this contact treat the body as if it had smaller inertia.</summary>
/// <summary>Sets the invMassScale of body 0 This can be set to any value in the range [0, PX_MAX_F32). A value < 1.0 makes this contact treat the body as if it had larger mass. A value of 0.f makes this contact treat the body as if it had infinite mass. Any value > 1.f makes this contact treat the body as if it had smaller mass.</summary>
/// <summary>Sets the invMassScale of body 1 This can be set to any value in the range [0, PX_MAX_F32). A value < 1.0 makes this contact treat the body as if it had larger mass. A value of 0.f makes this contact treat the body as if it had infinite mass. Any value > 1.f makes this contact treat the body as if it had smaller mass.</summary>
/// <summary>Sets the invInertiaScale of body 0 This can be set to any value in the range [0, PX_MAX_F32). A value < 1.0 makes this contact treat the body as if it had larger inertia. A value of 0.f makes this contact treat the body as if it had infinite inertia. Any value > 1.f makes this contact treat the body as if it had smaller inertia.</summary>
/// <summary>Sets the invInertiaScale of body 1 This can be set to any value in the range [0, PX_MAX_F32). A value < 1.0 makes this contact treat the body as if it had larger inertia. A value of 0.f makes this contact treat the body as if it had infinite inertia. Any value > 1.f makes this contact treat the body as if it had smaller inertia.</summary>
/// <summary>Passes modifiable arrays of contacts to the application. The initial contacts are regenerated from scratch each frame by collision detection. The number of contacts can not be changed, so you cannot add your own contacts. You may however disable contacts using PxContactSet::ignore().</summary>
/// <summary>Passes modifiable arrays of contacts to the application. The initial contacts are regenerated from scratch each frame by collision detection. The number of contacts can not be changed, so you cannot add your own contacts. You may however disable contacts using PxContactSet::ignore().</summary>
/// <summary>Notification if an object or its memory gets released If release() gets called on a PxBase object, an eUSER_RELEASE event will get fired immediately. The object state can be queried in the callback but it is not allowed to change the state. Furthermore, when reading from the object it is the user's responsibility to make sure that no other thread is writing at the same time to the object (this includes the simulation itself, i.e., [`PxScene::fetchResults`]() must not get called at the same time). Calling release() on a PxBase object does not necessarily trigger its destructor immediately. For example, the object can be shared and might still be referenced by other objects or the simulation might still be running and accessing the object state. In such cases the destructor will be called as soon as it is safe to do so. After the destruction of the object and its memory, an eMEMORY_RELEASE event will get fired. In this case it is not allowed to dereference the object pointer in the callback.</summary>
/// <summary>Sets the Poisson's ratio which defines the body's volume preservation. Completely incompressible materials have a poisson ratio of 0.5. Its value should not be set to exactly 0.5 because this leads to numerical problems.</summary>
/// <summary>Sets the dynamic friction value which defines the strength of resistance when two objects slide relative to each other while in contact.</summary>
/// <summary>Specifies whether the collision object belongs to a kinematic rigid body True if the object belongs to a kinematic rigid body, else false</summary>
/// <summary>Filter method to specify how a pair of potentially colliding objects should be processed. This method gets called when the filter flags returned by the filter shader (see [`PxSimulationFilterShader`]) indicate that the filter callback should be invoked ([`PxFilterFlag::eCALLBACK`] or #PxFilterFlag::eNOTIFY set). Return the PxFilterFlag flags and set the PxPairFlag flags to define what the simulation should do with the given collision pair. Filter flags defining whether the pair should be discarded, temporarily ignored or processed and whether the pair should be tracked and send a report on pair deletion through the filter callback</summary>
/// <summary>Callback to inform that a tracked collision pair is gone. This method gets called when a collision pair disappears or gets re-filtered. Only applies to collision pairs which have been marked as filter callback pairs ([`PxFilterFlag::eNOTIFY`] set in #pairFound()).</summary>
/// <summary>Callback to give the opportunity to change the filter state of a tracked collision pair. This method gets called once per simulation step to let the application change the filter and pair flags of a collision pair that has been reported in [`pairFound`]() and requested callbacks by setting [`PxFilterFlag::eNOTIFY`]. To request a change of filter status, the target pair has to be specified by its ID, the new filter and pair flags have to be provided and the method should return true. If this method changes the filter status of a collision pair and the pair should keep being tracked by the filter callbacks then [`PxFilterFlag::eNOTIFY`] has to be set. The application is responsible to ensure that this method does not get called for pairs that have been reported as lost, see [`pairLost`](). True if the changes should be applied. In this case the method will get called again. False if no more status changes should be done in the current simulation step. In that case the provided flags will be discarded.</summary>
/// <summary>Sets the coefficient of dynamic friction. The coefficient of dynamic friction should be in [0, PX_MAX_F32). If set to greater than staticFriction, the effective value of staticFriction will be increased to match. Sleeping: Does NOT wake any actors which may be affected.</summary>
/// <summary>Sets the coefficient of static friction The coefficient of static friction should be in the range [0, PX_MAX_F32) Sleeping: Does NOT wake any actors which may be affected.</summary>
/// <summary>Sets the coefficient of restitution A coefficient of 0 makes the object bounce as little as possible, higher values up to 1.0 result in more bounce. This property is overloaded when PxMaterialFlag::eCOMPLIANT_CONTACT flag is enabled. This permits negative values for restitution to be provided. The negative values are converted into spring stiffness terms for an implicit spring simulated at the contact site, with the spring positional error defined by the contact separation value. Higher stiffness terms produce stiffer springs that behave more like a rigid contact. Sleeping: Does NOT wake any actors which may be affected.</summary>
/// <summary>Sets the coefficient of damping This property only affects the simulation if PxMaterialFlag::eCOMPLIANT_CONTACT is raised. Damping works together with spring stiffness (set through a negative restitution value). Spring stiffness corrects positional error while damping resists relative velocity. Setting a high damping coefficient can produce spongy contacts. Sleeping: Does NOT wake any actors which may be affected.</summary>
/// <summary>Raises or clears a particular material flag. See the list of flags [`PxMaterialFlag`] Default: eIMPROVED_PATCH_FRICTION Sleeping: Does NOT wake any actors which may be affected.</summary>
/// <summary>sets all the material flags. See the list of flags [`PxMaterialFlag`] Default: eIMPROVED_PATCH_FRICTION Sleeping: Does NOT wake any actors which may be affected.</summary>
/// <summary>Sets the friction combine mode. See the enum ::PxCombineMode . Default: PxCombineMode::eAVERAGE Sleeping: Does NOT wake any actors which may be affected.</summary>
/// <summary>Sets the restitution combine mode. See the enum ::PxCombineMode . Default: PxCombineMode::eAVERAGE Sleeping: Does NOT wake any actors which may be affected.</summary>
/// <summary>Retrieves the restitution combine mode. See [`setRestitutionCombineMode`]. The coefficient of restitution combine mode for this material.</summary>
/// <summary>Sets material adhesion radius scale. This is multiplied by the particle rest offset to compute the fall-off distance at which point adhesion ceases to operate.</summary>
/// <summary>Destroys the instance it is called on. Use this release method to destroy an instance of this class. Be sure to not keep a reference to this object after calling release. Avoid release calls while a scene is simulating (in between simulate() and fetchResults() calls). Note that this must be called once for each prior call to PxCreatePhysics, as there is a reference counter. Also note that you mustn't destroy the PxFoundation instance (holding the allocator, error callback etc.) until after the reference count reaches 0 and the SDK is actually removed. Releasing an SDK will also release any objects created through it (scenes, triangle meshes, convex meshes, heightfields, shapes etc.), provided the user hasn't already done so. Releasing the PxPhysics instance is a prerequisite to releasing the PxFoundation instance.</summary>
/// <summary>Creates an aggregate with the specified maximum size and filtering hint. The previous API used \"bool enableSelfCollision\" which should now silently evaluates to a PxAggregateType::eGENERIC aggregate with its self-collision bit. Use PxAggregateType::eSTATIC or PxAggregateType::eKINEMATIC for aggregates that will only contain static or kinematic actors. This provides faster filtering when used in combination with PxPairFilteringMode. The new aggregate.</summary>
/// <summary>Writes the array of triangle mesh pointers to a user buffer. Returns the number of pointers written. The ordering of the triangle meshes in the array is not specified. The number of triangle mesh pointers written to userBuffer, this should be less or equal to bufferSize.</summary>
/// <summary>Writes the array of tetrahedron mesh pointers to a user buffer. Returns the number of pointers written. The ordering of the tetrahedron meshes in the array is not specified. The number of tetrahedron mesh pointers written to userBuffer, this should be less or equal to bufferSize.</summary>
/// <summary>Creates a heightfield object from previously cooked stream. This can then be instanced into [`PxShape`] objects. The new heightfield.</summary>
/// <summary>Writes the array of heightfield pointers to a user buffer. Returns the number of pointers written. The ordering of the heightfields in the array is not specified. The number of heightfield pointers written to userBuffer, this should be less or equal to bufferSize.</summary>
/// <summary>Writes the array of convex mesh pointers to a user buffer. Returns the number of pointers written. The ordering of the convex meshes in the array is not specified. The number of convex mesh pointers written to userBuffer, this should be less or equal to bufferSize.</summary>
/// <summary>Writes the array of bounding volume hierarchy pointers to a user buffer. Returns the number of pointers written. The ordering of the BVHs in the array is not specified. The number of BVH pointers written to userBuffer, this should be less or equal to bufferSize.</summary>
/// <summary>Creates a scene. Every scene uses a Thread Local Storage slot. This imposes a platform specific limit on the number of scenes that can be created. The new scene object.</summary>
/// <summary>Writes the array of scene pointers to a user buffer. Returns the number of pointers written. The ordering of the scene pointers in the array is not specified. The number of scene pointers written to userBuffer, this should be less or equal to bufferSize.</summary>
/// <summary>Creates a pruning structure from actors. Every provided actor needs at least one shape with the eSCENE_QUERY_SHAPE flag set. Both static and dynamic actors can be provided. It is not allowed to pass in actors which are already part of a scene. Articulation links cannot be provided. Pruning structure created from given actors, or NULL if any of the actors did not comply with the above requirements.</summary>
/// <summary>Creates a shape which may be attached to multiple actors The shape will be created with a reference count of 1. The shape Shared shapes are not mutable when they are attached to an actor</summary>
/// <summary>Creates a shape which may be attached to multiple actors The shape will be created with a reference count of 1. The shape Shared shapes are not mutable when they are attached to an actor Shapes created from *SDF* triangle-mesh geometries do not support more than one material.</summary>
/// <summary>Writes the array of shape pointers to a user buffer. Returns the number of pointers written. The ordering of the shapes in the array is not specified. The number of shape pointers written to userBuffer, this should be less or equal to bufferSize.</summary>
/// <summary>Creates a constraint shader. A constraint shader will get added automatically to the scene the two linked actors belong to. Either, but not both, of actor0 and actor1 may be NULL to denote attachment to the world. The new constraint shader.</summary>
/// <summary>Writes the array of rigid body material pointers to a user buffer. Returns the number of pointers written. The ordering of the materials in the array is not specified. The number of material pointers written to userBuffer, this should be less or equal to bufferSize.</summary>
/// <summary>Register a deletion listener. Listeners will be called whenever an object is deleted. It is illegal to register or unregister a deletion listener while deletions are being processed. By default a registered listener will receive events from all objects. Set the restrictedObjectSet parameter to true on registration and use [`registerDeletionListenerObjects`] to restrict the received events to specific objects. The deletion events are only supported on core PhysX objects. In general, objects in extension modules do not provide this functionality, however, in the case of PxJoint objects, the underlying PxConstraint will send the events.</summary>
/// <summary>Unregister a deletion listener. It is illegal to register or unregister a deletion listener while deletions are being processed.</summary>
/// <summary>Register specific objects for deletion events. This method allows for a deletion listener to limit deletion events to specific objects only. It is illegal to register or unregister objects while deletions are being processed. The deletion listener has to be registered through [`registerDeletionListener`]() and configured to support restricted object sets prior to this method being used.</summary>
/// <summary>Unregister specific objects for deletion events. This method allows to clear previously registered objects for a deletion listener (see [`registerDeletionListenerObjects`]()). It is illegal to register or unregister objects while deletions are being processed. The deletion listener has to be registered through [`registerDeletionListener`]() and configured to support restricted object sets prior to this method being used.</summary>
/// <summary>Gets PxPhysics object insertion interface. The insertion interface is needed for PxCreateTriangleMesh, PxCooking::createTriangleMesh etc., this allows runtime mesh creation.</summary>
/// <summary>Creates an instance of the physics SDK. Creates an instance of this class. May not be a class member to avoid name mangling. Pass the constant [`PX_PHYSICS_VERSION`] as the argument. There may be only one instance of this class per process. Calling this method after an instance has been created already will result in an error message and NULL will be returned. Calling this will register all optional code modules (Articulations and HeightFields), preparing them for use. If you do not need some of these modules, consider calling PxCreateBasePhysics() instead and registering needed modules manually. PxPhysics instance on success, NULL if operation failed</summary>
/// <summary>This filter callback is executed before the exact intersection test if PxQueryFlag::ePREFILTER flag was set. the updated type for this hit (see [`PxQueryHitType`])</summary>
/// <summary>This filter callback is executed if the exact intersection test returned true and PxQueryFlag::ePOSTFILTER flag was set. the updated hit type for this hit (see [`PxQueryHitType`])</summary>
/// <summary>Moves kinematically controlled dynamic actors through the game world. You set a dynamic actor to be kinematic using the PxRigidBodyFlag::eKINEMATIC flag with setRigidBodyFlag(). The move command will result in a velocity that will move the body into the desired pose. After the move is carried out during a single time step, the velocity is returned to zero. Thus, you must continuously call this in every time step for kinematic actors so that they move along a path. This function simply stores the move destination until the next simulation step is processed, so consecutive calls will simply overwrite the stored target variable. The motion is always fully carried out. It is invalid to use this method if the actor has not been added to a scene already or if PxActorFlag::eDISABLE_SIMULATION is set. Sleeping: This call wakes the actor if it is sleeping and will set the wake counter to [`PxSceneDesc::wakeCounterResetValue`].</summary>
/// <summary>Get target pose of a kinematically controlled dynamic actor. True if the actor is a kinematically controlled dynamic and the target has been set, else False.</summary>
/// <summary>Returns true if this body is sleeping. When an actor does not move for a period of time, it is no longer simulated in order to save time. This state is called sleeping. However, because the object automatically wakes up when it is either touched by an awake object, or one of its properties is changed by the user, the entire sleep mechanism should be transparent to the user. In general, a dynamic rigid actor is guaranteed to be awake if at least one of the following holds: The wake counter is positive (see [`setWakeCounter`]()). The linear or angular velocity is non-zero. A non-zero force or torque has been applied. If a dynamic rigid actor is sleeping, the following state is guaranteed: The wake counter is zero. The linear and angular velocity is zero. There is no force update pending. When an actor gets inserted into a scene, it will be considered asleep if all the points above hold, else it will be treated as awake. If an actor is asleep after the call to PxScene::fetchResults() returns, it is guaranteed that the pose of the actor was not changed. You can use this information to avoid updating the transforms of associated objects. A kinematic actor is asleep unless a target pose has been set (in which case it will stay awake until two consecutive simulation steps without a target pose being set have passed). The wake counter will get set to zero or to the reset value [`PxSceneDesc::wakeCounterResetValue`] in the case where a target pose has been set to be consistent with the definitions above. It is invalid to use this method if the actor has not been added to a scene already. It is not allowed to use this method while the simulation is running. True if the actor is sleeping.</summary>
/// <summary>Sets the mass-normalized kinetic energy threshold below which an actor may go to sleep. Actors whose kinetic energy divided by their mass is below this threshold will be candidates for sleeping. Default: 5e-5f * PxTolerancesScale::speed * PxTolerancesScale::speed</summary>
/// <summary>Sets the mass-normalized kinetic energy threshold below which an actor may participate in stabilization. Actors whose kinetic energy divided by their mass is above this threshold will not participate in stabilization. This value has no effect if PxSceneFlag::eENABLE_STABILIZATION was not enabled on the PxSceneDesc. Default: 1e-5f * PxTolerancesScale::speed * PxTolerancesScale::speed</summary>
/// <summary>Returns the mass-normalized kinetic energy below which an actor may participate in stabilization. Actors whose kinetic energy divided by their mass is above this threshold will not participate in stabilization. The energy threshold for participating in stabilization.</summary>
/// <summary>Reads the PxRigidDynamic lock flags. See the list of flags [`PxRigidDynamicLockFlag`] The values of the PxRigidDynamicLock flags.</summary>
/// <summary>Raises or clears a particular rigid dynamic lock flag. See the list of flags [`PxRigidDynamicLockFlag`] Default: no flags are set</summary>
/// <summary>Retrieves the linear velocity of an actor. It is not allowed to use this method while the simulation is running (except during PxScene::collide(), in PxContactModifyCallback or in contact report callbacks). The linear velocity of the actor.</summary>
/// <summary>Sets the linear velocity of the actor. Note that if you continuously set the velocity of an actor yourself, forces such as gravity or friction will not be able to manifest themselves, because forces directly influence only the velocity/momentum of an actor. Default: (0.0, 0.0, 0.0) Sleeping: This call wakes the actor if it is sleeping, and the autowake parameter is true (default) or the new velocity is non-zero. It is invalid to use this method if PxActorFlag::eDISABLE_SIMULATION is set.</summary>
/// <summary>Retrieves the angular velocity of the actor. It is not allowed to use this method while the simulation is running (except during PxScene::collide(), in PxContactModifyCallback or in contact report callbacks). The angular velocity of the actor.</summary>
/// <summary>Sets the angular velocity of the actor. Note that if you continuously set the angular velocity of an actor yourself, forces such as friction will not be able to rotate the actor, because forces directly influence only the velocity/momentum. Default: (0.0, 0.0, 0.0) Sleeping: This call wakes the actor if it is sleeping, and the autowake parameter is true (default) or the new velocity is non-zero. It is invalid to use this method if PxActorFlag::eDISABLE_SIMULATION is set.</summary>
/// <summary>Sets the wake counter for the actor. The wake counter value determines the minimum amount of time until the body can be put to sleep. Please note that a body will not be put to sleep if the energy is above the specified threshold (see [`setSleepThreshold`]()) or if other awake bodies are touching it. Passing in a positive value will wake the actor up automatically. It is invalid to use this method for kinematic actors since the wake counter for kinematics is defined based on whether a target pose has been set (see the comment in [`isSleeping`]()). It is invalid to use this method if PxActorFlag::eDISABLE_SIMULATION is set. Default: 0.4 (which corresponds to 20 frames for a time step of 0.02)</summary>
/// <summary>Returns the wake counter of the actor. It is not allowed to use this method while the simulation is running. The wake counter of the actor.</summary>
/// <summary>Wakes up the actor if it is sleeping. The actor will get woken up and might cause other touching actors to wake up as well during the next simulation step. This will set the wake counter of the actor to the value specified in [`PxSceneDesc::wakeCounterResetValue`]. It is invalid to use this method if the actor has not been added to a scene already or if PxActorFlag::eDISABLE_SIMULATION is set. It is invalid to use this method for kinematic actors since the sleep state for kinematics is defined based on whether a target pose has been set (see the comment in [`isSleeping`]()).</summary>
/// <summary>Forces the actor to sleep. The actor will stay asleep during the next simulation step if not touched by another non-sleeping actor. Any applied force will be cleared and the velocity and the wake counter of the actor will be set to 0. It is invalid to use this method if the actor has not been added to a scene already or if PxActorFlag::eDISABLE_SIMULATION is set. It is invalid to use this method for kinematic actors since the sleep state for kinematics is defined based on whether a target pose has been set (see the comment in [`isSleeping`]()).</summary>
/// <summary>Sets the solver iteration counts for the body. The solver iteration count determines how accurately joints and contacts are resolved. If you are having trouble with jointed bodies oscillating and behaving erratically, then setting a higher position iteration count may improve their stability. If intersecting bodies are being depenetrated too violently, increase the number of velocity iterations. More velocity iterations will drive the relative exit velocity of the intersecting objects closer to the correct value given the restitution. Default: 4 position iterations, 1 velocity iteration</summary>
/// <summary>Retrieves the force threshold for contact reports. The contact report threshold is a force threshold. If the force between two actors exceeds this threshold for either of the two actors, a contact report will be generated according to the contact report threshold flags provided by the filter shader/callback. See [`PxPairFlag`]. The threshold used for a collision between a dynamic actor and the static environment is the threshold of the dynamic actor, and all contacts with static actors are summed to find the total normal force. Default: PX_MAX_F32 Force threshold for contact reports.</summary>
/// <summary>Forces dynamic trees to be immediately rebuilt. PxScene will call this function with the PX_SCENE_PRUNER_STATIC or PX_SCENE_PRUNER_DYNAMIC value.</summary>
/// <summary>Retrieves the system's internal scene query timestamp, increased each time a change to the static scene query structure is performed. scene query static timestamp</summary>
/// <summary>Flushes any changes to the scene query representation. This method updates the state of the scene query representation to match changes in the scene state. By default, these changes are buffered until the next query is submitted. Calling this function will not change the results from scene queries, but can be used to ensure that a query will not perform update work in the course of its execution. A thread performing updates will hold a write lock on the query structure, and thus stall other querying threads. In multithread scenarios it can be useful to explicitly schedule the period where this lock may be held for a significant period, so that subsequent queries issued from multiple threads will not block.</summary>
/// <summary>Performs a raycast against objects in the scene, returns results in a PxRaycastBuffer object or via a custom user callback implementation inheriting from PxRaycastCallback. Touching hits are not ordered. Shooting a ray from within an object leads to different results depending on the shape type. Please check the details in user guide article SceneQuery. User can ignore such objects by employing one of the provided filter mechanisms. True if any touching or blocking hits were found or any hit was found in case PxQueryFlag::eANY_HIT was specified.</summary>
/// <summary>Performs a sweep test against objects in the scene, returns results in a PxSweepBuffer object or via a custom user callback implementation inheriting from PxSweepCallback. Touching hits are not ordered. If a shape from the scene is already overlapping with the query shape in its starting position, the hit is returned unless eASSUME_NO_INITIAL_OVERLAP was specified. True if any touching or blocking hits were found or any hit was found in case PxQueryFlag::eANY_HIT was specified.</summary>
/// <summary>Performs an overlap test of a given geometry against objects in the scene, returns results in a PxOverlapBuffer object or via a custom user callback implementation inheriting from PxOverlapCallback. Filtering: returning eBLOCK from user filter for overlap queries will cause a warning (see [`PxQueryHitType`]). True if any touching or blocking hits were found or any hit was found in case PxQueryFlag::eANY_HIT was specified. eBLOCK should not be returned from user filters for overlap(). Doing so will result in undefined behavior, and a warning will be issued. If the PxQueryFlag::eNO_BLOCK flag is set, the eBLOCK will instead be automatically converted to an eTOUCH and the warning suppressed.</summary>
/// <summary>Retrieves the scene's internal scene query timestamp, increased each time a change to the static scene query structure is performed. scene query static timestamp</summary>
/// <summary>Executes scene queries update tasks. This function will refit dirty shapes within the pruner and will execute a task to build a new AABB tree, which is build on a different thread. The new AABB tree is built based on the dynamic tree rebuild hint rate. Once the new tree is ready it will be commited in next fetchQueries call, which must be called after. This function is equivalent to the following PxSceneQuerySystem calls: Synchronous calls: - PxSceneQuerySystemBase::flushUpdates() - handle0 = PxSceneQuerySystem::prepareSceneQueryBuildStep(PX_SCENE_PRUNER_STATIC) - handle1 = PxSceneQuerySystem::prepareSceneQueryBuildStep(PX_SCENE_PRUNER_DYNAMIC) Asynchronous calls: - PxSceneQuerySystem::sceneQueryBuildStep(handle0); - PxSceneQuerySystem::sceneQueryBuildStep(handle1); This function is part of the PxSceneSQSystem interface because it uses the PxScene task system under the hood. But it calls PxSceneQuerySystem functions, which are independent from this system and could be called in a similar fashion by a separate, possibly user-defined task manager. If PxSceneQueryUpdateMode::eBUILD_DISABLED_COMMIT_DISABLED is used, it is required to update the scene queries using this function.</summary>
/// <summary>This checks to see if the scene queries update has completed. This does not cause the data available for reading to be updated with the results of the scene queries update, it is simply a status check. The bool will allow it to either return immediately or block waiting for the condition to be met so that it can return true True if the results are available.</summary>
/// <summary>This method must be called after sceneQueriesUpdate. It will wait for the scene queries update to finish. If the user makes an illegal scene queries update call, the SDK will issue an error message. If a new AABB tree build finished, then during fetchQueries the current tree within the pruning structure is swapped with the new tree.</summary>
/// <summary>Acquires a counted reference to this object. This method increases the reference count of the object by 1. Decrement the reference count by calling release()</summary>
/// <summary>Preallocates internal arrays to minimize the amount of reallocations. The system does not prevent more allocations than given numbers. It is legal to not call this function at all, or to add more shapes to the system than the preallocated amounts.</summary>
/// <summary>Frees internal memory that may not be in-use anymore. This is an entry point for reclaiming transient memory allocated at some point by the SQ system, but which wasn't been immediately freed for performance reason. Calling this function might free some memory, but it might also produce a new set of allocations in the next frame.</summary>
/// <summary>Updates a shape in the SQ system. The same function is used to update either a regular shape, or a SQ compound shape. The transforms are eager-evaluated, but the bounds are lazy-evaluated. This means that the updated transform has to be passed to the update function, while the bounds are automatically recomputed by the system whenever needed.</summary>
/// <summary>Shape to SQ-pruner-handle mapping function. This function finds and returns the SQ pruner handle associated with a given (actor/shape) couple that was previously added to the system. This is needed for the sync function. Associated SQ pruner handle.</summary>
/// <summary>Synchronizes the scene-query system with another system that references the same objects. This function is used when the scene-query objects also exist in another system that can also update them. For example the scene-query objects (used for raycast, overlap or sweep queries) might be driven by equivalent objects in an external rigid-body simulation engine. In this case the rigid-body simulation engine computes the new poses and transforms, and passes them to the scene-query system using this function. It is more efficient than calling updateSQShape on each object individually, since updateSQShape would end up recomputing the bounds already available in the rigid-body engine.</summary>
/// <summary>Finalizes updates made to the SQ system. This function should be called after updates have been made to the SQ system, to fully reflect the changes inside the internal pruners. In particular it should be called: - after calls to updateSQShape - after calls to sync This function: - recomputes bounds of manually updated shapes (i.e. either regular or SQ compound shapes modified by updateSQShape) - updates dynamic pruners (refit operations) - incrementally rebuilds AABB-trees The amount of work performed in this function depends on PxSceneQueryUpdateMode.</summary>
/// <summary>Prepares asynchronous build step. This is directly called (synchronously) by PxSceneSQSystem::sceneQueriesUpdate(). See the comments there. This function is called to let the system execute any necessary synchronous operation before the asynchronous sceneQueryBuildStep() function is called. If there is any work to do for the specific pruner, the function returns a pruner-specific handle that will be passed to the corresponding, asynchronous sceneQueryBuildStep function. A pruner-specific handle that will be sent to sceneQueryBuildStep if there is any work to do, i.e. to execute the corresponding sceneQueryBuildStep() call. Null if there is no work to do, otherwise a pruner-specific handle.</summary>
/// <summary>Executes asynchronous build step. This is directly called (asynchronously) by PxSceneSQSystem::sceneQueriesUpdate(). See the comments there. This function incrementally builds the internal trees/pruners. It is called asynchronously, i.e. this can be called from different threads for building multiple trees at the same time.</summary>
/// <summary>Retrieves the filter group for static objects. Mark static objects with this group when adding them to the broadphase. Overlaps between static objects will not be detected. All static objects should have the same group. Filter group for static objects.</summary>
/// <summary>Retrieves a filter group for dynamic objects. Mark dynamic objects with this group when adding them to the broadphase. Each dynamic object must have an ID, and overlaps between dynamic objects that have the same ID will not be detected. This is useful to dismiss overlaps between shapes of the same (compound) actor directly within the broadphase. Filter group for the object.</summary>
/// <summary>Retrieves a filter group for kinematic objects. Mark kinematic objects with this group when adding them to the broadphase. Each kinematic object must have an ID, and overlaps between kinematic objects that have the same ID will not be detected. Filter group for the object.</summary>
/// <summary>Adds a new broad-phase region. The total number of regions is limited to PxBroadPhaseCaps::mMaxNbRegions. If that number is exceeded, the call is ignored. The newly added region will be automatically populated with already existing objects that touch it, if the 'populateRegion' parameter is set to true. Otherwise the newly added region will be empty, and it will only be populated with objects when those objects are added to the simulation, or updated if they already exist. Using 'populateRegion=true' has a cost, so it is best to avoid it if possible. In particular it is more efficient to create the empty regions first (with populateRegion=false) and then add the objects afterwards (rather than the opposite). Objects automatically move from one region to another during their lifetime. The system keeps tracks of what regions a given object is in. It is legal for an object to be in an arbitrary number of regions. However if an object leaves all regions, or is created outside of all regions, several things happen: - collisions get disabled for this object - the object appears in the getOutOfBoundsObjects() array If an out-of-bounds object, whose collisions are disabled, re-enters a valid broadphase region, then collisions are re-enabled for that object. Handle for newly created region, or 0xffffffff in case of failure.</summary>
/// <summary>Removes a broad-phase region. If the region still contains objects, and if those objects do not overlap any region any more, they are not automatically removed from the simulation. Instead, the PxBroadPhaseCallback::onObjectOutOfBounds notification is used for each object. Users are responsible for removing the objects from the simulation if this is the desired behavior. If the handle is invalid, or if a valid handle is removed twice, an error message is sent to the error stream. True if success</summary>
/// <summary>Retrieves the regions API if applicable. For broadphases that do not use explicit user-defined regions, this call returns NULL. Region API, or NULL.</summary>
/// <summary>Retrieves the broadphase allocator. User-provided buffers should ideally be allocated with this allocator, for best performance. This is especially true for the GPU broadphases, whose buffers need to be allocated in CUDA host memory. The broadphase allocator.</summary>
/// <summary>Sets a scratch buffer Some broadphases might take advantage of a scratch buffer to limit runtime allocations. All broadphases still work without providing a scratch buffer, this is an optional function that can potentially reduce runtime allocations.</summary>
/// <summary>Updates the broadphase and computes the lists of created/deleted pairs. The provided update data describes changes to objects since the last broadphase update. To benefit from potentially multithreaded implementations, it is necessary to provide a continuation task to the function. It is legal to pass NULL there, but the underlying (CPU) implementations will then run single-threaded.</summary>
/// <summary>Retrieves the broadphase results after an update. This should be called once after each update call to retrieve the results of the broadphase. The results are incremental, i.e. the system only returns new and lost pairs, not all current pairs.</summary>
/// <summary>Helper for single-threaded updates. This short helper function performs a single-theaded update and reports the results in a single call.</summary>
/// <summary>Retrieves the managed bounds. This is needed as input parameters to functions like PxBroadPhaseRegions::addRegion. The managed object bounds.</summary>
/// <summary>Retrieves the managed distances. This is needed as input parameters to functions like PxBroadPhaseRegions::addRegion. The managed object distances.</summary>
/// <summary>Retrieves the managed buffers' capacity. Bounds, distances and groups buffers have the same capacity. The managed buffers' capacity.</summary>
/// <summary>Adds an object to the manager. Objects' indices are externally managed, i.e. they must be provided by users (as opposed to handles that could be returned by this manager). The design allows users to identify an object by a single ID, and use the same ID in multiple sub-systems.</summary>
/// <summary>Updates an object in the manager. This call can update an object's bounds, distance, or both. It is not possible to update an object's filter group.</summary>
/// <summary>Updates the broadphase and computes the lists of created/deleted pairs. The data necessary for updating the broadphase is internally computed by the AABB manager. To benefit from potentially multithreaded implementations, it is necessary to provide a continuation task to the function. It is legal to pass NULL there, but the underlying (CPU) implementations will then run single-threaded.</summary>
/// <summary>Retrieves the broadphase results after an update. This should be called once after each update call to retrieve the results of the broadphase. The results are incremental, i.e. the system only returns new and lost pairs, not all current pairs.</summary>
/// <summary>Helper for single-threaded updates. This short helper function performs a single-theaded update and reports the results in a single call.</summary>
/// <summary>AABB manager factory function. Use this function to create a new standalone high-level broadphase. Newly created AABB manager, or NULL</summary>
/// <summary>Get number of shape collision pairs of a certain type processed for the current simulation step. There is an entry for each geometry pair type. entry[i][j] = entry[j][i], hence, if you want the sum of all pair types, you need to discard the symmetric entries Number of processed pairs of the specified geometry types.</summary>
/// <summary>Deletes the scene. Removes any actors and constraint shaders from this scene (if the user hasn't already done so). Be sure to not keep a reference to this object after calling release. Avoid release calls while the scene is simulating (in between simulate() and fetchResults() calls).</summary>
/// <summary>Sets a scene flag. You can only set one flag at a time. Not all flags are mutable and changing some will result in an error. Please check [`PxSceneFlag`] to see which flags can be changed.</summary>
/// <summary>Set new scene limits. Increase the maximum capacity of various data structures in the scene. The new capacities will be at least as large as required to deal with the objects currently in the scene. Further, these values are for preallocation and do not represent hard limits.</summary>
/// <summary>Adds an articulation to this scene. If the articulation is already assigned to a scene (see [`PxArticulationReducedCoordinate::getScene`]), the call is ignored and an error is issued. True if success</summary>
/// <summary>Removes an articulation from this scene. If the articulation is not part of this scene (see [`PxArticulationReducedCoordinate::getScene`]), the call is ignored and an error is issued. If the articulation is in an aggregate it will be removed from the aggregate.</summary>
/// <summary>Adds an actor to this scene. If the actor is already assigned to a scene (see [`PxActor::getScene`]), the call is ignored and an error is issued. If the actor has an invalid constraint, in checked builds the call is ignored and an error is issued. You can not add individual articulation links (see [`PxArticulationLink`]) to the scene. Use #addArticulation() instead. If the actor is a PxRigidActor then each assigned PxConstraint object will get added to the scene automatically if it connects to another actor that is part of the scene already. When a BVH is provided the actor shapes are grouped together. The scene query pruning structure inside PhysX SDK will store/update one bound per actor. The scene queries against such an actor will query actor bounds and then make a local space query against the provided BVH, which is in actor's local space. True if success</summary>
/// <summary>Adds actors to this scene. Only supports actors of type PxRigidStatic and PxRigidDynamic. This method only supports actors of type PxRigidStatic and PxRigidDynamic. For other actors, use addActor() instead. For articulation links, use addArticulation(). If one of the actors is already assigned to a scene (see [`PxActor::getScene`]), the call is ignored and an error is issued. If an actor in the array contains an invalid constraint, in checked builds the call is ignored and an error is issued. If an actor in the array is a PxRigidActor then each assigned PxConstraint object will get added to the scene automatically if it connects to another actor that is part of the scene already. this method is optimized for high performance. True if success</summary>
/// <summary>Adds a pruning structure together with its actors to this scene. Only supports actors of type PxRigidStatic and PxRigidDynamic. This method only supports actors of type PxRigidStatic and PxRigidDynamic. For other actors, use addActor() instead. For articulation links, use addArticulation(). If an actor in the pruning structure contains an invalid constraint, in checked builds the call is ignored and an error is issued. For all actors in the pruning structure each assigned PxConstraint object will get added to the scene automatically if it connects to another actor that is part of the scene already. This method is optimized for high performance. Merging a PxPruningStructure into an active scene query optimization AABB tree might unbalance the tree. A typical use case for PxPruningStructure is a large world scenario where blocks of closely positioned actors get streamed in. The merge process finds the best node in the active scene query optimization AABB tree and inserts the PxPruningStructure. Therefore using PxPruningStructure for actors scattered throughout the world will result in an unbalanced tree. True if success</summary>
/// <summary>Removes an actor from this scene. If the actor is not part of this scene (see [`PxActor::getScene`]), the call is ignored and an error is issued. You can not remove individual articulation links (see [`PxArticulationLink`]) from the scene. Use #removeArticulation() instead. If the actor is a PxRigidActor then all assigned PxConstraint objects will get removed from the scene automatically. If the actor is in an aggregate it will be removed from the aggregate.</summary>
/// <summary>Removes actors from this scene. Only supports actors of type PxRigidStatic and PxRigidDynamic. This method only supports actors of type PxRigidStatic and PxRigidDynamic. For other actors, use removeActor() instead. For articulation links, use removeArticulation(). If some actor is not part of this scene (see [`PxActor::getScene`]), the actor remove is ignored and an error is issued. You can not remove individual articulation links (see [`PxArticulationLink`]) from the scene. Use #removeArticulation() instead. If the actor is a PxRigidActor then all assigned PxConstraint objects will get removed from the scene automatically.</summary>
/// <summary>Adds an aggregate to this scene. If the aggregate is already assigned to a scene (see [`PxAggregate::getScene`]), the call is ignored and an error is issued. If the aggregate contains an actor with an invalid constraint, in checked builds the call is ignored and an error is issued. If the aggregate already contains actors, those actors are added to the scene as well. True if success</summary>
/// <summary>Removes an aggregate from this scene. If the aggregate is not part of this scene (see [`PxAggregate::getScene`]), the call is ignored and an error is issued. If the aggregate contains actors, those actors are removed from the scene as well.</summary>
/// <summary>Adds objects in the collection to this scene. This function adds the following types of objects to this scene: PxRigidActor (except PxArticulationLink), PxAggregate, PxArticulationReducedCoordinate. This method is typically used after deserializing the collection in order to populate the scene with deserialized objects. If the collection contains an actor with an invalid constraint, in checked builds the call is ignored and an error is issued. True if success</summary>
/// <summary>Retrieve an array of all the actors of certain types in the scene. For supported types, see PxActorTypeFlags. Number of actors written to the buffer.</summary>
/// <summary>Queries the PxScene for a list of the PxActors whose transforms have been updated during the previous simulation step. Only includes actors of type PxRigidDynamic and PxArticulationLink. PxSceneFlag::eENABLE_ACTIVE_ACTORS must be set. Do not use this method while the simulation is running. Calls to this method while the simulation is running will be ignored and NULL will be returned. A pointer to the list of active PxActors generated during the last call to fetchResults().</summary>
/// <summary>Specifies the dominance behavior of contacts between two actors with two certain dominance groups. It is possible to assign each actor to a dominance groups using [`PxActor::setDominanceGroup`](). With dominance groups one can have all contacts created between actors act in one direction only. This is useful, for example, if you want an object to push debris out of its way and be unaffected,while still responding physically to forces and collisions with non-debris objects. Whenever a contact between two actors (a0, a1) needs to be solved, the groups (g0, g1) of both actors are retrieved. Then the PxDominanceGroupPair setting for this group pair is retrieved with getDominanceGroupPair(g0, g1). In the contact, PxDominanceGroupPair::dominance0 becomes the dominance setting for a0, and PxDominanceGroupPair::dominance1 becomes the dominance setting for a1. A dominanceN setting of 1.0f, the default, will permit aN to be pushed or pulled by a(1-N) through the contact. A dominanceN setting of 0.0f, will however prevent aN to be pushed by a(1-N) via the contact. Thus, a PxDominanceGroupPair of (1.0f, 0.0f) makes the interaction one-way. The matrix sampled by getDominanceGroupPair(g1, g2) is initialised by default such that: if g1 == g2, then (1.0f, 1.0f) is returned if g1 < g2, then (0.0f, 1.0f) is returned if g1 > g2, then (1.0f, 0.0f) is returned In other words, we permit actors in higher groups to be pushed around by actors in lower groups by default. These settings should cover most applications, and in fact not overriding these settings may likely result in higher performance. It is not possible to make the matrix asymetric, or to change the diagonal. In other words: it is not possible to change (g1, g2) if (g1==g2) if you set (g1, g2) to X, then (g2, g1) will implicitly and automatically be set to ~X, where: ~(1.0f, 1.0f) is (1.0f, 1.0f) ~(0.0f, 1.0f) is (1.0f, 0.0f) ~(1.0f, 0.0f) is (0.0f, 1.0f) These two restrictions are to make sure that contacts between two actors will always evaluate to the same dominance setting, regardless of the order of the actors. Dominance settings are currently specified as floats 0.0f or 1.0f because in the future we may permit arbitrary fractional settings to express 'partly-one-way' interactions. Sleeping: Does NOT wake actors up automatically.</summary>
/// <summary>Reserves a new client ID. PX_DEFAULT_CLIENT is always available as the default clientID. Additional clients are returned by this function. Clients cannot be released once created. An error is reported when more than a supported number of clients (currently 128) are created.</summary>
/// <summary>Sets a user notify object which receives special simulation events when they occur. Do not set the callback while the simulation is running. Calls to this method while the simulation is running will be ignored.</summary>
/// <summary>Retrieves the simulationEventCallback pointer set with setSimulationEventCallback(). The current user notify pointer. See [`PxSimulationEventCallback`].</summary>
/// <summary>Sets a user callback object, which receives callbacks on all contacts generated for specified actors. Do not set the callback while the simulation is running. Calls to this method while the simulation is running will be ignored.</summary>
/// <summary>Sets a user callback object, which receives callbacks on all CCD contacts generated for specified actors. Do not set the callback while the simulation is running. Calls to this method while the simulation is running will be ignored.</summary>
/// <summary>Retrieves the PxContactModifyCallback pointer set with setContactModifyCallback(). The current user contact modify callback pointer. See [`PxContactModifyCallback`].</summary>
/// <summary>Retrieves the PxCCDContactModifyCallback pointer set with setContactModifyCallback(). The current user contact modify callback pointer. See [`PxContactModifyCallback`].</summary>
/// <summary>Sets a broad-phase user callback object. Do not set the callback while the simulation is running. Calls to this method while the simulation is running will be ignored.</summary>
/// <summary>Retrieves the PxBroadPhaseCallback pointer set with setBroadPhaseCallback(). The current broad-phase callback pointer. See [`PxBroadPhaseCallback`].</summary>
/// <summary>Sets the shared global filter data which will get passed into the filter shader. It is the user's responsibility to ensure that changing the shared global filter data does not change the filter output value for existing pairs. If the filter output for existing pairs does change nonetheless then such a change will not take effect until the pair gets refiltered. resetFiltering() can be used to explicitly refilter the pairs of specific objects. The provided data will get copied to internal buffers and this copy will be used for filtering calls. Do not use this method while the simulation is running. Calls to this method while the simulation is running will be ignored.</summary>
/// <summary>Gets the shared global filter data in use for this scene. The reference points to a copy of the original filter data specified in [`PxSceneDesc`].filterShaderData or provided by #setFilterShaderData(). Shared filter data for filter shader.</summary>
/// <summary>Marks the object to reset interactions and re-run collision filters in the next simulation step. This call forces the object to remove all existing collision interactions, to search anew for existing contact pairs and to run the collision filters again for found collision pairs. The operation is supported for PxRigidActor objects only. All persistent state of existing interactions will be lost and can not be retrieved even if the same collison pair is found again in the next step. This will mean, for example, that you will not get notified about persistent contact for such an interaction (see [`PxPairFlag::eNOTIFY_TOUCH_PERSISTS`]), the contact pair will be interpreted as newly found instead. Lost touch contact reports will be sent for every collision pair which includes this shape, if they have been requested through [`PxPairFlag::eNOTIFY_TOUCH_LOST`] or #PxPairFlag::eNOTIFY_THRESHOLD_FORCE_LOST. This is an expensive operation, don't use it if you don't have to. Can be used to retrieve collision pairs that were killed by the collision filters (see [`PxFilterFlag::eKILL`]) It is invalid to use this method if the actor has not been added to a scene already. It is invalid to use this method if PxActorFlag::eDISABLE_SIMULATION is set. Do not use this method while the simulation is running. Sleeping: Does wake up the actor. True if success</summary>
/// <summary>Marks the object to reset interactions and re-run collision filters for specified shapes in the next simulation step. This is a specialization of the resetFiltering(PxActor & actor) method and allows to reset interactions for specific shapes of a PxRigidActor. Do not use this method while the simulation is running. Sleeping: Does wake up the actor.</summary>
/// <summary>Advances the simulation by an elapsedTime time. Large elapsedTime values can lead to instabilities. In such cases elapsedTime should be subdivided into smaller time intervals and simulate() should be called multiple times for each interval. Calls to simulate() should pair with calls to fetchResults(): Each fetchResults() invocation corresponds to exactly one simulate() invocation; calling simulate() twice without an intervening fetchResults() or fetchResults() twice without an intervening simulate() causes an error condition. scene->simulate(); ...do some processing until physics is computed... scene->fetchResults(); ...now results of run may be retrieved. True if success</summary>
/// <summary>Performs dynamics phase of the simulation pipeline. Calls to advance() should follow calls to fetchCollision(). An error message will be issued if this sequence is not followed. True if success</summary>
/// <summary>Performs collision detection for the scene over elapsedTime Calls to collide() should be the first method called to simulate a frame. True if success</summary>
/// <summary>This checks to see if the simulation run has completed. This does not cause the data available for reading to be updated with the results of the simulation, it is simply a status check. The bool will allow it to either return immediately or block waiting for the condition to be met so that it can return true True if the results are available.</summary>
/// <summary>This method must be called after collide() and before advance(). It will wait for the collision phase to finish. If the user makes an illegal simulation call, the SDK will issue an error message.</summary>
/// <summary>This call performs the first section of fetchResults, and returns a pointer to the contact streams output by the simulation. It can be used to process contact pairs in parallel, which is often a limiting factor for fetchResults() performance. After calling this function and processing the contact streams, call fetchResultsFinish(). Note that writes to the simulation are not permitted between the start of fetchResultsStart() and the end of fetchResultsFinish(). True if the results have been fetched.</summary>
/// <summary>This call processes all event callbacks in parallel. It takes a continuation task, which will be executed once all callbacks have been processed. This is a utility function to make it easier to process callbacks in parallel using the PhysX task system. It can only be used in conjunction with fetchResultsStart(...) and fetchResultsFinish(...)</summary>
/// <summary>This call performs the second section of fetchResults. It must be called after fetchResultsStart() returns and contact reports have been processed. Note that once fetchResultsFinish() has been called, the contact streams returned in fetchResultsStart() will be invalid.</summary>
/// <summary>Clear internal buffers and free memory. This method can be used to clear buffers and free internal memory without having to destroy the scene. Can be useful if the physics data gets streamed in and a checkpoint with a clean state should be created. It is not allowed to call this method while the simulation is running. The call will fail.</summary>
/// <summary>Sets a constant gravity for the entire scene. Do not use this method while the simulation is running. Sleeping: Does NOT wake the actor up automatically.</summary>
/// <summary>Set the bounce threshold velocity. Collision speeds below this threshold will not cause a bounce. Do not use this method while the simulation is running.</summary>
/// <summary>Function that lets you set debug visualization parameters. Returns false if the value passed is out of range for usage specified by the enum. Do not use this method while the simulation is running. False if the parameter is out of range.</summary>
/// <summary>Defines a box in world space to which visualization geometry will be (conservatively) culled. Use a non-empty culling box to enable the feature, and an empty culling box to disable it. Do not use this method while the simulation is running.</summary>
/// <summary>Retrieves the render buffer. This will contain the results of any active visualization for this scene. Do not use this method while the simulation is running. Calls to this method while the simulation is running will result in undefined behaviour. The render buffer.</summary>
/// <summary>Call this method to retrieve statistics for the current simulation step. Do not use this method while the simulation is running. Calls to this method while the simulation is running will be ignored.</summary>
/// <summary>Adds a new broad-phase region. The bounds for the new region must be non-empty, otherwise an error occurs and the call is ignored. Note that by default, objects already existing in the SDK that might touch this region will not be automatically added to the region. In other words the newly created region will be empty, and will only be populated with new objects when they are added to the simulation, or with already existing objects when they are updated. It is nonetheless possible to override this default behavior and let the SDK populate the new region automatically with already existing objects overlapping the incoming region. This has a cost though, and it should only be used when the game can not guarantee that all objects within the new region will be added to the simulation after the region itself. Objects automatically move from one region to another during their lifetime. The system keeps tracks of what regions a given object is in. It is legal for an object to be in an arbitrary number of regions. However if an object leaves all regions, or is created outside of all regions, several things happen: - collisions get disabled for this object - if a PxBroadPhaseCallback object is provided, an \"out-of-bounds\" event is generated via that callback - if a PxBroadPhaseCallback object is not provided, a warning/error message is sent to the error stream If an object goes out-of-bounds and user deletes it during the same frame, neither the out-of-bounds event nor the error message is generated. Handle for newly created region, or 0xffffffff in case of failure.</summary>
/// <summary>Removes a new broad-phase region. If the region still contains objects, and if those objects do not overlap any region any more, they are not automatically removed from the simulation. Instead, the PxBroadPhaseCallback::onObjectOutOfBounds notification is used for each object. Users are responsible for removing the objects from the simulation if this is the desired behavior. If the handle is invalid, or if a valid handle is removed twice, an error message is sent to the error stream. True if success</summary>
/// <summary>Lock the scene for reading from the calling thread. When the PxSceneFlag::eREQUIRE_RW_LOCK flag is enabled lockRead() must be called before any read calls are made on the scene. Multiple threads may read at the same time, no threads may read while a thread is writing. If a call to lockRead() is made while another thread is holding a write lock then the calling thread will be blocked until the writing thread calls unlockWrite(). Lock upgrading is *not* supported, that means it is an error to call lockRead() followed by lockWrite(). Recursive locking is supported but each lockRead() call must be paired with an unlockRead().</summary>
/// <summary>Lock the scene for writing from this thread. When the PxSceneFlag::eREQUIRE_RW_LOCK flag is enabled lockWrite() must be called before any write calls are made on the scene. Only one thread may write at a time and no threads may read while a thread is writing. If a call to lockWrite() is made and there are other threads reading then the calling thread will be blocked until the readers complete. Writers have priority. If a thread is blocked waiting to write then subsequent calls to lockRead() from other threads will be blocked until the writer completes. If multiple threads are waiting to write then the thread that is first granted access depends on OS scheduling. Recursive locking is supported but each lockWrite() call must be paired with an unlockWrite(). If a thread has already locked the scene for writing then it may call lockRead().</summary>
/// <summary>set the cache blocks that can be used during simulate(). Each frame the simulation requires memory to store contact, friction, and contact cache data. This memory is used in blocks of 16K. Each frame the blocks used by the previous frame are freed, and may be retrieved by the application using PxScene::flushSimulation() This call will force allocation of cache blocks if the numBlocks parameter is greater than the currently allocated number of blocks, and less than the max16KContactDataBlocks parameter specified at scene creation time. Do not use this method while the simulation is running.</summary>
/// <summary>get the number of cache blocks currently used by the scene This function may not be called while the scene is simulating the number of cache blocks currently used by the scene</summary>
/// <summary>get the maximum number of cache blocks used by the scene This function may not be called while the scene is simulating the maximum number of cache blocks everused by the scene</summary>
/// <summary>Sets the number of actors required to spawn a separate rigid body solver thread. Do not use this method while the simulation is running.</summary>
/// <summary>Retrieves the number of actors required to spawn a separate rigid body solver thread. Current number of actors required to spawn a separate rigid body solver thread.</summary>
/// <summary>Sets the number of articulations required to spawn a separate rigid body solver thread. Do not use this method while the simulation is running.</summary>
/// <summary>Retrieves the number of articulations required to spawn a separate rigid body solver thread. Current number of articulations required to spawn a separate rigid body solver thread.</summary>
/// <summary>Shift the scene origin by the specified vector. The poses of all objects in the scene and the corresponding data structures will get adjusted to reflect the new origin location (the shift vector will get subtracted from all object positions). It is the user's responsibility to keep track of the summed total origin shift and adjust all input/output to/from PhysX accordingly. Do not use this method while the simulation is running. Calls to this method while the simulation is running will be ignored. Make sure to propagate the origin shift to other dependent modules (for example, the character controller module etc.). This is an expensive operation and we recommend to use it only in the case where distance related precision issues may arise in areas far from the origin.</summary>
/// <summary>Copy contact data from the internal GPU buffer to a user-provided device buffer. The contact data contains pointers to internal state and is only valid until the next call to simulate().</summary>
/// <summary>Compute dense Jacobian matrices for specified articulations on the GPU. The size of Jacobians can vary by articulation, since it depends on the number of links, degrees-of-freedom, and whether the base is fixed. The size is determined using these formulas: nCols = (fixedBase ? 0 : 6) + dofCount nRows = (fixedBase ? 0 : 6) + (linkCount - 1) * 6; The user must ensure that adequate space is provided for each Jacobian matrix.</summary>
/// <summary>Compute the joint-space inertia matrices that maps joint accelerations to joint forces: forces = M * accelerations on the GPU. The size of matrices can vary by articulation, since it depends on the number of links and degrees-of-freedom. The size is determined using this formula: sizeof(float) * dofCount * dofCount The user must ensure that adequate space is provided for each mass matrix.</summary>
/// <summary>Computes the joint DOF forces required to counteract gravitational forces for the given articulation pose. The size of the result can vary by articulation, since it depends on the number of links and degrees-of-freedom. The size is determined using this formula: sizeof(float) * dofCount The user must ensure that adequate space is provided for each articulation.</summary>
/// <summary>Computes the joint DOF forces required to counteract coriolis and centrifugal forces for the given articulation pose. The size of the result can vary by articulation, since it depends on the number of links and degrees-of-freedom. The size is determined using this formula: sizeof(float) * dofCount The user must ensure that adequate space is provided for each articulation.</summary>
/// <summary>Apply user-provided data to particle buffers. This function should be used if the particle buffer flags are already on the device. Otherwise, use PxParticleBuffer::raiseFlags() from the CPU. This assumes the data has been changed directly in the PxParticleBuffer.</summary>
/// <summary>Advances the iterator to next set of extra data items. The contact pair extra data stream contains sets of items as requested by the corresponding [`PxPairFlag`] flags [`PxPairFlag::ePRE_SOLVER_VELOCITY`], #PxPairFlag::ePOST_SOLVER_VELOCITY, #PxPairFlag::eCONTACT_EVENT_POSE. A set can contain one item of each plus the PxContactPairIndex item. This method parses the stream and points the iterator member variables to the corresponding items of the current set, if they are available. If CCD is not enabled, you should only get one set of items. If CCD with multiple passes is enabled, you might get more than one item set. Even though contact pair extra data is requested per shape pair, you will not get an item set per shape pair but one per actor pair. If, for example, an actor has two shapes and both collide with another actor, then there will only be one item set (since it applies to both shape pairs). True if there was another set of extra data items in the stream, else false.</summary>
/// <summary>Extracts the contact points from the stream and stores them in a convenient format. Number of contact points written to the buffer.</summary>
/// <summary>Helper method to clone the contact pair and copy the contact data stream into a user buffer. The contact data stream is only accessible during the contact report callback. This helper function provides copy functionality to buffer the contact stream information such that it can get accessed at a later stage.</summary>
/// <summary>This is called when a breakable constraint breaks. The user should not release the constraint shader inside this call! No event will get reported if the constraint breaks but gets deleted while the time step is still being simulated.</summary>
/// <summary>This is called with the actors which have just been woken up. Only supported by rigid bodies yet. Only called on actors for which the PxActorFlag eSEND_SLEEP_NOTIFIES has been set. Only the latest sleep state transition happening between fetchResults() of the previous frame and fetchResults() of the current frame will get reported. For example, let us assume actor A is awake, then A->putToSleep() gets called, then later A->wakeUp() gets called. At the next simulate/fetchResults() step only an onWake() event will get triggered because that was the last transition. If an actor gets newly added to a scene with properties such that it is awake and the sleep state does not get changed by the user or simulation, then an onWake() event will get sent at the next simulate/fetchResults() step.</summary>
/// <summary>This is called with the actors which have just been put to sleep. Only supported by rigid bodies yet. Only called on actors for which the PxActorFlag eSEND_SLEEP_NOTIFIES has been set. Only the latest sleep state transition happening between fetchResults() of the previous frame and fetchResults() of the current frame will get reported. For example, let us assume actor A is asleep, then A->wakeUp() gets called, then later A->putToSleep() gets called. At the next simulate/fetchResults() step only an onSleep() event will get triggered because that was the last transition (assuming the simulation does not wake the actor up). If an actor gets newly added to a scene with properties such that it is asleep and the sleep state does not get changed by the user or simulation, then an onSleep() event will get sent at the next simulate/fetchResults() step.</summary>
/// <summary>This is called when certain contact events occur. The method will be called for a pair of actors if one of the colliding shape pairs requested contact notification. You request which events are reported using the filter shader/callback mechanism (see [`PxSimulationFilterShader`], [`PxSimulationFilterCallback`], #PxPairFlag). Do not keep references to the passed objects, as they will be invalid after this function returns.</summary>
/// <summary>This is called with the current trigger pair events. Shapes which have been marked as triggers using PxShapeFlag::eTRIGGER_SHAPE will send events according to the pair flag specification in the filter shader (see [`PxPairFlag`], #PxSimulationFilterShader). Trigger shapes will no longer send notification events for interactions with other trigger shapes.</summary>
/// <summary>Provides early access to the new pose of moving rigid bodies. When this call occurs, rigid bodies having the [`PxRigidBodyFlag::eENABLE_POSE_INTEGRATION_PREVIEW`] flag set, were moved by the simulation and their new poses can be accessed through the provided buffers. The provided buffers are valid and can be read until the next call to [`PxScene::simulate`]() or #PxScene::collide(). This callback gets triggered while the simulation is running. If the provided rigid body references are used to read properties of the object, then the callback has to guarantee no other thread is writing to the same body at the same time. The code in this callback should be lightweight as it can block the simulation, that is, the [`PxScene::fetchResults`]() call.</summary>
/// <summary>Retrieve rigid actors in the pruning structure. You can retrieve the number of rigid actor pointers by calling [`getNbRigidActors`]() Number of rigid actor pointers written to the buffer.</summary>
/// <summary>Returns the number of rigid actors in the pruning structure. You can use [`getRigidActors`]() to retrieve the rigid actor pointers. Number of rigid actors in the pruning structure.</summary>
/// <summary>Gets the merge data for static actors This is mainly called by the PxSceneQuerySystem::merge() function to merge a PxPruningStructure with the internal data-structures of the scene-query system. Implementation-dependent merge data for static actors.</summary>
/// <summary>Gets the merge data for dynamic actors This is mainly called by the PxSceneQuerySystem::merge() function to merge a PxPruningStructure with the internal data-structures of the scene-query system. Implementation-dependent merge data for dynamic actors.</summary>
/// <summary>Called when current controller hits a shape. This is called when the CCT moves and hits a shape. This will not be called when a moving shape hits a non-moving CCT.</summary>
/// <summary>Sets controller's position. The position controlled by this function is the center of the collision shape. This is a 'teleport' function, it doesn't check for collisions. The character's position must be such that it does not overlap the static geometry. To move the character under normal conditions use the [`move`]() function. Currently always returns true.</summary>
/// <summary>Retrieve the raw position of the controller. The position retrieved by this function is the center of the collision shape. To retrieve the bottom position of the shape, a.k.a. the foot position, use the getFootPosition() function. The position is updated by calls to move(). Calling this method without calling move() will return the last position or the initial position of the controller. The controller's center position</summary>
/// <summary>Set controller's foot position. The position controlled by this function is the bottom of the collision shape, a.k.a. the foot position. The foot position takes the contact offset into account This is a 'teleport' function, it doesn't check for collisions. To move the character under normal conditions use the [`move`]() function. Currently always returns true.</summary>
/// <summary>Retrieve the \"foot\" position of the controller, i.e. the position of the bottom of the CCT's shape. The foot position takes the contact offset into account The controller's foot position</summary>
/// <summary>Get the rigid body actor associated with this controller (see PhysX documentation). The behavior upon manually altering this actor is undefined, you should primarily use it for reading const properties. the actor associated with the controller.</summary>
/// <summary>Sets the slope limit. This feature can not be enabled at runtime, i.e. if the slope limit is zero when creating the CCT (which disables the feature) then changing the slope limit at runtime will not have any effect, and the call will be ignored.</summary>
/// <summary>Flushes internal geometry cache. The character controller uses caching in order to speed up collision testing. The cache is automatically flushed when a change to static objects is detected in the scene. For example when a static shape is added, updated, or removed from the scene, the cache is automatically invalidated. However there may be situations that cannot be automatically detected, and those require manual invalidation of the cache. Currently the user must call this when the filtering behavior changes (the PxControllerFilters parameter of the PxController::move call). While the controller in principle could detect a change in these parameters, it cannot detect a change in the behavior of the filtering function.</summary>
/// <summary>Resizes the controller. This function attempts to resize the controller to a given size, while making sure the bottom position of the controller remains constant. In other words the function modifies both the height and the (center) position of the controller. This is a helper function that can be used to implement a 'crouch' functionality for example.</summary>
/// <summary>Retrieve behavior flags for a shape. When the CCT touches a shape, the CCT's behavior w.r.t. this shape can be customized by users. This function retrieves the desired PxControllerBehaviorFlag flags capturing the desired behavior. See comments about deprecated functions at the start of this class Desired behavior flags for the given shape</summary>
/// <summary>Retrieve behavior flags for a controller. When the CCT touches a controller, the CCT's behavior w.r.t. this controller can be customized by users. This function retrieves the desired PxControllerBehaviorFlag flags capturing the desired behavior. The flag PxControllerBehaviorFlag::eCCT_CAN_RIDE_ON_OBJECT is not supported. See comments about deprecated functions at the start of this class Desired behavior flags for the given controller</summary>
/// <summary>Retrieve behavior flags for an obstacle. When the CCT touches an obstacle, the CCT's behavior w.r.t. this obstacle can be customized by users. This function retrieves the desired PxControllerBehaviorFlag flags capturing the desired behavior. See comments about deprecated functions at the start of this class Desired behavior flags for the given obstacle</summary>
/// <summary>Releases the controller manager. This will release all associated controllers and obstacle contexts. This function is required to be called to release foundation usage.</summary>
/// <summary>Computes character-character interactions. This function is an optional helper to properly resolve interactions between characters, in case they overlap (which can happen for gameplay reasons, etc). You should call this once per frame, before your PxController::move() calls. The function will not move the characters directly, but it will compute overlap information for each character that will be used in the next move() call. You need to provide a proper time value here so that interactions are resolved in a way that do not depend on the framerate. If you only have one character in the scene, or if you can guarantee your characters will never overlap, then you do not need to call this function. Releasing the manager will automatically release all the associated obstacle contexts.</summary>
/// <summary>Enables or disables runtime tessellation. Large triangles can create accuracy issues in the sweep code, which in turn can lead to characters not sliding smoothly against geometries, or even penetrating them. This feature allows one to reduce those issues by tessellating large triangles at runtime, before performing sweeps against them. The amount of tessellation is controlled by the 'maxEdgeLength' parameter. Any triangle with at least one edge length greater than the maxEdgeLength will get recursively tessellated, until resulting triangles are small enough. This features only applies to triangle meshes, convex meshes, heightfields and boxes.</summary>
/// <summary>Enables or disables the overlap recovery module. The overlap recovery module can be used to depenetrate CCTs from static objects when an overlap is detected. This can happen in three main cases: - when the CCT is directly spawned or teleported in another object - when the CCT algorithm fails due to limited FPU accuracy - when the \"up vector\" is modified, making the rotated CCT shape overlap surrounding objects When activated, the CCT module will automatically try to resolve the penetration, and move the CCT to a safe place where it does not overlap other objects anymore. This only concerns static objects, dynamic objects are ignored by the recovery module. When the recovery module is not activated, it is possible for the CCTs to go through static objects. By default, the recovery module is enabled. The recovery module currently works with all geometries except heightfields.</summary>
/// <summary>Enables or disables the precise sweeps. Precise sweeps are more accurate, but also potentially slower than regular sweeps. By default, precise sweeps are enabled.</summary>
/// <summary>Enables or disables vertical sliding against ceilings. Geometry is seen as \"ceilings\" when the following condition is met: dot product(contact normal, up direction) < 0.0f This flag controls whether characters should slide vertically along the geometry in that case. By default, sliding is allowed.</summary>
/// <summary>Shift the origin of the character controllers and obstacle objects by the specified vector. The positions of all character controllers, obstacle objects and the corresponding data structures will get adjusted to reflect the shifted origin location (the shift vector will get subtracted from all character controller and obstacle object positions). It is the user's responsibility to keep track of the summed total origin shift and adjust all input/output to/from PhysXCharacterKinematic accordingly. This call will not automatically shift the PhysX scene and its objects. You need to call PxScene::shiftOrigin() seperately to keep the systems in sync.</summary>
/// <summary>Creates the controller manager. The character controller is informed by [`PxDeletionListener::onRelease`]() when actors or shapes are released, and updates its internal caches accordingly. If character controller movement or a call to [`PxControllerManager::shiftOrigin`]() may overlap with actor/shape releases, internal data structures must be guarded against concurrent access. Locking guarantees thread safety in such scenarios. locking may result in significant slowdown for release of actors or shapes. By default, locking is disabled.</summary>
/// <summary>Cooks a bounding volume hierarchy. The results are written to the stream. PxCookBVH() allows a BVH description to be cooked into a binary stream suitable for loading and performing BVH detection at runtime. true on success.</summary>
/// <summary>Cooks and creates a bounding volume hierarchy without going through a stream. This method does the same as cookBVH, but the produced BVH is not stored into a stream but is either directly inserted in PxPhysics, or created as a standalone object. Use this method if you are unable to cook offline. PxInsertionCallback can be obtained through PxPhysics::getPhysicsInsertionCallback() or PxCooking::getStandaloneInsertionCallback(). PxBVH pointer on success</summary>
/// <summary>Cooks a heightfield. The results are written to the stream. To create a heightfield object there is an option to precompute some of calculations done while loading the heightfield data. cookHeightField() allows a heightfield description to be cooked into a binary stream suitable for loading and performing collision detection at runtime. true on success</summary>
/// <summary>Cooks a convex mesh. The results are written to the stream. To create a triangle mesh object it is necessary to first 'cook' the mesh data into a form which allows the SDK to perform efficient collision detection. cookConvexMesh() allows a mesh description to be cooked into a binary stream suitable for loading and performing collision detection at runtime. The number of vertices and the number of convex polygons in a cooked convex mesh is limited to 255. If those limits are exceeded in either the user-provided data or the final cooked mesh, an error is reported. true on success.</summary>
/// <summary>Cooks and creates a convex mesh without going through a stream. This method does the same as cookConvexMesh, but the produced mesh is not stored into a stream but is either directly inserted in PxPhysics, or created as a standalone object. Use this method if you are unable to cook offline. PxInsertionCallback can be obtained through PxPhysics::getPhysicsInsertionCallback() or PxCooking::getStandaloneInsertionCallback(). PxConvexMesh pointer on success</summary>
/// <summary>Verifies if the convex mesh is valid. Prints an error message for each inconsistency found. The convex mesh descriptor must contain an already created convex mesh - the vertices, indices and polygons must be provided. This function should be used if PxConvexFlag::eDISABLE_MESH_VALIDATION is planned to be used in release builds. true if all the validity conditions hold, false otherwise.</summary>
/// <summary>Computed hull polygons from given vertices and triangles. Polygons are needed for PxConvexMeshDesc rather than triangles. Please note that the resulting polygons may have different number of vertices. Some vertices may be removed. The output vertices, indices and polygons must be used to construct a hull. The provided PxAllocatorCallback does allocate the out array's. It is the user responsibility to deallocated those array's. true on success</summary>
/// <summary>Verifies if the triangle mesh is valid. Prints an error message for each inconsistency found. The following conditions are true for a valid triangle mesh: 1. There are no duplicate vertices (within specified vertexWeldTolerance. See PxCookingParams::meshWeldTolerance) 2. There are no large triangles (within specified PxTolerancesScale.) true if all the validity conditions hold, false otherwise.</summary>
/// <summary>Cooks and creates a triangle mesh without going through a stream. This method does the same as cookTriangleMesh, but the produced mesh is not stored into a stream but is either directly inserted in PxPhysics, or created as a standalone object. Use this method if you are unable to cook offline. PxInsertionCallback can be obtained through PxPhysics::getPhysicsInsertionCallback() or PxCooking::getStandaloneInsertionCallback(). PxTriangleMesh pointer on success.</summary>
/// <summary>Cooks a triangle mesh. The results are written to the stream. To create a triangle mesh object it is necessary to first 'cook' the mesh data into a form which allows the SDK to perform efficient collision detection. PxCookTriangleMesh() allows a mesh description to be cooked into a binary stream suitable for loading and performing collision detection at runtime. true on success</summary>
/// <summary>get the relative linear velocity of the joint This function returns the linear velocity of the origin of the constraint frame of actor1, relative to the origin of the constraint frame of actor0. The value is returned in the constraint frame of actor0</summary>
/// <summary>get the relative angular velocity of the joint This function returns the angular velocity of actor1 relative to actor0. The value is returned in the constraint frame of actor0</summary>
/// <summary>set the break force for this joint. if the constraint force or torque on the joint exceeds the specified values, the joint will break, at which point it will not constrain the two actors and the flag PxConstraintFlag::eBROKEN will be set. The force and torque are measured in the joint frame of the first actor</summary>
/// <summary>Retrieves the PxConstraint corresponding to this joint. This can be used to determine, among other things, the force applied at the joint. the constraint</summary>
/// <summary>Sets a name string for the object that can be retrieved with getName(). This is for debugging and is not used by the SDK. The string is not copied by the SDK, only the pointer is stored.</summary>
/// <summary>Helper function to setup a joint's global frame This replaces the following functions from previous SDK versions: void NxJointDesc::setGlobalAnchor(const NxVec3 & wsAnchor); void NxJointDesc::setGlobalAxis(const NxVec3 & wsAxis); The function sets the joint's localPose using world-space input parameters.</summary>
/// <summary>Set the allowed minimum distance for the joint. The minimum distance must be no more than the maximum distance Default 0.0f Range [0, PX_MAX_F32)</summary>
/// <summary>Set the allowed maximum distance for the joint. The maximum distance must be no less than the minimum distance. Default 0.0f Range [0, PX_MAX_F32)</summary>
/// <summary>Get the error tolerance of the joint. the distance beyond the joint's [min, max] range before the joint becomes active. Default 0.25f * PxTolerancesScale::length Range (0, PX_MAX_F32) This value should be used to ensure that if the minimum distance is zero and the spring function is in use, the rest length of the spring is non-zero.</summary>
/// <summary>Set the strength of the joint spring. The spring is used if enabled, and the distance exceeds the range [min-error, max+error]. Default 0.0f Range [0, PX_MAX_F32)</summary>
/// <summary>Set the damping of the joint spring. The spring is used if enabled, and the distance exceeds the range [min-error, max+error]. Default 0.0f Range [0, PX_MAX_F32)</summary>
/// <summary>Set the contact distance for the min & max distance limits. This is similar to the PxJointLimitParameters::contactDistance parameter for regular limits. The two most common values are 0 and infinite. Infinite means the internal constraints are always created, resulting in the best simulation quality but slower performance. Zero means the internal constraints are only created when the limits are violated, resulting in best performance but worse simulation quality. Default 0.0f Range [0, PX_MAX_F32)</summary>
/// <summary>sets the joint limit parameters. The limit range is [-PX_MAX_F32, PX_MAX_F32], but note that the width of the limit (upper-lower) must also be a valid float.</summary>
/// <summary>set the joint limit parameters. The limit is activated using the flag PxRevoluteJointFlag::eLIMIT_ENABLED The limit angle range is (-2*Pi, 2*Pi).</summary>
/// <summary>set the target velocity for the drive model. The motor will only be able to reach this velocity if the maxForce is sufficiently large. If the joint is spinning faster than this velocity, the motor will actually try to brake (see PxRevoluteJointFlag::eDRIVE_FREESPIN.) The sign of this variable determines the rotation direction, with positive values going the same way as positive joint angles. Setting a very large target velocity may cause undesirable results. Range: (-PX_MAX_F32, PX_MAX_F32) Default: 0.0</summary>
/// <summary>sets the maximum torque the drive can exert. The value set here may be used either as an impulse limit or a force limit, depending on the flag PxConstraintFlag::eDRIVE_LIMITS_ARE_FORCES Range: [0, PX_MAX_F32) Default: PX_MAX_F32</summary>
/// <summary>sets the gear ratio for the drive. When setting up the drive constraint, the velocity of the first actor is scaled by this value, and its response to drive torque is scaled down. So if the drive target velocity is zero, the second actor will be driven to the velocity of the first scaled by the gear ratio Range: [0, PX_MAX_F32) Default: 1.0</summary>
/// <summary>Set the limit cone. If enabled, the limit cone will constrain the angular movement of the joint to lie within an elliptical cone. the limit cone</summary>
/// <summary>Set the motion type around the specified axis. Each axis may independently specify that the degree of freedom is locked (blocking relative movement along or around this axis), limited by the corresponding limit, or free. Default: all degrees of freedom are locked</summary>
/// <summary>Set the distance limit for the joint. A single limit constraints all linear limited degrees of freedom, forming a linear, circular or spherical constraint on motion depending on the number of limited degrees. This is similar to a distance limit.</summary>
/// <summary>Set the linear limit for a given linear axis. This function extends the previous setDistanceLimit call with the following features: - there can be a different limit for each linear axis - each limit is defined by two values, i.e. it can now be asymmetric This can be used to create prismatic joints similar to PxPrismaticJoint, or point-in-quad joints, or point-in-box joints.</summary>
/// <summary>Set the twist limit for the joint. The twist limit controls the range of motion around the twist axis. The limit angle range is (-2*Pi, 2*Pi).</summary>
/// <summary>Set the swing cone limit for the joint. The cone limit is used if either or both swing axes are limited. The extents are symmetrical and measured in the frame of the parent. If only one swing degree of freedom is limited, the corresponding value from the cone limit defines the limit range.</summary>
/// <summary>Set a pyramidal swing limit for the joint. The pyramid limits will only be used in the following cases: - both swing Y and Z are limited. The limit shape is then a pyramid. - Y is limited and Z is locked, or vice versa. The limit shape is an asymmetric angular section, similar to what is supported for the twist axis. The remaining cases (Y limited and Z is free, or vice versa) are not supported.</summary>
/// <summary>Set the drive parameters for the specified drive type. Default The default drive spring and damping values are zero, the force limit is zero, and no flags are set.</summary>
/// <summary>Set the linear tolerance threshold for projection. Projection is enabled if PxConstraintFlag::ePROJECTION is set for the joint. If the joint separates by more than this distance along its locked degrees of freedom, the solver will move the bodies to close the distance. Setting a very small tolerance may result in simulation jitter or other artifacts. Sometimes it is not possible to project (for example when the joints form a cycle). Range: [0, PX_MAX_F32) Default: 1e10f</summary>
/// <summary>Set the angular tolerance threshold for projection. Projection is enabled if PxConstraintFlag::ePROJECTION is set for the joint. If the joint deviates by more than this angle around its locked angular degrees of freedom, the solver will move the bodies to close the angle. Setting a very small tolerance may result in simulation jitter or other artifacts. Sometimes it is not possible to project (for example when the joints form a cycle). Range: [0,Pi] Default: Pi Angular projection is implemented only for the case of two or three locked angular degrees of freedom.</summary>
/// <summary>Set the hinge/revolute joints connected by the gear joint. The passed joints can be either PxRevoluteJoint, PxD6Joint or PxArticulationJointReducedCoordinate. The joints must define degrees of freedom around the twist axis. They cannot be null. Note that these joints are only used to compute the positional error correction term, used to adjust potential drift between jointed actors. The gear joint can run without calling this function, but in that case some visible overlap may develop over time between the teeth of the gear meshes. Calling this function resets the internal positional error correction term. true if success</summary>
/// <summary>Set the desired gear ratio. For two gears with n0 and n1 teeth respectively, the gear ratio is n0/n1. You may need to use a negative gear ratio if the joint frames of involved actors are not oriented in the same direction. Calling this function resets the internal positional error correction term.</summary>
/// <summary>Set the hinge & prismatic joints connected by the rack & pinion joint. The passed hinge joint can be either PxRevoluteJoint, PxD6Joint or PxArticulationJointReducedCoordinate. It cannot be null. The passed prismatic joint can be either PxPrismaticJoint or PxD6Joint. It cannot be null. Note that these joints are only used to compute the positional error correction term, used to adjust potential drift between jointed actors. The rack & pinion joint can run without calling this function, but in that case some visible overlap may develop over time between the teeth of the rack & pinion meshes. Calling this function resets the internal positional error correction term. true if success</summary>
/// <summary>Set the desired ratio directly. You may need to use a negative gear ratio if the joint frames of involved actors are not oriented in the same direction. Calling this function resets the internal positional error correction term.</summary>
/// <summary>Set the desired ratio indirectly. This is a simple helper function that computes the ratio from passed data: ratio = (PI*2*nbRackTeeth)/(rackLength*nbPinionTeeth) Calling this function resets the internal positional error correction term. true if success</summary>
/// <summary>Implementation of a simple filter shader that emulates PhysX 2.8.x filtering This shader provides the following logic: If one of the two filter objects is a trigger, the pair is acccepted and [`PxPairFlag::eTRIGGER_DEFAULT`] will be used for trigger reports Else, if the filter mask logic (see further below) discards the pair it will be suppressed ([`PxFilterFlag::eSUPPRESS`]) Else, the pair gets accepted and collision response gets enabled ([`PxPairFlag::eCONTACT_DEFAULT`]) Filter mask logic: Given the two [`PxFilterData`] structures fd0 and fd1 of two collision objects, the pair passes the filter if the following conditions are met: 1) Collision groups of the pair are enabled 2) Collision filtering equation is satisfied</summary>
/// <summary>Determines if collision detection is performed between a pair of groups Collision group is an integer between 0 and 31. True if the groups could collide</summary>
/// <summary>Retrieves the value set with PxSetGroup() Collision group is an integer between 0 and 31. The collision group this actor belongs to</summary>
/// <summary>Creates a new shape with default properties and a list of materials and adds it to the list of shapes of this actor. This is equivalent to the following ```cpp // reference count is 1 PxShape* shape(...) = PxGetPhysics().createShape(...); // increments reference count actor->attachShape(shape); // releases user reference, leaving reference count at 1 shape->release(); ``` As a consequence, detachShape() will result in the release of the last reference, and the shape will be deleted. The default shape flags to be set are: eVISUALIZATION, eSIMULATION_SHAPE, eSCENE_QUERY_SHAPE (see [`PxShapeFlag`]). Triangle mesh, heightfield or plane geometry shapes configured as eSIMULATION_SHAPE are not supported for non-kinematic PxRigidDynamic instances. Creating compounds with a very large number of shapes may adversely affect performance and stability. Sleeping: Does NOT wake the actor up automatically. The newly created shape.</summary>
/// <summary>Creates a new shape with default properties and a single material adds it to the list of shapes of this actor. This is equivalent to the following ```cpp // reference count is 1 PxShape* shape(...) = PxGetPhysics().createShape(...); // increments reference count actor->attachShape(shape); // releases user reference, leaving reference count at 1 shape->release(); ``` As a consequence, detachShape() will result in the release of the last reference, and the shape will be deleted. The default shape flags to be set are: eVISUALIZATION, eSIMULATION_SHAPE, eSCENE_QUERY_SHAPE (see [`PxShapeFlag`]). Triangle mesh, heightfield or plane geometry shapes configured as eSIMULATION_SHAPE are not supported for non-kinematic PxRigidDynamic instances. Creating compounds with a very large number of shapes may adversely affect performance and stability. Sleeping: Does NOT wake the actor up automatically. The newly created shape.</summary>
/// <summary>Gets a list of bounds based on shapes in rigid actor. This list can be used to cook/create bounding volume hierarchy though PxCooking API.</summary>
/// <summary>Convenience function to create a PxBVH object from a PxRigidActor. The computed PxBVH can then be used in PxScene::addActor() or PxAggregate::addActor(). After adding the actor & BVH to the scene/aggregate, release the PxBVH object by calling PxBVH::release(). The PxBVH for this actor.</summary>
/// <summary>Compute mass properties based on a provided geometry structure. This constructor assumes the geometry has a density of 1. Mass and inertia tensor scale linearly with density.</summary>
/// <summary>Get the entries of the diagonalized inertia tensor and the corresponding reference rotation. The entries of the diagonalized inertia tensor.</summary>
/// <summary>Computation of mass properties for a rigid body actor To simulate a dynamic rigid actor, the SDK needs a mass and an inertia tensor. This method offers functionality to compute the necessary mass and inertia properties based on the shapes declared in the PxRigidBody descriptor and some additionally specified parameters. For each shape, the shape geometry, the shape positioning within the actor and the specified shape density are used to compute the body's mass and inertia properties. Shapes without PxShapeFlag::eSIMULATION_SHAPE set are ignored unless includeNonSimShapes is true. Shapes with plane, triangle mesh or heightfield geometry and PxShapeFlag::eSIMULATION_SHAPE set are not allowed for PxRigidBody collision. This method will set the mass, center of mass, and inertia tensor if no collision shapes are found, the inertia tensor is set to (1,1,1) and the mass to 1 if massLocalPose is non-NULL, the rigid body's center of mass parameter will be set to the user provided value (massLocalPose) and the inertia tensor will be resolved at that point. If all shapes of the actor have the same density then the overloaded method updateMassAndInertia() with a single density parameter can be used instead. Boolean. True on success else false.</summary>
/// <summary>Computation of mass properties for a rigid body actor This method sets the mass, inertia and center of mass of a rigid body. The mass is set to the sum of all user-supplied shape mass values, and the inertia and center of mass are computed according to the rigid body's shapes and the per shape mass input values. If no collision shapes are found, the inertia tensor is set to (1,1,1) If a single mass value should be used for the actor as a whole then the overloaded method setMassAndUpdateInertia() with a single mass parameter can be used instead. Boolean. True on success else false.</summary>
/// <summary>Computation of mass properties for a rigid body actor This method sets the mass, inertia and center of mass of a rigid body. The mass is set to the user-supplied value, and the inertia and center of mass are computed according to the rigid body's shapes and the input mass. If no collision shapes are found, the inertia tensor is set to (1,1,1) Boolean. True on success else false.</summary>
/// <summary>Applies a force (or impulse) defined in the global coordinate frame, acting at a particular point in global coordinates, to the actor. Note that if the force does not act along the center of mass of the actor, this will also add the corresponding torque. Because forces are reset at the end of every timestep, you can maintain a total external force on an object by calling this once every frame. if this call is used to apply a force or impulse to an articulation link, only the link is updated, not the entire articulation ::PxForceMode determines if the force is to be conventional or impulsive. Only eFORCE and eIMPULSE are supported, as the force required to produce a given velocity change or acceleration is underdetermined given only the desired change at a given point. Sleeping: This call wakes the actor if it is sleeping and the wakeup parameter is true (default).</summary>
/// <summary>Applies a force (or impulse) defined in the global coordinate frame, acting at a particular point in local coordinates, to the actor. Note that if the force does not act along the center of mass of the actor, this will also add the corresponding torque. Because forces are reset at the end of every timestep, you can maintain a total external force on an object by calling this once every frame. if this call is used to apply a force or impulse to an articulation link, only the link is updated, not the entire articulation ::PxForceMode determines if the force is to be conventional or impulsive. Only eFORCE and eIMPULSE are supported, as the force required to produce a given velocity change or acceleration is underdetermined given only the desired change at a given point. Sleeping: This call wakes the actor if it is sleeping and the wakeup parameter is true (default).</summary>
/// <summary>Applies a force (or impulse) defined in the actor local coordinate frame, acting at a particular point in global coordinates, to the actor. Note that if the force does not act along the center of mass of the actor, this will also add the corresponding torque. Because forces are reset at the end of every timestep, you can maintain a total external force on an object by calling this once every frame. if this call is used to apply a force or impulse to an articulation link, only the link is updated, not the entire articulation ::PxForceMode determines if the force is to be conventional or impulsive. Only eFORCE and eIMPULSE are supported, as the force required to produce a given velocity change or acceleration is underdetermined given only the desired change at a given point. Sleeping: This call wakes the actor if it is sleeping and the wakeup parameter is true (default).</summary>
/// <summary>Applies a force (or impulse) defined in the actor local coordinate frame, acting at a particular point in local coordinates, to the actor. Note that if the force does not act along the center of mass of the actor, this will also add the corresponding torque. Because forces are reset at the end of every timestep, you can maintain a total external force on an object by calling this once every frame. if this call is used to apply a force or impulse to an articulation link, only the link is updated, not the entire articulation ::PxForceMode determines if the force is to be conventional or impulsive. Only eFORCE and eIMPULSE are supported, as the force required to produce a given velocity change or acceleration is underdetermined given only the desired change at a given point. Sleeping: This call wakes the actor if it is sleeping and the wakeup parameter is true (default).</summary>
/// <summary>Computes the velocity of a point given in world coordinates if it were attached to the specified body and moving with it. The velocity of point in the global frame.</summary>
/// <summary>Computes the velocity of a point given in local coordinates if it were attached to the specified body and moving with it. The velocity of point in the local frame.</summary>
/// <summary>Computes the velocity of a point (offset from the origin of the body) given in world coordinates if it were attached to the specified body and moving with it. The velocity of point (offset from the origin of the body) in the global frame.</summary>
/// <summary>Compute the change to linear and angular velocity that would occur if an impulsive force and torque were to be applied to a specified rigid body. The rigid body is left unaffected unless a subsequent independent call is executed that actually applies the computed changes to velocity and angular velocity. if this call is used to determine the velocity delta for an articulation link, only the mass properties of the link are taken into account.</summary>
/// <summary>Computes the linear and angular velocity change vectors for a given impulse at a world space position taking a mass and inertia scale into account This function is useful for extracting the respective linear and angular velocity changes from a contact or joint when the mass/inertia ratios have been adjusted. if this call is used to determine the velocity delta for an articulation link, only the mass properties of the link are taken into account.</summary>
/// <summary>Computes the linear and angular impulse vectors for a given impulse at a world space position taking a mass and inertia scale into account This function is useful for extracting the respective linear and angular impulses from a contact or joint when the mass/inertia ratios have been adjusted.</summary>
/// <summary>Performs a linear sweep through space with the body's geometry objects. Supported geometries are: box, sphere, capsule, convex. Other geometry types will be ignored. If eTOUCH is returned from the filter callback, it will trigger an error and the hit will be discarded. The function sweeps all shapes attached to a given rigid body through space and reports the nearest object in the scene which intersects any of of the shapes swept paths. Information about the closest intersection is written to a [`PxSweepHit`] structure. True if a blocking hit was found.</summary>
/// <summary>Performs a linear sweep through space with the body's geometry objects, returning all overlaps. Supported geometries are: box, sphere, capsule, convex. Other geometry types will be ignored. This function sweeps all shapes attached to a given rigid body through space and reports all objects in the scene that intersect any of the shapes' swept paths until there are no more objects to report or a blocking hit is encountered. the number of touching hits. If overflow is set to true, the results are incomplete. In case of overflow there are also no guarantees that all touching hits returned are closer than the blocking hit.</summary>
/// <summary>Sweep a geometry object against the shape. Currently only box, sphere, capsule and convex mesh shapes are supported, i.e. the swept geometry object must be one of those types. True if the swept geometry object hits the shape</summary>
/// <summary>Find the mesh triangles which touch the specified geometry object. Number of overlaps found. Triangle indices can then be accessed through the [`getResults`]() function.</summary>
/// <summary>Find the height field triangles which touch the specified geometry object. Number of overlaps found. Triangle indices can then be accessed through the [`getResults`]() function.</summary>
/// <summary>Computes an approximate minimum translational distance (MTD) between a geometry object and a mesh. This iterative function computes an approximate vector that can be used to depenetrate a geom object from a triangle mesh. Returned depenetration vector should be applied to 'geom', to get out of the mesh. The function works best when the amount of overlap between the geom object and the mesh is small. If the geom object's center goes inside the mesh, backface culling usually kicks in, no overlap is detected, and the function does not compute an MTD vector. The function early exits if no overlap is detected after a depenetration attempt. This means that if maxIter = N, the code will attempt at most N iterations but it might exit earlier if depenetration has been successful. Usually N = 4 gives good results. True if the MTD has successfully been computed, i.e. if objects do overlap.</summary>
/// <summary>Computes an approximate minimum translational distance (MTD) between a geometry object and a heightfield. This iterative function computes an approximate vector that can be used to depenetrate a geom object from a heightfield. Returned depenetration vector should be applied to 'geom', to get out of the heightfield. The function works best when the amount of overlap between the geom object and the mesh is small. If the geom object's center goes inside the heightfield, backface culling usually kicks in, no overlap is detected, and the function does not compute an MTD vector. The function early exits if no overlap is detected after a depenetration attempt. This means that if maxIter = N, the code will attempt at most N iterations but it might exit earlier if depenetration has been successful. Usually N = 4 gives good results. True if the MTD has successfully been computed, i.e. if objects do overlap.</summary>
/// <summary>Returns whether the collection is serializable with the externalReferences collection. Some definitions to explain whether a collection can be serialized or not: For definitions of requires and complete see [`PxSerialization::complete`] A serializable object is subordinate if it cannot be serialized on its own The following objects are subordinate: - articulation links - articulation joints - joints A collection C can be serialized with external references collection D iff - C is complete relative to D (no dangling references) - Every object in D required by an object in C has a valid ID (no unnamed references) - Every subordinate object in C is required by another object in C (no orphans) Whether the collection is serializable</summary>
/// <summary>Adds to a collection all objects such that it can be successfully serialized. A collection C is complete relative to an other collection D if every object required by C is either in C or D. This function adds objects to a collection, such that it becomes complete with respect to the exceptFor collection. Completeness is needed for serialization. See [`PxSerialization::serializeCollectionToBinary`], [`PxSerialization::serializeCollectionToXml`]. Sdk objects require other sdk object according to the following rules: - joints require their actors and constraint - rigid actors require their shapes - shapes require their material(s) and mesh (triangle mesh, convex mesh or height field), if any - articulations require their links and joints - aggregates require their actors If followJoints is specified another rule is added: - actors require their joints Specifying followJoints will make whole jointed actor chains being added to the collection. Following chains is interrupted whenever a object in exceptFor is encountered.</summary>
/// <summary>Creates PxSerialObjectId values for unnamed objects in a collection. Creates PxSerialObjectId names for unnamed objects in a collection starting at a base value and incrementing, skipping values that are already assigned to objects in the collection.</summary>
/// <summary>Deserializes a PxCollection from memory. Creates a collection from memory. If the collection has external dependencies another collection can be provided to resolve these. The memory block provided has to be 128 bytes aligned and contain a contiguous serialized collection as written by PxSerialization::serializeCollectionToBinary. The contained binary data needs to be compatible with the current binary format version which is defined by \"PX_PHYSICS_VERSION_MAJOR.PX_PHYSICS_VERSION_MINOR.PX_PHYSICS_VERSION_BUGFIX-PX_BINARY_SERIAL_VERSION\". For a list of compatible sdk releases refer to the documentation of PX_BINARY_SERIAL_VERSION.</summary>
/// <summary>Serializes a physics collection to an XML output stream. The collection to be serialized needs to be complete Serialization of objects in a scene that is simultaneously being simulated is not supported and leads to undefined behavior. true if the collection is successfully serialized.</summary>
/// <summary>Serializes a collection to a binary stream. Serializes a collection to a stream. In order to resolve external dependencies the externalReferences collection has to be provided. Optionally names of objects that where set for example with [`PxActor::setName`] are serialized along with the objects. The collection can be successfully serialized if isSerializable(collection) returns true. See [`isSerializable`]. The implementation of the output stream needs to fulfill the requirements on the memory block input taken by PxSerialization::createCollectionFromBinary. Serialization of objects in a scene that is simultaneously being simulated is not supported and leads to undefined behavior. Whether serialization was successful</summary>
/// <summary>Create default dispatcher, extensions SDK needs to be initialized first. numThreads may be zero in which case no worker thread are initialized and simulation tasks will be executed on the thread that calls PxScene::simulate() yieldProcessorCount must be greater than zero if eYIELD_PROCESSOR is the chosen mode and equal to zero for all other modes. eYIELD_THREAD and eYIELD_PROCESSOR modes will use compute resources even if the simulation is not running. It is left to users to keep threads inactive, if so desired, when no simulation is running.</summary>
/// <summary>Builds smooth vertex normals over a mesh. - \"smooth\" because smoothing groups are not supported here - takes angles into account for correct cube normals computation To use 32bit indices pass a pointer in dFaces and set wFaces to zero. Alternatively pass a pointer to wFaces and set dFaces to zero. True on success.</summary>
/// <summary>simple method to create a PxRigidDynamic actor with a single PxShape. a new dynamic actor with the PxRigidBodyFlag, or NULL if it could not be constructed</summary>
/// <summary>simple method to create a PxRigidDynamic actor with a single PxShape. a new dynamic actor with the PxRigidBodyFlag, or NULL if it could not be constructed</summary>
/// <summary>simple method to create a kinematic PxRigidDynamic actor with a single PxShape. unlike PxCreateDynamic, the geometry is not restricted to box, capsule, sphere or convex. However, kinematics of other geometry types may not participate in simulation collision and may be used only for triggers or scene queries of moving objects under animation control. In this case the density parameter will be ignored and the created shape will be set up as a scene query only shape (see [`PxShapeFlag::eSCENE_QUERY_SHAPE`]) a new dynamic actor with the PxRigidBodyFlag::eKINEMATIC set, or NULL if it could not be constructed</summary>
/// <summary>simple method to create a kinematic PxRigidDynamic actor with a single PxShape. unlike PxCreateDynamic, the geometry is not restricted to box, capsule, sphere or convex. However, kinematics of other geometry types may not participate in simulation collision and may be used only for triggers or scene queries of moving objects under animation control. In this case the density parameter will be ignored and the created shape will be set up as a scene query only shape (see [`PxShapeFlag::eSCENE_QUERY_SHAPE`]) a new dynamic actor with the PxRigidBodyFlag::eKINEMATIC set, or NULL if it could not be constructed</summary>
/// <summary>create a shape by copying attributes from another shape The function clones a PxShape. The following properties are copied: - geometry - flags - materials - actor-local pose - contact offset - rest offset - simulation filter data - query filter data - torsional patch radius - minimum torsional patch radius The following are not copied and retain their default values: - name - user data the newly-created rigid static</summary>
/// <summary>create a static body by copying attributes from another rigid actor The function clones a PxRigidDynamic or PxRigidStatic as a PxRigidStatic. A uniform scale is applied. The following properties are copied: - shapes - actor flags - owner client and client behavior bits - dominance group The following are not copied and retain their default values: - name - joints or observers - aggregate or scene membership - user data Transforms are not copied with bit-exact accuracy. the newly-created rigid static</summary>
/// <summary>create a dynamic body by copying attributes from an existing body The following properties are copied: - shapes - actor flags, rigidDynamic flags and rigidDynamic lock flags - mass, moment of inertia, and center of mass frame - linear and angular velocity - linear and angular damping - maximum linear velocity - maximum angular velocity - position and velocity solver iterations - maximum depenetration velocity - sleep threshold - contact report threshold - dominance group - owner client and client behavior bits - name pointer - kinematic target The following are not copied and retain their default values: - name - joints or observers - aggregate or scene membership - sleep timer - user data Transforms are not copied with bit-exact accuracy. the newly-created rigid static</summary>
/// <summary>scale a rigid actor by a uniform scale The geometry and relative positions of the actor are multiplied by the given scale value. If the actor is a rigid body or an articulation link and the scaleMassProps value is true, the mass properties are scaled assuming the density is constant: the center of mass is linearly scaled, the mass is multiplied by the cube of the scale, and the inertia tensor by the fifth power of the scale.</summary>
/// <summary>Creates regions for PxSceneDesc, from a global box. This helper simply subdivides the given global box into a 2D grid of smaller boxes. Each one of those smaller boxes is a region of interest for the broadphase. There are nbSubdiv*nbSubdiv regions in the 2D grid. The function does not subdivide along the given up axis. This is the simplest setup one can use with PxBroadPhaseType::eMBP. A more sophisticated setup would try to cover the game world with a non-uniform set of regions (i.e. not just a grid). number of regions written out to the 'regions' array</summary>
/// <summary>Raycast returning any blocking hit, not necessarily the closest. Returns whether any rigid actor is hit along the ray. Shooting a ray from within an object leads to different results depending on the shape type. Please check the details in article SceneQuery. User can ignore such objects by using one of the provided filter mechanisms. True if a blocking hit was found.</summary>
/// <summary>Raycast returning a single result. Returns the first rigid actor that is hit along the ray. Data for a blocking hit will be returned as specified by the outputFlags field. Touching hits will be ignored. Shooting a ray from within an object leads to different results depending on the shape type. Please check the details in article SceneQuery. User can ignore such objects by using one of the provided filter mechanisms. True if a blocking hit was found.</summary>
/// <summary>Raycast returning multiple results. Find all rigid actors that get hit along the ray. Each result contains data as specified by the outputFlags field. Touching hits are not ordered. Shooting a ray from within an object leads to different results depending on the shape type. Please check the details in article SceneQuery. User can ignore such objects by using one of the provided filter mechanisms. Number of hits in the buffer, or -1 if the buffer overflowed.</summary>
/// <summary>Sweep returning any blocking hit, not necessarily the closest. Returns whether any rigid actor is hit along the sweep path. If a shape from the scene is already overlapping with the query shape in its starting position, behavior is controlled by the PxSceneQueryFlag::eINITIAL_OVERLAP flag. True if a blocking hit was found.</summary>
/// <summary>Sweep returning a single result. Returns the first rigid actor that is hit along the ray. Data for a blocking hit will be returned as specified by the outputFlags field. Touching hits will be ignored. If a shape from the scene is already overlapping with the query shape in its starting position, behavior is controlled by the PxSceneQueryFlag::eINITIAL_OVERLAP flag. True if a blocking hit was found.</summary>
/// <summary>Sweep returning multiple results. Find all rigid actors that get hit along the sweep. Each result contains data as specified by the outputFlags field. Touching hits are not ordered. If a shape from the scene is already overlapping with the query shape in its starting position, behavior is controlled by the PxSceneQueryFlag::eINITIAL_OVERLAP flag. Number of hits in the buffer, or -1 if the buffer overflowed.</summary>
/// <summary>Test overlap between a geometry and objects in the scene. Filtering: Overlap tests do not distinguish between touching and blocking hit types. Both get written to the hit buffer. PxHitFlag::eMESH_MULTIPLE and PxHitFlag::eMESH_BOTH_SIDES have no effect in this case Number of hits in the buffer, or -1 if the buffer overflowed.</summary>
/// <summary>Test returning, for a given geometry, any overlapping object in the scene. Filtering: Overlap tests do not distinguish between touching and blocking hit types. Both trigger a hit. PxHitFlag::eMESH_MULTIPLE and PxHitFlag::eMESH_BOTH_SIDES have no effect in this case True if an overlap was found.</summary>
/// <summary>Performs a raycast against objects in the scene. Touching hits are not ordered. Shooting a ray from within an object leads to different results depending on the shape type. Please check the details in article SceneQuery. User can ignore such objects by using one of the provided filter mechanisms. This query call writes to a list associated with the query object and is NOT thread safe (for performance reasons there is no lock and overlapping writes from different threads may result in undefined behavior). Returns a PxRaycastBuffer pointer that will store the result of the query after execute() is completed. This will point either to an element of the buffer allocated on construction or to a user buffer passed to the constructor.</summary>
/// <summary>Performs a sweep test against objects in the scene. Touching hits are not ordered. If a shape from the scene is already overlapping with the query shape in its starting position, the hit is returned unless eASSUME_NO_INITIAL_OVERLAP was specified. This query call writes to a list associated with the query object and is NOT thread safe (for performance reasons there is no lock and overlapping writes from different threads may result in undefined behavior). Returns a PxSweepBuffer pointer that will store the result of the query after execute() is completed. This will point either to an element of the buffer allocated on construction or to a user buffer passed to the constructor.</summary>
/// <summary>Performs an overlap test of a given geometry against objects in the scene. Filtering: returning eBLOCK from user filter for overlap queries will cause a warning (see [`PxQueryHitType`]). eBLOCK should not be returned from user filters for overlap(). Doing so will result in undefined behavior, and a warning will be issued. If the PxQueryFlag::eNO_BLOCK flag is set, the eBLOCK will instead be automatically converted to an eTOUCH and the warning suppressed. This query call writes to a list associated with the query object and is NOT thread safe (for performance reasons there is no lock and overlapping writes from different threads may result in undefined behavior). Returns a PxOverlapBuffer pointer that will store the result of the query after execute() is completed. This will point either to an element of the buffer allocated on construction or to a user buffer passed to the constructor.</summary>
/// <summary>Create a PxBatchQueryExt without the need for pre-allocated result or touch buffers. Returns a PxBatchQueryExt instance. A NULL pointer will be returned if the subsequent allocations fail or if any of the arguments are illegal. In the event that a NULL pointer is returned a corresponding error will be issued to the error stream.</summary>
/// <summary>Create a PxBatchQueryExt with user-supplied result and touch buffers. Returns a PxBatchQueryExt instance. A NULL pointer will be returned if the subsequent allocations fail or if any of the arguments are illegal. In the event that a NULL pointer is returned a corresponding error will be issued to the error stream.</summary>
/// <summary>Creates an external scene query system. An external SQ system is the part of a PxScene that deals with scene queries (SQ). This is usually taken care of by an internal implementation inside PxScene, but it is also possible to re-route all SQ calls to an external implementation, potentially opening the door to some customizations in behavior and features for advanced users. The following external SQ system is an example of how an implementation would look like. It re-uses much of the same code as the internal version, but it could be re-implemented in a completely different way to match users' specific needs. An external SQ system instance</summary>
/// <summary>Adds a pruner to the system. The internal PhysX scene-query system uses two regular pruners (one for static shapes, one for dynamic shapes) and an optional compound pruner. Our custom scene query system supports an arbitrary number of regular pruners. This can be useful to reduce the load on each pruner, in particular during updates, when internal trees are rebuilt in the background. On the other hand this implementation simply iterates over all created pruners to perform queries, so their cost might increase if a large number of pruners is used. In any case this serves as an example of how the PxSceneQuerySystem API can be used to customize scene queries. A pruner index</summary>
/// <summary>Start custom build-steps for all pruners This function is used in combination with customBuildstep() and finishCustomBuildstep() to let users take control of the pruners' build-step & commit calls - basically the pruners' update functions. These functions should be used with the PxSceneQueryUpdateMode::eBUILD_DISABLED_COMMIT_DISABLED update mode, otherwise the build-steps will happen automatically in fetchResults. For N pruners it can be more efficient to use these custom build-step functions to perform the updates in parallel: - call startCustomBuildstep() first (one synchronous call) - for each pruner, call customBuildstep() (asynchronous calls from multiple threads) - once it is done, call finishCustomBuildstep() to finish the update (synchronous call) The multi-threaded update is more efficient here than what it is in PxScene, because the \"flushShapes()\" call is also multi-threaded (while it is not in PxScene). Note that users are responsible for locks here, and these calls should not overlap with other SQ calls. In particular one should not add new objects to the SQ system or perform queries while these calls are happening. The number of pruners in the system.</summary>
/// <summary>Gets a pruner index for an actor/shape. This user-defined function tells the system in which pruner a given actor/shape should go. The returned index must be valid, i.e. it must have been previously returned to users by PxCustomSceneQuerySystem::addPruner. A pruner index for this actor/shape.</summary>
/// <summary>Pruner filtering callback. This will be called for each query to validate whether it should process a given pruner. True to process the pruner, false to skip it entirely</summary>
/// <summary>Creates a custom scene query system. This is similar to PxCreateExternalSceneQuerySystem, except this function creates a PxCustomSceneQuerySystem object. It can be plugged to PxScene the same way, via PxSceneDesc::sceneQuerySystem. A custom SQ system instance</summary>
/// <summary>Computes closest polygon of the convex hull geometry for a given impact point and impact direction. When doing sweeps against a scene, one might want to delay the rather expensive computation of the hit face index for convexes until it is clear the information is really needed and then use this method to get the corresponding face index. Closest face index of the convex geometry.</summary>
/// <summary>Sets the sampling radius Returns true if the sampling was successful and false if there was a problem. Usually an internal overflow is the problem for very big meshes or very small sampling radii.</summary>
/// <summary>Returns the index of the tetrahedron that contains a point The index of the tetrahedon containing the point, -1 if not tetrahedron contains the opoint</summary>
/// <summary>Initialize the PhysXExtensions library. This should be called before calling any functions or methods in extensions which may require allocation. This function does not need to be called before creating a PxDefaultAllocator object.</summary>
/// <summary>Shut down the PhysXExtensions library. This function should be called to cleanly shut down the PhysXExtensions library before application exit. This function is required to be called to release foundation usage.</summary>
/// <summary>Convert from a descriptor to a live object. Must be an object of this Serializer type. The new live object. It can be an invalid object if the instantiation cannot take place.</summary>
/// <summary>Disconnects the SDK from the PhysX Visual Debugger application. If we are still connected, this will kill the entire debugger connection.</summary>
/// <summary>write bytes to the other endpoint of the connection. should lock before witre. If an error occurs this connection will assume to be dead.</summary>
