Cramming PhysX in there

More PhysX work

More PhysX work

modules/PhysX/physx/physx-sys/pxbind/tests/data/enum/flags.h

@@ -0,0 +1,95 @@
+#include "foundation/PxFlags.h"
+#include "PxArticulationReducedCoordinate.h"
+
+namespace physx {
+    // From PxActorData.h
+
+    /**
+    \brief Identifies each type of information for retrieving from actor.
+    @see PxScene::applyActorData
+    */
+    struct PxActorCacheFlag
+    {
+        enum Enum
+        {
+            eACTOR_DATA = (1 << 0), //include transform and velocity
+            eFORCE = (1 << 2),
+            eTORQUE = (1 << 3)
+        };
+    };
+
+    /**
+    \brief Collection of set bits defined in PxActorCacheFlag.
+
+    @see PxActorCacheFlag
+    */
+    typedef PxFlags<PxActorCacheFlag::Enum, PxU16> PxActorCacheFlags;
+
+    // From PxArticulationFlags.h
+
+    /**
+    \brief Flags which affect the behavior of PxShapes.
+
+    @see PxShape PxShape.setFlag()
+    */
+    struct PxShapeFlag
+    {
+        enum Enum
+        {
+            /**
+            \brief The shape will partake in collision in the physical simulation.
+
+            \note It is illegal to raise the eSIMULATION_SHAPE and eTRIGGER_SHAPE flags.
+            In the event that one of these flags is already raised the sdk will reject any 
+            attempt to raise the other.  To raise the eSIMULATION_SHAPE first ensure that 
+            eTRIGGER_SHAPE is already lowered.
+
+            \note This flag has no effect if simulation is disabled for the corresponding actor (see #PxActorFlag::eDISABLE_SIMULATION).
+
+            @see PxSimulationEventCallback.onContact() PxScene.setSimulationEventCallback() PxShape.setFlag(), PxShape.setFlags()
+            */
+            eSIMULATION_SHAPE				= (1<<0),
+
+            /**
+            \brief The shape will partake in scene queries (ray casts, overlap tests, sweeps, ...).
+            */
+            eSCENE_QUERY_SHAPE				= (1<<1),
+
+            /**
+            \brief The shape is a trigger which can send reports whenever other shapes enter/leave its volume.
+
+            \note Triangle meshes and heightfields can not be triggers. Shape creation will fail in these cases.
+
+            \note Shapes marked as triggers do not collide with other objects. If an object should act both
+            as a trigger shape and a collision shape then create a rigid body with two shapes, one being a 
+            trigger shape and the other a collision shape. It is illegal to raise the eTRIGGER_SHAPE and 
+            eSIMULATION_SHAPE flags on a single PxShape instance.  In the event that one of these flags is already 
+            raised the sdk will reject any attempt to raise the other.  To raise the eTRIGGER_SHAPE flag first 
+            ensure that eSIMULATION_SHAPE flag is already lowered.
+
+            \note Trigger shapes will no longer send notification events for interactions with other trigger shapes.
+
+            \note Shapes marked as triggers are allowed to participate in scene queries, provided the eSCENE_QUERY_SHAPE flag is set. 
+
+            \note This flag has no effect if simulation is disabled for the corresponding actor (see #PxActorFlag::eDISABLE_SIMULATION).
+
+            @see PxSimulationEventCallback.onTrigger() PxScene.setSimulationEventCallback() PxShape.setFlag(), PxShape.setFlags()
+            */
+            eTRIGGER_SHAPE					= (1<<2),
+
+            /**
+            \brief Enable debug renderer for this shape
+
+            @see PxScene.getRenderBuffer() PxRenderBuffer PxVisualizationParameter
+            */
+            eVISUALIZATION					= (1<<3)
+        };
+    };
+
+    /**
+    \brief collection of set bits defined in PxShapeFlag.
+
+    @see PxShapeFlag
+    */
+    typedef PxFlags<PxShapeFlag::Enum,PxU8> PxShapeFlags;
+}

modules/PhysX/physx/physx-sys/pxbind/tests/data/enum/i32.h

@@ -0,0 +1,48 @@
+// From PxBroadPhase.h
+
+namespace physx {
+
+/**
+\brief Broad phase algorithm used in the simulation
+
+eSAP is a good generic choice with great performance when many objects are sleeping. Performance
+can degrade significantly though, when all objects are moving, or when large numbers of objects
+are added to or removed from the broad phase. This algorithm does not need world bounds to be
+defined in order to work.
+
+eMBP is an alternative broad phase algorithm that does not suffer from the same performance
+issues as eSAP when all objects are moving or when inserting large numbers of objects. However
+its generic performance when many objects are sleeping might be inferior to eSAP, and it requires
+users to define world bounds in order to work.
+
+eABP is a revisited implementation of MBP, which automatically manages broad-phase regions.
+It offers the convenience of eSAP (no need to define world bounds or regions) and the performance
+of eMBP when a lot of objects are moving. While eSAP can remain faster when most objects are
+sleeping and eMBP can remain faster when it uses a large number of properly-defined regions,
+eABP often gives the best performance on average and the best memory usage.
+
+ePABP is a parallel implementation of ABP. It can often be the fastest (CPU) broadphase, but it
+can use more memory than ABP.
+
+eGPU is a GPU implementation of the incremental sweep and prune approach. Additionally, it uses a ABP-style
+initial pair generation approach to avoid large spikes when inserting shapes. It not only has the advantage 
+of traditional SAP approch which is good for when many objects are sleeping, but due to being fully parallel, 
+it also is great when lots of shapes are moving or for runtime pair insertion and removal. It can become a 
+performance bottleneck if there are a very large number of shapes roughly projecting to the same values
+on a given axis. If the scene has a very large number of shapes in an actor, e.g. a humanoid, it is recommended
+to use an aggregate to represent multi-shape or multi-body actors to minimize stress placed on the broad phase.
+*/
+struct PxBroadPhaseType
+{
+	enum Enum
+	{
+		eSAP,	//!< 3-axes sweep-and-prune
+		eMBP,	//!< Multi box pruning
+		eABP,	//!< Automatic box pruning
+		ePABP,	//!< Parallel automatic box pruning
+		eGPU,	//!< GPU broad phase
+		eLAST
+	};
+};
+
+} // physx

modules/PhysX/physx/physx-sys/pxbind/tests/data/enum/simple.h

@@ -0,0 +1,9 @@
+namespace physx {
+
+/** enum for empty constructor tag*/
+enum PxEMPTY
+{
+	PxEmpty
+};
+
+} // physx

modules/PhysX/physx/physx-sys/pxbind/tests/data/enum/u32.h

@@ -0,0 +1,79 @@
+namespace physx {
+
+// From PxThread.h
+
+struct PxThreadPriority
+{
+	enum Enum
+	{
+		eHIGH         = 0,	//!< High priority
+		eABOVE_NORMAL = 1,	//!< Above Normal priority
+		eNORMAL       = 2,	//!< Normal/default priority
+		eBELOW_NORMAL = 3,	//!< Below Normal priority
+		eLOW          = 4,	//!< Low priority.
+		eFORCE_DWORD  = 0xffFFffFF
+	};
+};
+
+// From PxShape.h
+
+/**
+\brief Flags which affect the behavior of PxShapes.
+
+@see PxShape PxShape.setFlag()
+*/
+struct PxShapeFlag
+{
+	enum Enum
+	{
+		/**
+		\brief The shape will partake in collision in the physical simulation.
+
+		\note It is illegal to raise the eSIMULATION_SHAPE and eTRIGGER_SHAPE flags.
+		In the event that one of these flags is already raised the sdk will reject any 
+		attempt to raise the other.  To raise the eSIMULATION_SHAPE first ensure that 
+		eTRIGGER_SHAPE is already lowered.
+
+		\note This flag has no effect if simulation is disabled for the corresponding actor (see #PxActorFlag::eDISABLE_SIMULATION).
+
+		@see PxSimulationEventCallback.onContact() PxScene.setSimulationEventCallback() PxShape.setFlag(), PxShape.setFlags()
+		*/
+		eSIMULATION_SHAPE				= (1<<0),
+
+		/**
+		\brief The shape will partake in scene queries (ray casts, overlap tests, sweeps, ...).
+		*/
+		eSCENE_QUERY_SHAPE				= (1<<1),
+
+		/**
+		\brief The shape is a trigger which can send reports whenever other shapes enter/leave its volume.
+
+		\note Triangle meshes and heightfields can not be triggers. Shape creation will fail in these cases.
+
+		\note Shapes marked as triggers do not collide with other objects. If an object should act both
+		as a trigger shape and a collision shape then create a rigid body with two shapes, one being a 
+		trigger shape and the other a collision shape. It is illegal to raise the eTRIGGER_SHAPE and 
+		eSIMULATION_SHAPE flags on a single PxShape instance.  In the event that one of these flags is already 
+		raised the sdk will reject any attempt to raise the other.  To raise the eTRIGGER_SHAPE flag first 
+		ensure that eSIMULATION_SHAPE flag is already lowered.
+
+		\note Trigger shapes will no longer send notification events for interactions with other trigger shapes.
+
+		\note Shapes marked as triggers are allowed to participate in scene queries, provided the eSCENE_QUERY_SHAPE flag is set. 
+
+		\note This flag has no effect if simulation is disabled for the corresponding actor (see #PxActorFlag::eDISABLE_SIMULATION).
+
+		@see PxSimulationEventCallback.onTrigger() PxScene.setSimulationEventCallback() PxShape.setFlag(), PxShape.setFlags()
+		*/
+		eTRIGGER_SHAPE					= (1<<2),
+
+		/**
+		\brief Enable debug renderer for this shape
+
+		@see PxScene.getRenderBuffer() PxRenderBuffer PxVisualizationParameter
+		*/
+		eVISUALIZATION					= (1<<3)
+	};
+};
+
+} // physx