HOOPS/3dGS automatically performs a wide variety of automatic optimizations, and efforts continually evolve in this area. Similarly, HOOPS/MVO automatically encapsulates a variety of performance guidelines because it encapsulates some higher-level application logic and provides many built in file import modules which handle scene-graph creation. However, because HOOPS/3dGS specifically consists of an API to create/manipulate the scene-graph hierarchy and it’s graphical primitives, the developer has some responsibility to ensure that the scene-graph is reasonably designed and appropriate attributes are being set.

The developer sometimes has the opportunity to set attributes which may sacrifice some visual accuracy in exchange for improved performance. For example, a 5 million point shell can run 5x faster if only 1/5 of the points are drawn using a lower level-of-detail (LOD) representation, but the choice of whether to enable that render mode lies with the application developer and ultimately the application’s interface.

The majority of these topics will apply to most HOOPS/3dAF applications, thus developers are strongly advised to review the content and follow the guidelines to the maximum extent possible.