🐦Looking Glass Core Migration Guide
Update legacy Looking Glass apps to work with the 16" and 32" spatial displays
Looking Glass Core required the integrator to implement their own post-processing stage using a special shader and calibration parameters from the display. However, Bridge takes care of this post-processing step by using a shared rendering context with a shared framebuffer object.
An application using Bridge is then responsible for rendering views of 3D objects into a GPU texture using a quilt format. Then the Bridge code will apply the Looking Glass optical transformation as a post-processing step. This process ensures that the application can render correctly to any Looking Glass display.
The aforementioned integration pattern is very different from Looking Glass Core. So Bridge still supports the same functionality offered as part of Looking Glass Core using new native functions. The following table presents a mapping between Looking Glass Core functions and corresponding Bridge functions.
Note: the shader used in legacy applications will need to be updated for applications that support the new Looking Glass 16” and 32” Spatial Displays.
Looking Glass Core SDK → Bridge SDK
| Looking Glass Core SDK | Looking Glass Bridge SDK |
|---|---|
No longer needed | |
No longer needed | |
No longer needed | |
Last updated