OctaneRender™ Standalone 1.34

[roeland]

Hi,

This is a release to patch a few bugs of 1.33, and add some missing features.


Changes since version 1.33

Rendering

• Added object layer picker, which works similar to the material picker. Picking a mesh without an object layer map attached will select the mesh node.
• Added object layer ID channel to the info channels kernel.
• The wireframe mode works with any type of camera, and the line weights are more even.
• Added option to the info channel kernel to disable motion blur, DOF and filtering.
• Changed how PMC handles high ray depths. All rays are traced until they reach the maximum depth, so transparent objects no longer cause a dark outline in scenes.
• Fixed behavior of glossy materials when using the direct lighting kernel
• Fixed broken renderer state after switching on the environment importance sampling with the image texture power set to 0.

Lua

• Lua scripts can place text and progress in the status bar.
• Fix setting up aperiodic animators,
• Add copyItemTree function to copy an item and all its inputs, and writeToPackage to save a root node graph to a package.

User interface

• The text in a note node is always updated after deselecting the node. No click on the Update button is required.
• If connection to OctaneLive fails and no offline data is available, make sure Octane appears in the taskbar anyway.
• Octane saves if a node was expanded in the node inspector.

Other

• Added new command line parameters for use in combination with --script:
  • --no-gui: hides the main Octane UI, and exit after the script finishes
  • --stop-after-script: exit after the script finishes
• Fixed saving relative paths on Windows.

Download:

Windows
ZIP archives:
- 64-bit
- 32-bit

MacOS X
ZIP archive:
- 32-bit and 64-bit

Linux
ZIP archive:
- 64-bit

Happy rendering,
Your OTOY NZ Team

[Tugpsx]

Added object layer picker, which works similar to the material picker. Picking a mesh without an object layer map attached will select the mesh node.

Sweet, now I can finish the script.

[bepeg4d]

great, thanks, me too
i was waiting the copyItemTree command
ciao beppe

[Dmi3ryd]

Hello. Thanks for update.

Render time of my project in 1.33 is 10 min 48 sec, in 1.34 is 10 min 26 sec

[funk]

Thanks for the update guys, but untonemapped EXRs are still brighter than they should be. If I compare the EXR to a tonemapped PNG in photoshop, I have to add an exposure adjustment layer and lower it by -1.35 to match the PNG.

I mentioned this in the 1.33 thread. Is this going to be fixed?

[face]

Thanks for the update guys, but untonemapped EXRs are still brighter than they should be. If I compare the EXR to a tonemapped PNG in photoshop, I have to add an exposure adjustment layer and lower it by -1.35 to match the PNG.

I mentioned this in the 1.33 thread. Is this going to be fixed?

EXR use a gamma of 2.2, png one of 1.0.
The result is also correct and the same as in Modo and in Softimage...

face

[face]

When you use a camera response curve on exr´s, the tonemapped one is brighter than the untonemapped because the respopnse curve has only values between 0.0 and 1.0 and the exr is clamped also between 0.0 and 1.0.
The exr is also tonemapped with the curve but you get no intensity information.

The untonemapped don´t use the response curve, so the values are darker, but have values greater than 1.0. It has also intensity.

face

[m.arc.in]

GPU failed after switching to Infochannels Kernel
It works, whith geometric normals, failed with Wireframe mode

It is a very simple scene. I've tested a few other scens. Results are the same.

Octane 1,20 works fine

I've tested only on my laptop with GTX460M


M.

[merid888]

thank you for new version

[funk]

Thanks for the update guys, but untonemapped EXRs are still brighter than they should be. If I compare the EXR to a tonemapped PNG in photoshop, I have to add an exposure adjustment layer and lower it by -1.35 to match the PNG.

I mentioned this in the 1.33 thread. Is this going to be fixed?

EXR use a gamma of 2.2, png one of 1.0.
The result is also correct and the same as in Modo and in Softimage...

face

You have misunderstood. I'm not talking about a gamma difference. I'm talking about a difference in exposure (brightness)

In 1.20 the camera imager controls were not taken into account (exposure/fstop etc) but since 1.30 a new method is used and all these controls affect the saved EXR.

eg. In 1.20 I could use the following camera imager settings:
exposure = 1
fstop = 1
iso = 55
gamma = 2.2
response = LINEAR (no camera response)

The brightness of the output of the tonemapped and untonemapped (once gamma corrected) would match. In other words, photoshop would look just like what I see in octane.

In 1.34 this is no longer the case. I need to adjust the EXPOSURE (not gamma!) of the untonemapped EXR in photoshop by -1.35

I have attached a file showing this is not a gamma problem. You can see the first image from octane, the second is the untonemapped EXR (as shown by default in PS), the third is the EXR with a 1.0 gamma. The second image should look exactly like the first.