PhysX 3.4, APEX 1.4 patch release @24990349

3 files changed, 9 insertions, 10 deletions

diff --git a/PhysX_3.4/Documentation/PhysXGuide/_sources/Manual/Geometry.txt b/PhysX_3.4/Documentation/PhysXGuide/_sources/Manual/Geometry.txt
index 86af8322..dd5b5fce 100644
--- a/PhysX_3.4/Documentation/PhysXGuide/_sources/Manual/Geometry.txt
+++ b/PhysX_3.4/Documentation/PhysXGuide/_sources/Manual/Geometry.txt
@@ -381,7 +381,7 @@ Each sample consists of a 16 bit integer height value, two materials (for the tw
 The flag and materials refer to the cell below and to the right of the sample point, and indicate along which diagonal to split it into triangles, and the materials of those triangles.  A special predefined material ``PxHeightFieldMaterial::eHOLE`` specifies a hole in the height field. See the reference documentation for *PxHeightFieldSample* for more details.
 
 .. csv-table::
-   :header: Tesselation flag set, Tesselation flag not set
+   :header: Tesselation flag not set, Tesselation flag set
    
    .. image:: ../images/heightfieldTriMat1.png, .. image:: ../images/heightfieldTriMat2.png
 
@@ -390,17 +390,17 @@ Examples:
 +-------------------+-------------------------------------------+
 | Tesselation flags | Result                                    |
 +===================+===========================================+
-| |     0,0,0       | .. image:: ../images/heightfieldTess1.png |
+| |     0,0,0       | .. image:: ../images/heightfieldTess2.png |
 | |     0,0,0       |                                           |
 | |     0,0,0       |                                           |
 +-------------------+-------------------------------------------+
-| |     1,1,1       | .. image:: ../images/heightfieldTess2.png |
+| |     1,1,1       | .. image:: ../images/heightfieldTess1.png |
 | |     1,1,1       |                                           |
 | |     1,1,1       |                                           |
 +-------------------+-------------------------------------------+
-| |     0,1,0       | .. image:: ../images/heightfieldTess3.png |
-| |     1,0,1       |                                           |
+| |     1,0,1       | .. image:: ../images/heightfieldTess3.png |
 | |     0,1,0       |                                           |
+| |     1,0,1       |                                           |
 +-------------------+-------------------------------------------+
 
 To tell the system the number of sampled heights in each direction, use a descriptor to instantiate a PxHeightField object::
diff --git a/PhysX_3.4/Documentation/PhysXGuide/_sources/Manual/Startup.txt b/PhysX_3.4/Documentation/PhysXGuide/_sources/Manual/Startup.txt
index da518a03..3cb347d1 100644
--- a/PhysX_3.4/Documentation/PhysXGuide/_sources/Manual/Startup.txt
+++ b/PhysX_3.4/Documentation/PhysXGuide/_sources/Manual/Startup.txt
@@ -111,13 +111,13 @@ Delay-Loading DLLs
 The PhysXCommon DLL, PxFoundation DLL and PxPvdSDK DLL are marked as delay-loaded inside of the PhysX, PhysXCooking, PhysXCommon and PxPvdSDK projects. So it is possible to have delay-loaded PxFoundation, PxPvdSDK, PhysXCommon, PhysX and PhysXCooking DLLs. 
 
 +++++++++++++++++++++++++++++++++++++++++++++++++++
-PhysXCommon DLL and PsFoundation DLL load
+PhysXCommon DLL and PxFoundation DLL load
 +++++++++++++++++++++++++++++++++++++++++++++++++++
 
 The application links against PhysXCommon DLL, and will usually load PxFoundation.dll, PxPvdSDK and PhysXCommon.dll before any other PhysX DLL. The DLL loaded by the application must be the same one that will be used by the PhysX and PhysXCooking DLLs.  In the PhysX and PhysXCooking DLLs, the choice of PhysXCommon, PxFoundation and PxPvdSDK is made as follows:
 
  * If delay load hook is specified the PhysXCommon name, PxFoundation or PxPvdSDK name provided by user is used
- * If delay load hook is not specified, the corresponding PhysXCommon DLL, PsFoundation DLL or PxPvdSDK DLL is used
+ * If delay load hook is not specified, the corresponding PhysXCommon DLL, PxFoundation DLL or PxPvdSDK DLL is used
  
 
 +++++++++++++++++++++++++++++++
@@ -154,11 +154,10 @@ The PxDelayLoadHook class supports loading of different versions of PhysXCommon
             { return "PxPvdSDK_x64_Test.dll"; }
     } gDelayLoadHook;
 
-Now the hook must be set for PhysX, PhysXCooking, PhysXGpu, PhysXCommon, PxPvdSDK::
+Now the hook must be set for PhysX, PhysXCooking, PhysXCommon, PxPvdSDK::
 
     PxSetPhysXDelayLoadHook(&gDelayLoadHook);
     PxSetPhysXCookingDelayLoadHook(&gDelayLoadHook);
-    PxSetPhysXGpuDelayLoadHook(&gDelayLoadHook);
     PxSetPhysXCommonDelayLoadHook(&gDelayLoadHook);
     PxPvdSetFoundationDelayLoadHook(&gDelayLoadHook);
     
diff --git a/PhysX_3.4/Documentation/PhysXGuide/_sources/Manual/VisualDebugger.txt b/PhysX_3.4/Documentation/PhysXGuide/_sources/Manual/VisualDebugger.txt
index 34e34ea7..2f274fbd 100644
--- a/PhysX_3.4/Documentation/PhysXGuide/_sources/Manual/VisualDebugger.txt
+++ b/PhysX_3.4/Documentation/PhysXGuide/_sources/Manual/VisualDebugger.txt
@@ -13,7 +13,7 @@ PVD
 
 The PhysX Visual Debugger (PVD) provides a graphical view of the PhysX scene and includes various tools to inspect and visualize variables of every PhysX object. Additionally it can also record and visualize memory and timing data.
 
-PVD can be downloaded from: http://supportcenteronline.com/ics/support/default.asp?deptID=1949
+PVD can be downloaded from: https://developer.nvidia.com/physx-visual-debugger
 
 Questions regarding the usage of the GUI should all be answered by its detailed built-in help.