kimusan wrote:Goldorak wrote:Yes, if you drop 001.jpg-300.jpg you can load an image sequence (in any format, including cube maps) as follows (can be EXR or PNG but they night take longer to load)
{"title":"MyCubeMapvideo_VR",
"author":" Goldorak",
"url:","*.jpg",
"loop":true,
"fps":60,
"scrub":0.1}
This will allow you to develop and test your content locally. We use ORC for 100+ frame 18K renders at scale, and further leverage the ORC render nodes to encode .OKX frames (OKX == device specific GPU image data specifically exported for an ORC supported target platform). This can be as high as 9 mins/frame for Gear VR compression compatible with Note 4 and later - which is longer than the render itself in some cases.
ORC generates a default JSON (you can edit it) that is included in an ORBX package along with all the frames for the job on completion. You can fetch it from a private URL, and even publish this URL to share with others. This way you can treat the render job a as a pure movie or navigable scene on its own right out of ORC.
Goldorak, I can't get this to work. The JSON file is named 001.json and the animation files are 001.jpg - 030.jpg, and I am running ORBX 2.0.7 (BTW in general Update does not seem to work at all on my Note 4 and Gear VR so I have to uninstall the app I want to update and then install it).
The app update problem is a known bug and our top priority. We haven't yet been able to resolve why this is happening with Oculus. It may or may not be our app. Our support resources are focused on this right now, but if you PM Jax he might be able to help you out today.
Just off the top of my head, could you try adding a prefix before the frame number in all the files, and the JSON too? If that fixes the issue, please let us know, so we can add a fix in the next update if needed.