Hi,
Vizor.io is a web based virtual creation "sandbox". I chatted in twitter with one of their staff members and I suggested to them Octane Render integration. What Otoy would say, could this seem doable?
http://vizor.io/
vizor.io
It looks great, would love to support it best we can. Can you have them ping us on twitter or [email protected]?
- ristoraven
- Posts: 390
- Joined: Wed Jan 08, 2014 5:47 am
I thought so too 
Sure, I'll send them your message.

Sure, I'll send them your message.
- ristoraven
- Posts: 390
- Joined: Wed Jan 08, 2014 5:47 am
In case you wish to try this service, note in the terms of service chapter 4.5.
"4.5 These Terms of Service do not constitute any transfer of intellectual property rights in the Content from You to Pixelface. However, You grant to Pixelface a perpetual, irrevocable, worldwide, non-exclusive, royalty-free, fully paid-up, transferable, sub-licensable license to use, transfer and modify the Content in any way ("License"). You represent and warrant that You have the right to grant the License to the Content to Pixelface. The License shall survive the termination of these Terms of Service."
I asked from Vizor that does this mean they could open up my project, modify it and then license it to a third party..
I got a reply that in this betaphace users privacy is weak. Anyone who knows the address to the project can fiddle with it as he/she wishes. However, this will change later on and the Terms of Service will be changed so that the author has the proper rights.
So if you wish to try this now, keep this in mind and don't upload any assets you don't wish to be "open for everyone".. Use test assets only.
Good news, that based on twitter chat, Otoy and Vizor are connected and they may come up with something.. wonderful.
If you look at the tools already there, mind boggles what you could eventually do with those when combined with Otoys stereo cubemaps..
"4.5 These Terms of Service do not constitute any transfer of intellectual property rights in the Content from You to Pixelface. However, You grant to Pixelface a perpetual, irrevocable, worldwide, non-exclusive, royalty-free, fully paid-up, transferable, sub-licensable license to use, transfer and modify the Content in any way ("License"). You represent and warrant that You have the right to grant the License to the Content to Pixelface. The License shall survive the termination of these Terms of Service."
I asked from Vizor that does this mean they could open up my project, modify it and then license it to a third party..
I got a reply that in this betaphace users privacy is weak. Anyone who knows the address to the project can fiddle with it as he/she wishes. However, this will change later on and the Terms of Service will be changed so that the author has the proper rights.
So if you wish to try this now, keep this in mind and don't upload any assets you don't wish to be "open for everyone".. Use test assets only.
Good news, that based on twitter chat, Otoy and Vizor are connected and they may come up with something.. wonderful.

If you look at the tools already there, mind boggles what you could eventually do with those when combined with Otoys stereo cubemaps..
- regionfive
- Posts: 73
- Joined: Mon Dec 06, 2010 5:50 pm
- Location: Nuremberg/Germany
- Contact:
this is the most awesome web stuff i´ve ever seen.
Thanks for posting Guys!!! That's awesome tool =)
- ristoraven
- Posts: 390
- Joined: Wed Jan 08, 2014 5:47 am
Guys.... heads up!
https://twitter.com/Vizor_VR/status/669896024140288001
Vizor.io –– now live w/ updated editor, drag & drop, user pages, @otoy stereo cubemap support and a new homepage!
https://twitter.com/Vizor_VR/status/669896024140288001
Vizor.io –– now live w/ updated editor, drag & drop, user pages, @otoy stereo cubemap support and a new homepage!
Yes! More to come...
- 360precision
- Posts: 63
- Joined: Mon Apr 27, 2015 8:55 am
This is cool but an example would be helpful.
Hi got your PM. I will review this week.360precision wrote:This is cool but an example would be helpful.
Given how much we are changing on the authoring end right now both in ORBX/Octane, we don't recommend building too far beyond the simple examples we have put out thus far, especially for commercial work (ORBX Media Player is still a simple viewer app/experimental sandbox, not yet a commercial publishing tool for white labelled apps - that will come in time).
The primary consideration today is that we (and most Octane users) want support for 3rd party tools like vizor.io and our own built in Octane node system (see image I posted in the ORBX 2.0 player thread) for art driven authoring of ORBX player content in the not too distant future.
The ORBX Lua backend API (or ORBX js backend for WebVR) is evolving pretty quickly around these efforts, and the API we have now is changing behind the scenes as this matures across more platforms beyond just Gear VR. While you can freely experiment with what's exposed in the JSON/Lua today, for commercial projects you really should wait on the script nodes we are building into Octane and 3rd party apps/tools. These will be supported officially, and be updated with every Octane release which exposes new features for ORBX Media player playback.