pfschuyler wrote:1.) I have two good graphics cards but only one appears to be utilized. Is this a limitation of Octane's Unity version?
For the (free) T1, we limit the usage to a single GPU. If you have a higher Tier, you can activate additional GPUs in the Octane settings window.
pfschuyler wrote:2.) I want to render out cubic panoramic images exactly like the old "render the metaverse" GearVR competition. Those settings used to be (camera panoramic:cube map, Stereo enabled: side-by-side, resolution 18432x1536). That full resolution does not seem to be allowed by Octane, it gives an error message saying the resolution is too high. In the resolution presets there is an option listed under Virtual Reality>Gear VR (CUBE MAP), which has a resolution of 9216x1536 (six 1536x1536 images I guess vs the old 12 stereo pairs?). Using this option with Stereo side-by-side produces 12 stretched tiles. What group of settings can produce the same Gear VR cubemaps, or is there something I'm missing?
Unity's max texture size is 16384 pixels, which isn't enough for a Gear VR stereo cubemap (which requires 18432 pixels). You can create a 9216x3072 texture, and set the stereo ouput to Over-under
. This will fit in a Unity texture. It will be quite an impact on performance for now, until we can figure out how to hide the latency of copying the Octane render result to the Unity window.
I'm not sure how to get an over-under
cubemap to work with our ORBX viewer for the Gear VR, but I'll check with the team that works on it.