Render Stats

Press F4 to see the render stats. The first value 'fps' gives some indication of how well this scene will perform when rendered in real time VR. The Oculus and Vive, for example, both run at 90 fps so ideally the scene will render at or above that. A high drawable count that is more than a few thousand will cause frame rate drops. The term drawable is used in the Vizard context to define an object that Vizard performs a cull check on each frame. The exact number that can be supported without frame drops depends on the GPU used as well as other aspects of the scene (e.g. polygons, textures, real time lights etc.) What tends to cause high drawable counts are trees, plants, and other components that contain hundreds or thousands of individual parts.

An issue common to models taken from the 3DWarehouse (like this one) is with foliage. In most cases where the foliage looks good, it doesn't render very well in real time. There are optimizations that are possible to reduce drawables but not in the direct SU to Vizard workflow (e.g. using 3ds Max as intermediary). The only choice here to render at a decent rate is to either remove or reduce the amount of foliage in the scene.


Back: Inspector

Next: Scene Graph