From 326e24039dd3f063afd211fad770e15bdd5ff4ea Mon Sep 17 00:00:00 2001 From: Sheikh Dawood Abdul Ajees Date: Sun, 2 Dec 2018 13:31:57 -0600 Subject: PhysX 3.4, APEX 1.4 patch release @25354359 --- PhysX_3.4/Documentation/PhysXGuide/Manual/ExtendingSerialization.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'PhysX_3.4/Documentation/PhysXGuide/Manual/ExtendingSerialization.html') diff --git a/PhysX_3.4/Documentation/PhysXGuide/Manual/ExtendingSerialization.html b/PhysX_3.4/Documentation/PhysXGuide/Manual/ExtendingSerialization.html index 2ecdfa05..d8372ea5 100644 --- a/PhysX_3.4/Documentation/PhysXGuide/Manual/ExtendingSerialization.html +++ b/PhysX_3.4/Documentation/PhysXGuide/Manual/ExtendingSerialization.html @@ -68,7 +68,7 @@

Serialization and deserialization of a custom class can be achieved with the following steps:

  1. Define a PxConcreteType and type info for the custom class. Make sure its type value is unique.
    2. -
  2. The custom class needs to inherit from PxBase and implement it's interface.
    3. +
  3. The custom class needs to inherit from PxBase and implement its interface.
  4. Instance PxSerializerDefaultAdapter<T> and implement specialized methods where necessary.
  5. If retargeting to other platforms is needed, implement getBinaryMetaData().
  6. Register the adapter and metadata, see PX_NEW_SERIALIZER_ADAPTER , PxSerializationRegistry::registerSerializer and PxSerializationRegistry::registerBinaryMetaDataCallback. Note that serializers also need to be unregistered before PxSerializationRegistry::release is called. The application is responsible for custom type serializer allocation and deallocation.
    7. -- cgit v1.2.3