Request: Revised command line input / batching

Generic forum to discuss Octane Render, post ideas and suggest improvements.
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Post Reply
newske
Licensed Customer
Posts: 126
Joined: Sat Nov 03, 2012 11:51 pm

I am proposing that the command line input have the possibility to refer to a text file for the render target information.

Currently, my batch files look somewhat like this (repeated many times):
"C:\...\octane.exe" "C:\...\scene.ocs" --film-height 720--film-width 1280 -s 512 -t "RenderTarget" -o "C:\...\Output.png" -e -q
For a single render that's pretty fine. Scene opens, voxelizes, renders, saves, quits.
The problem is when I'm trying to do 20 views of the same scene and the scene has to voxelize every time. A large scene and the load time could be up to 2-3 minutes. Still, for finished quality views, not too much.
The real problem is when I'm trying to do 2000 frames of animation. For a basic quality direct-lighting animation at a moderate (720p) resolution and a decent graphics card the loading/voxelizing time ends up being greater than the render time, such that if the scene were only loaded once the time would be cut in half.

Instead, what if the batch file could look like this:
"C:\...\octane.exe" "C:\...\scene.ocs" "C:\...\targets.txt" -e -q
And thus the text file would look like this:
-t Animation1 --cam-pos-x 208.33 --cam-pos-y 24.09 --cam-pos-z 27.82 --cam-target-x 160.36 --cam-target-y 24.09 --cam-target-z 0.66 --film-height 720 --film-width 1280 -s 128 -o "C:\...\Output1.png"
-t Animation1 --cam-pos-x 208.33 --cam-pos-y 24.09 --cam-pos-z 27.82 --cam-target-x 160.36 --cam-target-y 24.09 --cam-target-z 0.66 --film-height 720 --film-width 1280 -s 128 -o "C:\...\Output2.png"
...
-t Animation1 --cam-pos-x 208.33 --cam-pos-y 24.09 --cam-pos-z 27.82 --cam-target-x 160.36 --cam-target-y 24.09 --cam-target-z 0.66 --film-height 720 --film-width 1280 -s 128 -o "C:\...\Output999.png"
-t Animation1 --cam-pos-x 208.33 --cam-pos-y 24.09 --cam-pos-z 27.82 --cam-target-x 160.36 --cam-target-y 24.09 --cam-target-z 0.66 --film-height 720 --film-width 1280 -s 128 -o "C:\...\Output1000.png"
No more re-voxelizing for every frame. This would greatly enhance the production capability of the Standalone from many programs, as it is not difficult to generate such .txt files from a multitude of 3d programs. And, of course, it could still accept the previous method.

Could we see this change?
Octane for Rhino | Windows 8.1 x64 | i7-3820 OC | GTX970 4GB OC & GTX 560 Ti 1GB OC | 32GB DDR3
User avatar
roeland
OctaneRender Team
Posts: 1823
Joined: Wed Mar 09, 2011 10:09 pm

Hi,

We are planning to implement a more advanced input file format allowing Octane to import things like animation and proper instancing. We will then also review the command line options.

--
Roeland
Post Reply

Return to “General Discussion”