diff options
| author | sschirm <[email protected]> | 2017-02-27 16:40:12 +0100 |
|---|---|---|
| committer | sschirm <[email protected]> | 2017-03-01 18:04:26 +0100 |
| commit | 7840347c32755e94a807f978f1cbb558717ac8cf (patch) | |
| tree | 295cd3ca93a45f8fcc43cf3cbf3887c0e0c5526b /PhysX_3.4/release_notes.html | |
| parent | Pre-release comments marking end of beta. (diff) | |
| download | physx-3.4-7840347c32755e94a807f978f1cbb558717ac8cf.tar.xz physx-3.4-7840347c32755e94a807f978f1cbb558717ac8cf.zip | |
PhysX 3.4, APEX 1.4 final release @21757769v3.4.0-rc-2
Diffstat (limited to 'PhysX_3.4/release_notes.html')
| -rw-r--r-- | PhysX_3.4/release_notes.html | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/PhysX_3.4/release_notes.html b/PhysX_3.4/release_notes.html index abbf109b..3f4e79a7 100644 --- a/PhysX_3.4/release_notes.html +++ b/PhysX_3.4/release_notes.html @@ -31,7 +31,7 @@ <!-- -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> <h1 style="TEXT-ALIGN: center">Release Notes - NVIDIA<sup>®</sup> PhysX<sup>®</sup> SDK 3.4</h1> -<h2 style="TEXT-ALIGN: center">January 2017</h2> +<h2 style="TEXT-ALIGN: center">February 2017</h2> <h2>Supported Platforms</h2> <blockquote> @@ -211,6 +211,7 @@ <li>Calls to contact modification callbacks can be made from multiple threads simultaneously. Therefore, modification callbacks should must be thread-safe. </li> <li>Unified heightfield contact generation is now the default heightfield contact generation approach. This approach offers similar performance and behavior to contact generation with triangle meshes. Unified heightfields have no thickness because contact genreation operates on triangles so objects may tunnel if CCD is not enabled.</li> <li>When unified heightfield contact generation is in use, the bounds of heightfield shapes are no longer extruded by "thickness".</li> + <li>PxArticulationJoint::setTwistLimit and PxArticulationJoint::getTwistLimit were incorrectly documented with zLimit and yLimit in the wrong order. The behavior of both functions remains unchanged but now they are correctly documented with zLimit and yLimit in the correct order. This is simply a clarification of the existing function behavior.</li> </ul> <li>Removed:</li> <ul> |