jingles wrote:Thanks Goldorak. Can the file type be used to package 3D polygonal shapes which could be parsed (?) by threejs?
The Gear VR OToy media player and OctaneRender's ORBX file output turned me on to this potential, though am looking to use this in a non-VR capacity.
I'm hitting walls trying to figure out how to get animated/baked 3D shapes into this streetview experience and hoping this may be an alt option.
Thanks
There is no mesh support in the current app. This is being added into the ORBX 3.0 player (released probably during the Octane 3 beta when baking is solid). We are testing mesh loading on Gear VR (with octane 3 baked textures+mesh export) and it works, but you have a limited budget of 65K polys for meshes on GVR. Mesh export is more useful on PC VR.
For non-VR viewing, you can push more polys on the android app.
The current ORBX scene packages exported from Octane 2.x contain OBJ or ABC files, so this can be loaded into any app that supports those formats - and I believe three.js has an OBJ viewer.
When we export the mesh layers for ORBX 3.0 viewer in compressed/streaming format, we plan to do the same thing we do with OKX textures now, which is make a device/GPU specific package optimized for fast loading, streaming and rendering on the client. For example OpenGL ES2 has 16-bit index buffer, PC DX9 20-bit etc. so the mesh has to be exported differently - unless we send down the original OBJ, ABC, but then it would take too long to load and not easy to compress, and performance might be slow.
We are adding export and publishing options on ORC for mesh export. This way we can keep adding new export options for your uploaded ORBX scene as new devices come out, while still keeping a single URL . The ORBX viewer will automatically download the right package for the device requesting the content, like youtube does for video.
We may add a generic OBJ file loader in the viewer too, but it is not on our current roadmap for the next release.