From 3dfe2108cfab31ba3ee5527e217d0d8e99a51162 Mon Sep 17 00:00:00 2001 From: git perforce import user Date: Tue, 25 Oct 2016 12:29:14 -0600 Subject: Initial commit: PhysX 3.4.0 Update @ 21294896 APEX 1.4.0 Update @ 21275617 [CL 21300167] --- .../files/structPxPvdInstrumentationFlag.html | 92 ++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 PhysX_3.4/Documentation/PhysXAPI/files/structPxPvdInstrumentationFlag.html (limited to 'PhysX_3.4/Documentation/PhysXAPI/files/structPxPvdInstrumentationFlag.html') diff --git a/PhysX_3.4/Documentation/PhysXAPI/files/structPxPvdInstrumentationFlag.html b/PhysX_3.4/Documentation/PhysXAPI/files/structPxPvdInstrumentationFlag.html new file mode 100644 index 00000000..1ab08c7a --- /dev/null +++ b/PhysX_3.4/Documentation/PhysXAPI/files/structPxPvdInstrumentationFlag.html @@ -0,0 +1,92 @@ + + + NVIDIA(R) PhysX(R) SDK 3.4 API Reference: PxPvdInstrumentationFlag Struct Reference + + + + + + + +
+

PxPvdInstrumentationFlag Struct Reference
+ +[Pvd] +

types of instrumentation that PVD can do. +More... +

+#include <PxPvd.h> +

+ +

+List of all members. + + + + +

Public Types

enum  Enum {
+  eDEBUG = 1 << 0, +
+  ePROFILE = 1 << 1, +
+  eMEMORY = 1 << 2, +
+  eALL = (eDEBUG | ePROFILE | eMEMORY) +
+ }
+

Detailed Description

+types of instrumentation that PVD can do.

Member Enumeration Documentation

+ +
+
+ + + + +
enum PxPvdInstrumentationFlag::Enum
+
+
+ +

+

Enumerator:
+ + + + + +
eDEBUG  +Send debugging information to PVD. +

+This information is the actual object data of the rigid statics, shapes, articulations, etc. Sending this information has a noticeable impact on performance and thus this flag should not be set if you want an accurate performance profile.

ePROFILE  +Send profile information to PVD. +

+This information populates PVD's profile view. It has (at this time) negligible cost compared to Debug information and makes PVD *much* more useful so it is quite highly recommended.

+This flag works together with a PxCreatePhysics parameter. Using it allows the SDK to send profile events to PVD.

eMEMORY  +Send memory information to PVD. +

+The PVD sdk side hooks into the Foundation memory controller and listens to allocation/deallocation events. This has a noticable hit on the first frame, however, this data is somewhat compressed and the PhysX SDK doesn't allocate much once it hits a steady state. This information also has a fairly negligible impact and thus is also highly recommended.

+This flag works together with a PxCreatePhysics parameter, trackOutstandingAllocations. Using both of them together allows users to have an accurate view of the overall memory usage of the simulation at the cost of a hashtable lookup per allocation/deallocation. Again, PhysX makes a best effort attempt not to allocate or deallocate during simulation so this hashtable lookup tends to have no effect past the first frame.

+Sending memory information without tracking outstanding allocations means that PVD will accurate information about the state of the memory system before the actual connection happened.

eALL  +
+
+ +
+

+

The documentation for this struct was generated from the following file: +
+ +

+Copyright © 2008-2016 NVIDIA Corporation, 2701 San Tomas Expressway, Santa Clara, CA 95050 U.S.A. All rights reserved. www.nvidia.com + + -- cgit v1.2.3