From 3f9977d72f8a481e76b6ad643a3d312a8cf9b551 Mon Sep 17 00:00:00 2001 From: Sheikh Dawood Date: Mon, 13 Aug 2018 13:37:04 -0500 Subject: PhysX 3.4, APEX 1.4 patch release @24698370 --- PhysX_3.4/Documentation/PhysXAPI/files/classphysx_1_1PxTaskManager.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'PhysX_3.4/Documentation/PhysXAPI/files/classphysx_1_1PxTaskManager.html') diff --git a/PhysX_3.4/Documentation/PhysXAPI/files/classphysx_1_1PxTaskManager.html b/PhysX_3.4/Documentation/PhysXAPI/files/classphysx_1_1PxTaskManager.html index 8bda85a2..0bc98be7 100644 --- a/PhysX_3.4/Documentation/PhysXAPI/files/classphysx_1_1PxTaskManager.html +++ b/PhysX_3.4/Documentation/PhysXAPI/files/classphysx_1_1PxTaskManager.html @@ -90,7 +90,7 @@

Detailed Description

The PxTaskManager interface.

-A PxTaskManager instance holds references to user-provided dispatcher objects, when tasks are submitted the PxTaskManager routes them to the appropriate dispatcher and handles task profiling if enabled. Users should not implement the PxTaskManager interface, the SDK creates it's own concrete PxTaskManager object per-scene which users can configure by passing dispatcher objects into the PxSceneDesc.

+A PxTaskManager instance holds references to user-provided dispatcher objects, when tasks are submitted the PxTaskManager routes them to the appropriate dispatcher and handles task profiling if enabled. Users should not implement the PxTaskManager interface, the SDK creates its own concrete PxTaskManager object per-scene which users can configure by passing dispatcher objects into the PxSceneDesc.

See also:
CpuDispatcher

PxGpuDispatcher

Constructor & Destructor Documentation

-- cgit v1.2.3