The base class of all Aspose.ThreeD objects, all sub classes will support dynamic properties.
The BonePose contains the transformation matrix for a bone node
Meta data or custom objects used in 3D files are managed by this class. All custom properties are saved as dynamic properties.
Exceptions when Aspose.3D failed to export the scene to file
File format definition
File format type
Global transform is similar to Transform but it's immutable while it represents the final evaluated transformation. Right-hand coordinate system is used while evaluating global transform
Exception when Aspose.3D failed to open the specified source
Provides methods to license the component.
Provides methods to set metered key.
Represents an element in the scene graph. A scene graph is a tree of Node objects. The tree management services are self contained in this class. Note the Aspose.3D SDK does not test the validity of the constructed scene graph. It is the responsibility of the caller to make sure that it does not generate cyclic graphs in a node hierarchy. Besides the tree management, this class defines all the properties required to describe the position of the object in the scene. This information include the basic Translation, Rotation and Scaling properties and the more advanced options for pivots, limits, and IK joints attributes such the stiffness and dampening. When it is first created, the Node object is "empty" (i.e: it is an object without any graphical representation that only contains the position information). In this state, it can be used to represent parents in the node tree structure but not much more. The normal use of this type of objects is to add them an entity that will specialize the node (see the "Entity"). The entity is an object in itself and is connected to the the Node. This also means that the same entity can be shared among multiple nodes. Camera, Light, Mesh, etc... are all entities and they all derived from the base class Entity.
Class to hold user-defined properties.
A scene is a top-level object that contains the nodes, geometries, materials, textures, animation, poses, sub-scenes and etcs. Scene can have sub-scenes, acts as multiple-document support in files like collada/blender/fbx Node hierarchy can be accessed through RootNodeLibrary is used to keep a reference of unattached objects during serialization(like meta data or custom objects) so it can be used as a library.
A transform contains information that allow access to object's translate/scale/rotation or transform matrix at minimum cost This is used by local transform.
A callback to travel through the whole node hierarchy.