OctaneRender for Carrara 3.0.12.10[Beta]

[Sighman]

WARNING: This version has had limited testing. Use at your own risk!

Changes in 3.0.12.10

• Re-Implemented support for hair groups. (see notes)
  Set Invert Absorption on Medium nodes to false when loading old scenes. (see notes)
  Properly set Motion Blur on OpenVDB import settings.
  Properly set surface brightness and illumination on Emissive Textures.

Changes in 3.0.0.9

• Fixed visibility tracking in render room.

Changes in 3.0.0.8

• Integrated with Octane SDK 3.0 Beta 1
• Added new imager option (disable partial alpha).
• Added new SubDiv options (adaptive).
• Added new Device option (use for tonemapping).
• Added new velocity options to VDB import dialog.
• Support new activation behavior.
• Added preference to set number of digits to use for animation sequence numbers.
• Fixed issue where Viewport would not open on some systems.
• Fixed display of backgrounds and atmosphere on initial/single frame in render room.
• Fixed visibility tracking in render room.
• Fixed potential crash when starting a render in the render room.
• Fixed animated camera not exporting to .orbx
• Fixed hang that may occur when rendering an animation in the render room if nothing in the scene changes.
• Fixed crash that can occur when saving a scene if the Octane Renderer is set in the render room.

Changes in 3.0.0.7

• Attempt to fix inability to open Octane Viewport on some systems.

Changes in 3.0.0.6

• Added Render Room rendering. (See notes)

Quick Notes:
Invert Absorption
3.0 introduced a new flag to medium nodes called Invert Absorption. The default for this flag is true unless you load an old scene. If you load an old scene then the Invert Absorption flag should now default to false. However, there is a side effect due to the late implementation of this fix. Loading any scene that you saved prior to 3.0.12.10 will reset the Invert Absorption flag to false even if you wanted it set to true. You will need to go back into your medium nodes are reset it to true if you need to. Sorry for this inconvenience, but it is beta software after all.

Hair Groups
I have changed the way you assign shaders to hair groups. There is no longer a popup and you will not be shot into the material room when you change the shader. I think the new effect is straight forward to use. Just pick a hair group and then pick the shader you want or create a new one. You can edit the currently select shader with one of the two edit buttons if you want to. All changes take effect immediately.

Render Room Rendering
You can now render from directly inside the render room. To do so you need to switch the Renderer to Octane Renderer. The 'Enable' option does nothing so you can ignore it. Just verify your output settings and click Render. If the Octane Viewport or Settings is open then they will be closed when you start a render in the render room. I have not tried the batch queue so please let me know if it is working or not.

There are limitations when using the Render Room to render:

• Saving EXR, HDR, or Deep Images are not supported at this time.
• Camera and object motion blur is not supported at this time.
• Render Passes are not supported at this time.
• Abort only aborts rendering when the current frame is finished. The only way to stop a single frame render before max samples is reached is to kill Carrara from the Window's Task Manager.

Known issues (to be fixed in a later release):

• There is no statistical feedback. No estimates, no pixel per second, just the current frame of an animation.
• If you override the Camera position in the Octane Viewport then the rendered image in the render room will not be correct.

As usual, please let me know if you find ANY other issues.

ATTENTION: This version is based on Octane 3.0. Make sure your NVIDIA graphics drivers is up to date.

Happy Rendering...

Download Links:
OctaneRender for Carrara (64-bit) 3.0.12.10

[EddyMI3D]

Thank you! Great!

[protovu]

Thanks, Simon. I will give it a go.

[protovu]

Hi Simon,
Seem to encountered a gremlin when trying to launch the new preview. Please see attached.

[Sighman]

Hmm, Never tested preview. Always went straight to render.

However, I cannot reproduce this issue. What exactly are your steps to get Carrara to crash?

[protovu]

Hi Simon,
Actually, by "Preview" I was referencing the forum subject header, "OctaneRender for Carrara 3.0.0.6 [Preview]", and its associated download version,
which I installed.


The SystemInvalid....screen popped up when I launched Octane the usual way, Ctrl+Shift+R, or through the Edit dropdown equivalent command.

My nvidia driver is up to date. 10.18.13.6472

Sorry for the confusion. Oddly, what happened when seeing the pop up was not a crash in the usual sense. Simply, Octane would not launch. Though I did not test it much, and quickly
reverted to 2.25.0087, Carrara seemed normal.


Rick

[Tugpsx]

Works fine for me, I have 3 cards one for interface 2 others for rendering.

[protovu]

Hi Simon,
Apparently, Ctrl+Shift+R , for me anyway, does not work - gives me the previous pop-up, but once selecting the Octane renderer in the render room (as you instructed) , Ctrl+R does launch an Octane render.
As you indicated, the render viewport has no stat. data.
Also, there is no way to select the focus point, and no way to access the Live Data Base, area render, and anything else nested in the normal Octane render viewport.

I am wondering if other users are able to access the traditional Octane viewport, and optionally use the Carrara Render room (absent the normal Octane selections). This would allow
normal fine tuning while working, and later batch queue rendering.

Forgive my ignorance on this regarding how difficult it may be to code: If possible, it would be terrific to avoid the Carrara render room altogether, and have the batch queue option nested in the traditional Octane render viewport. This would allow the workflow Octane provides, and scheduled renders.

Finally, - getting Octane to work through the Carrara Render room seems to have killed the viewed file. That is, once viewed through Octane via Carrara Render Room, and then reverting to Octane 2.250087, the file will not open, and the provided error message appears. This eliminates an option I was considering: work in 2.25 for normal Octane workflow, then install 3.0 to batch render at the end of the day.

Thank you,
Rick

[Sighman]

The render room rendering is only meant for 'final' rendering and batch queue rendering. It also allows you to render to an avi which you cannot do with the viewport. It certainly does not have any of the dynamic options of the viewport nor is it meant to. You should not use ctrl-shift-R from the render room, it should be disabled. Only open it from the assembly room. The octane viewport should be fully usable at any time except when rendering in the render room.

I cannot implement batch queues any other way. The API does not support loading a scene from a file, at least I could not get it to work without crashing.

[protovu]

Actually, from the very start, I was attempting to access the Octane viewport through the Assembly Room, not the Render Room.

Just re-installed 3.0.0.6 to check a 3rd time. Same result:
The System.Invalid pop-up with Crtl+Shft+R, or using the Edit>drop down Octane launch command.

From the Assembly Room, this pop_up comes up regardless of whether the Octane renderer is selected in the Render Room, or not.

I did the test with a fresh file, with a single sphere. The fresh file, does render with Octane using the Crtl+R command, but the hdri background did not show. (Might have missed a setting?)

The test file (attached) is not backward compatible with Octane 2.25.

Suggestions? Trying to figure this......my Carrarra behaves well, and my Octane 2.25 behaves well. No one else has reported lack of access to the new 3.0.0.6 viewport?

Thank you,
Rick