From d41654b469fa51870b5952c836c04d9da17f32d3 Mon Sep 17 00:00:00 2001 From: Anton Novoselov Date: Tue, 8 Aug 2017 20:14:22 +0300 Subject: Updated to CL 22627414: * docs updates * authoring fixes * stress solver crash fixes --- docs/api_docs/files/pageextpxserialization.html | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'docs/api_docs/files/pageextpxserialization.html') diff --git a/docs/api_docs/files/pageextpxserialization.html b/docs/api_docs/files/pageextpxserialization.html index 92e056f..3fb2843 100644 --- a/docs/api_docs/files/pageextpxserialization.html +++ b/docs/api_docs/files/pageextpxserialization.html @@ -22,7 +22,7 @@

ExtPhysX Serialization (NvBlastExtPxSerialization)

This extension contains serializers which can be loaded into the ExtSerialization manager defined in Serialization (NvBlastExtSerialization).

To use this extension, you must also load the ExtSerialization extension and create a serialization manager as described in Serialization (NvBlastExtSerialization).

-We repeat this here (again, assuming we're in the Nv::Blast namespace):

+We repeat this here (again, assuming we are in the Nv::Blast namespace):

ExtSerialization* ser = NvBlastExtSerializationCreate();

Then, call the function NvBlastExtPxSerializerLoadSet, declared in NvBlastExtPxSerialization.h, passing in your TkFramework (required by ExtPhysX), along with your physx::PxPhysics and physx::PxCooking pointers:

@@ -43,7 +43,9 @@ As with low-level assets, you can serialize using the serialization manager dire uint64_t size = ser->serializeIntoBuffer(buffer, asset, ExtPxObjectTypeID::Asset);

or use the wrapper function defined in NvBlastExtPxSerialization.h:

-/code void* buffer; uint64_t size = NvBlastExtSerializationSerializeExtPxAssetIntoBuffer(buffer, *ser, asset); /endcode

+

void* buffer;
+uint64_t size = NvBlastExtSerializationSerializeExtPxAssetIntoBuffer(buffer, *ser, asset);
+


-- cgit v1.2.3