OctaneRender™ Standalone 1.52

[matej]

For some reason the aperture command line parameter doesn't seem to work (the value is not updated), although all the other camera parameters do. I use it like:

Code: Select all

--cam-aperture 1.4

[necko77]

online manual is not available at this particular moment, (http://render.otoy.com/manuals/Standalone_1_5/)
Can Manual be downloaded or just preview online only ?
How to bypass moments like this one ?

Over and out

Thx

[matej]

Could we have an option for the command line args, that assigns all the camera arguments to some existing camera node? The same as you can select which Render Target node or Geometry node to render, with -t & -m args respectively.

The problem is that all the --cam-* parameters are now assigned to some default 'hidden' camera node and if you use render targets, all those params are not applied to the camera in the Render Target. Maybe there is a way to do this in Lua, but it would be useful if it can be done through cmd line args.

[matej]

If I run a .lua script to the command line, all the print() statements are not outputted anywhere, even if Octane was started from a console. Could we have an option for such output from Octane to be passed to the console?

[stratified]

If I run a .lua script to the command line, all the print() statements are not outputted anywhere, even if Octane was started from a console. Could we have an option for such output from Octane to be passed to the console?

Hi Matej,

The output for Lua is going to the log. To redirect the log to stdout, you need to create a file octane_log_flags.txt in the directory of the binary. In this file goes the single word logToStdout.

cheers,
Thomas

[abstrax]

For some reason the aperture command line parameter doesn't seem to work (the value is not updated), although all the other camera parameters do. I use it like:

Code: Select all

--cam-aperture 1.4

Just for your information: This problem will be solved with the next build, which we plan to release this week.

[matej]

The output for Lua is going to the log. To redirect the log to stdout, you need to create a file octane_log_flags.txt in the directory of the binary. In this file goes the single word logToStdout.

It works, thanks

@abstrax, thanks for feedback

[manalokos]

Saving a image file with a existing name overwrites the file without asking. Already lost a few hours of render with this.