The Scene Statistics dialogue provides information about the nodes and their occurrence that have been used in the scene. It shows which scene components and resources use how much memory space. Additionally all assets that are used in the open Ventuz scenes are listed.
The Statistics dialogue is separated into four parts.
The Nodes tab gives an overview of the nodes used in the currently open scene.
Below the summery all used nodes are listed according to their Toolbox category. The number behind the category folder is the total number of nodes from this category in the scene. If one expands the folder, all used node types and their occurrence are listed. It is possible to double-click on an entry and the Hierarchy and Content Editors will navigate to the according node in the scene tree.
Additional filters can be applied to list e.g. deprecated nodes, see the following list for more.
Filter | Function |
No Filters | All Nodes of the active scene |
Hierarchy Only | Only Hierarchy Nodes |
Content Only | Only Content Nodes |
Full ScenePort Hierarchy | All Nodes from the active and all nested Scenes |
Deprecated only | Only Nodes of a previous Ventuz version that are no longer available |
Live-Linked only | Only Nodes with an active Live-Link |
The Resources tab shows the memory usage of all scene resources. If the Show all Resources in Memory option is enabled, all resources of all loaded scenes will be listed; otherwise only those of the active scene. The resources are assigned to different categories/folders:
The memory usage of the resources is separated into the System and Video memory pools. System represents the normal CPU memory and Video the memory on graphics cards.
The Assets tab lists all assets that are currently loaded into memory. Every asset lists all those nodes which reference this asset. The assets are sorted according to their data pools in the Project folder.
The Issues tab lists all nodes that are causing issues. Scenes from older Ventuz versions can contain nodes that do either not work at all any more, cause errors in the rendering or only function in a limited fashion.
Hovering over the Nodes in the Issues tab shows a tooltip with a hint on how to node could be replaced.
You can also use the Auto-Resolve issues, which will try to solve issues automatically, for example exchanging deprecated nodes with new ones.
If the scene tree is modified by adding or deleting any nodes, press the Refresh button to update the statistics.