OctaneRender for Carrara 3.08.03.42[Stable and Test]

[Sighman]

Hi Simon,
Are there any other files I can provide for this? I realized the HDRI may not have come through in my export.

Can you post or PM me the HDR.

Edit: This looks like an Octane problem and not a plugin issue. However, I have forwarded the issue on to the Octane team and hopefully they will fix it or let me know what needs to change in the scene to fix it.

[Sighman]

Hi Simon,
Are there any other files I can provide for this? I realized the HDRI may not have come through in my export.

Can you post or PM me the HDR.

Edit: This looks like an Octane problem and not a plugin issue. However, I have forwarded the issue on to the Octane team and hopefully they will fix it or let me know what needs to change in the scene to fix it.

It looks like the problem is that your material normals are set to black. If you don’t want to provide a normal map then you should clear ('none') the normal channel. I’ll make sure the channel is empty by default, and yes, this is a new requirement for 3.8+.

[protovu]

Thank you, Simon.
I will give it another try and let you know.

[protovu]

Yes! Thanks.

Putting "none" in the normal channel does the trick.

One thing that threw me a little:
Directly after switching to "none", the Octane viewport blinks, as if it is refreshing. But it is not really refreshing and the render does not change.
It is only after I specifically refresh the Octane viewport that the results show themselves.

This same false refresh happens with other Material changes, like updating a bitmap or opacity map.

I wonder if anyone else is experiencing this?

Thanks again,
Rick

[Sighman]

Yes! Thanks.

Putting "none" in the normal channel does the trick.

One thing that threw me a little:
Directly after switching to "none", the Octane viewport blinks, as if it is refreshing. But it is not really refreshing and the render does not change.
It is only after I specifically refresh the Octane viewport that the results show themselves.

This same false refresh happens with other Material changes, like updating a bitmap or opacity map.

I wonder if anyone else is experiencing this?

Thanks again,
Rick

Glad it fixed your issue.

The render should restart after a shader change. I'll look into it...

[protovu]

Thank you, Simon.

[protovu]

Hi Simon,
I am curious regarding rendered file size and samples. The attached shows two file sizes, the smaller file size is rendered at 10X the samples of the larger file size.
The samples were done at 10, 100, and 1000 with the 10 samples render about twice the size of the 1000.

Is this normal? What is at work here? Anything I should adjust?

Thanks,
Rick

Win 7
dual xeon
4 Nvidia Cards , 1080, 2 Titan, 970

[Sighman]

The fewer the samples the more noise is in the scene. PNG uses a simple lossless compression algorithm. The more variation there is between neighboring pixels, the less efficient it becomes. If you saved to a tiff or bmp the file size would be consistent (and large) since those formats don’t use compression. Basically, the longer you bake, the more consistent the image becomes and the better the compression efficiency.

[protovu]

Thanks, Simon.

If we could bottle all I don't know we'd be millionaires.

[rashadcarter]

Sighman please forgive me for asking but is there any eta on a Octane 4 plug-in for Carrara? I'm loving the improvements including the denoiser and AI light as well as the much much faster scene navigation and loading between frames and the Universal material. I really want to avoid using the standalone but for some of the tools it is quite attractive at the moment. Any feedback is greatly appreciated. thanks, Sighman!