It tooks nearly 10-20 seconds to launch the application every time. And sometime it authorsize failed and need to retry 20 seconds later.
But in my usage, we want to use octane render to build an automatic quick(30s per task) render farm, octane.exe needs to launch every task by other python script. So that wastes so much time. WIth this usage, we plan to buy 10+ licenses and much more in the furture.
Now, How to avoid the slow launch if I bought the license?
A little sorry about my Chinese English。
Why the octane.exe launch slowly?
Are you using OctaneVR? If yes, then every time you launch Octane, some data is loaded from OctaneLive to allow rendering, which takes some time. In the regular Standalone the data is cached and doesn't need to be downloaded every time. I.e. the startup times should be quicker.butterhuang wrote:It tooks nearly 10-20 seconds to launch the application every time. And sometime it authorsize failed and need to retry 20 seconds later.
But in my usage, we want to use octane render to build an automatic quick(30s per task) render farm, octane.exe needs to launch every task by other python script. So that wastes so much time. WIth this usage, we plan to buy 10+ licenses and much more in the furture.
Now, How to avoid the slow launch if I bought the license?
A little sorry about my Chinese English。
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
- butterhuang
- Posts: 11
- Joined: Mon Jun 01, 2015 5:10 am
what's the different between OctaneVR and regular Standalone?abstrax wrote:Are you using OctaneVR? If yes, then every time you launch Octane, some data is loaded from OctaneLive to allow rendering, which takes some time. In the regular Standalone the data is cached and doesn't need to be downloaded every time. I.e. the startup times should be quicker.butterhuang wrote:It tooks nearly 10-20 seconds to launch the application every time. And sometime it authorsize failed and need to retry 20 seconds later.
But in my usage, we want to use octane render to build an automatic quick(30s per task) render farm, octane.exe needs to launch every task by other python script. So that wastes so much time. WIth this usage, we plan to buy 10+ licenses and much more in the furture.
Now, How to avoid the slow launch if I bought the license?
A little sorry about my Chinese English。
Hi,
exact the same except for a different licence system, only max 2 GPU and the absence of the net-rendering feature
ciao beppe
exact the same except for a different licence system, only max 2 GPU and the absence of the net-rendering feature

ciao beppe
OctaneVR is free until end of July, because of that we added some limitations and restrictions: As Beppe mentioned you can use only up to 2 GPUs, no network rendering and can't use it without an Internet connection.butterhuang wrote:what's the different between OctaneVR and regular Standalone?
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
- butterhuang
- Posts: 11
- Joined: Mon Jun 01, 2015 5:10 am
How much quicker if I use the regular standalone about the launch proccess?abstrax wrote:Are you using OctaneVR? If yes, then every time you launch Octane, some data is loaded from OctaneLive to allow rendering, which takes some time. In the regular Standalone the data is cached and doesn't need to be downloaded every time. I.e. the startup times should be quicker.butterhuang wrote:It tooks nearly 10-20 seconds to launch the application every time. And sometime it authorsize failed and need to retry 20 seconds later.
But in my usage, we want to use octane render to build an automatic quick(30s per task) render farm, octane.exe needs to launch every task by other python script. So that wastes so much time. WIth this usage, we plan to buy 10+ licenses and much more in the furture.
Now, How to avoid the slow launch if I bought the license?
A little sorry about my Chinese English。