Scene Graph

Description of scenegraph structure and best practices


When working with this SDK and the rest of this documentation, a decent knowledge of Visionary Render tree structure is assumed.

This page provides a basic recap on node structures and locations in the tree, most commonly used to make CAD data visible in the 3D view. This structure can be seen in the Visionary Render tree views when importing data, or loading an existing scene.


This is the model data; vertices, materials, textures, and other supplementary data.

The standard location for assets is under the Libraries node (VRGetLibrariesNode). The organisation of nodes in this area of the tree is not subject to any concrete definition, so it is mostly up to the scene author to decide how best to structure the data for their purposes.

This might include Library child nodes containing specific types of asset (e.g. one for Models, one for Materials, one for Textures, etc).

Materials and Textures

Materials and Textures are usually standalone, single nodes.

A texture alone does not do much - it should be referenced by a material node, in one of the material's map properties.


Models have a more complex structure.

A model node is mostly just a container which does nothing on its own. It can contain any number of LOD or GeoGroup nodes (each LOD node is itself a GeoGroup container). Each GeoGroup can contain any number of Mesh nodes. Each Mesh node contains data about the mesh stored in VertexAttrib and IndexPrim nodes; vertices, indices, normals, texture coordinates, etc.

A GeoGroup can reference a Material, which is applied to all of its meshes. When a Model or LOD contains multiple GeoGroups, each GeoGroup may reference a different material.


The existence of assets in the Libraries section of the tree does not result in them being drawn. In order to use the assets in the scene, they must be instanced by Visual nodes attached to an Assembly and placed under the Scenes node (VRGetScenesNode).

In the Scenes tree view, Visual nodes are hidden, instead affecting the tree icon of the assembly, and sharing the same property panel. In the developer tree, this is not the case.

A Visual should reference the Model it wishes to use, and it will be rendered at the location specified by the Assembly transform, combined with any parent assembly transforms. A Visual can also reference a Material, which overrides the material selection of allGeoGroup nodes in the Model, unless they are set to Lock Material.

No Results.

Getting StartedArchitectureBest PracticesHow ToAdvanced TopicsChangelogvrtree_cppCoreForeign Function InterfaceMetanodesMigrationsObserversPropertiesTreeUtilitiesAPI DefinitionsVR ExchangePluginsLua API