Page 2 of 2
Another changes in PhysX SDK 3.x
Collision Detection
- Documentation of limits of PxShape counts has been added for affected platforms.
- Made kinematics interact better with CCD.
- Adding support for disabled contact response in CCD by respecting the dominance setting. In this case, CCD will emit events but will not alter the motion of the bodies.
- Fixed potential crash in eENABLE_PCM codepath.
Rigid Bodies
- Fixed bug in force based contact reports. An assert could occur when PxPairFlag::eNOTIFY_THRESHOLD_FORCE_PERSISTS was set and PxPairFlag::eNOTIFY_THRESHOLD_FORCE_FOUND was not set.
- Twist Limit range is documented for revolute and D6 joints, and validated.
- Reduced the number of SDK allocations when using CCD.
Scene Queries
- Raycasts against heighfields now return correct actual mesh index, which can be used for getTriangle().
- Fixed bug that caused scene queries to miss hits for static rigid bodies that got moved around (after having been added to the scene).
- Fixed rebuilding the dynamic structure properly when used for static rigid bodies.
- Fixed a rare crash in heightfield raycast code.
Some of the fixes in PhysX SDK 3.x
General
- Fixed a bug which caused actors to return wrong world bounds if the bounds minimum was above 10000 on any axis.
- Reporting allocation names can now be enabled or disabled (see PxFoundation::setReportAllocationNames). When enabled, some platforms allocate memory through ‘malloc’.
- eEXCEPTION_ON_STARTUP is removed from PxErrorCode and it is no longer needed.
- Added boilerplate.txt to the Tools folder. SpuShaderDump.exe and clang.exe require it.
- PxWindowsDelayLoadHook.h has been moved from Include/foundation/windows to Include/common/windows.
- PxScene::saveToDesc now reports the bounceThresholdVelocity value.
- Fixed a bug in PxDefaultSimulationFilterShader: the value of the second filter constant in the collision filtering equation was ignored and instead the value of the first filter constant was used.
- Fixed a crash bug in PCM collision.
Rigid Bodies
- Forces applied to bodies (with PxRigidBody::addForce) that go to sleep in the subsequent update now have their applied forces cleared when the body is set to sleep to avoid them being applied in a later update when the body is once more awake. This bug broke the rule that forces applied with PxRigidBody::addForce do not persist beyond the next scene update.
Cooking
- PxCookingParams constructor is now marked as deprecated. PxToleranceScale is needed for PxCookingParams in order to perform additional triangle check during cooking. This triangle check will trigger warning if too huge triangles are used. This check will ensure better simulation stability.
Character Controller
- PxControllerFilterCallback has been added, to make CCT-vs-CCT filtering more flexible.
- Fixed a bug where PxControllerBehaviorCallback was not called when a PxUserControllerHitReport was not defined.
- PxObstacle notifications has been added to handle touched obstacles.
- Touched PxObstacle has been replaced by touched ObstacleHandle.
- PxObstacleContext::getObstacleByHandle has been added.
- Touched actors scene is checked before ride on shape, to ensure valid touched shape.
- Touched shape scene query flag is checked before ride on shape, to ensure valid touched shape.
- Touched shape user CCT filtering is triggered before ride on shape, to ensure valid touched shape.
Vehicles
- Documented potential problem with PxVehicleWheelsDynData::getTireDrivableSurfaceType() and PxVehicleWheelsDynData::getTireDrivableSurfaceShape() whereby the pointer returned may reference a PxShape or PxMaterial that has been released in-between storing the pointer in PxVehicleUpdates and any subsequent query.
- PxVehicleWheelsSimData::disableWheel has been documented in more detail. PxVehicleWheelsSimData::enableWheel has been added.
- Fixed a bug where the denominator of the longitudinal slip calculation didn’t take into account the value of PxTolerancesScale::length. This will only have an impact if PxTolerancesScale::length != 1.0f.
- Fixed a bug where the engine torque would be incorrectly applied if PxTolerancesScale::length != 1.0f. This will only have an impact if PxTolerancesScale::length != 1.0f.
More information at: physxinfo