Looks like are a few results returned by io3d.furniture.search are groups, causing errors for a-frame, furniture.get and storage.export* methods.

For example: https://furniture.3d.io/#furnitureId=68833b2a-6559-4b25-8690-8ee18ecc9d41

To Reproduce
io3d.furniture.get('68833b2a-6559-4b25-8690-8ee18ecc9d41')

Actual
error gets thrown: File header error: Wrong magic number. F

engine-openvr-scene has the beginnings of a teleportation-style locomotion system. A long time ago, Valve and others discovered that fading to black before the teleport event minimizes locomotion-induced sickness. This will need to be integrated into the renderer as configurable post pass.

Port some of the initial HTK focus tests to ensure focusing works properly

Ideally we will have a gltf for each device, but in the meantime we could use a generic VR input device like https://poly.google.com/view/cUT5C1Krx7g or https://poly.google.com/view/0n5B6e5lYZe

I like .ply, it's an easy format that supports vertex colors! .ply files are often used for point clouds, so it could be good to consider point cloud rendering when importing .ply files as well.

Might be able to find a nice library for this on here:
https://github.com/nothings/single_file_libs