Performance

Keep frame rates low

Keep frame rates above 30fps.

When viewers switch from high frame-rate experiences to low frame-rate experiences, they often donโ€™t have words to describe the loss in quality, but can tell that something doesnโ€™t look right. In short: low frame rates ruin the illusion.

This can be challenging as Looking Glass renders 45 simultaneous views per frame. This is an expensive operation when not managed properly.

If using Unity, use the Rendering Statistics window to keep tabs on the following.

Keep poly count low

The ballpark range of the upper limit of polygons the system can render on a typical high end gaming computer is about 200k to 300k polys. This guideline can be bent under certain contexts as long as the final experience is tested.

Keep draw ball catches low

Having many different textures on different objects under many different lights will multiply out to be many different draw call batches. If frame rates are too high, try unifying the lighting and textures to lower the batch count.

Draw only what's important

Make sure to disable any unnecessary scene elements to only render what is important.

Use view interpolation

The HoloPlay Unity Plugin View Interpolation will skip intermediate renders (and interpolate from captured renders), lowering computation cost. This can be used to increase performance.

Last updated

#502: August 18 Changes

Change request updated