OctaneRender™ Standalone 1.21

[kavorka]

I have the official plugin for Blender as well but haven't starting using it in my workflow for various reasons (have an ongoing project of 1600 images that will be several months more and I don't want to change things mid way through, nothing against the plugin). I was just bringing it up because it might be a small change that will bring back functionality, it might also be something that needs to be modified in the unofficial plugins. Either way, there needs to be some kind of fix (either in Octane or by the devs for those plugins) or a lot of people wont be able to use the new Octane.

[gah5118]

I have the official plugin for Blender as well but haven't starting using it in my workflow for various reasons (have an ongoing project of 1600 images that will be several months more and I don't want to change things mid way through, nothing against the plugin). I was just bringing it up because it might be a small change that will bring back functionality, it might also be something that needs to be modified in the unofficial plugins. Either way, there needs to be some kind of fix (either in Octane or by the devs for those plugins) or a lot of people wont be able to use the new Octane.

same boat with the workflow. It seems more like a bug though.

[roeland]

The camera target command line argument is broken in this release, it will be fixed in the next release.

--
Roeland

[r-username]

The RGB values do not match.
It would seem that the values in the pop-up are correct, FF8000 = Red 1.000 G 0.500
and not Red 1.000 and Green 0.218

see attached image

[roeland]

This is because Octane uses linear workflow: http://render.otoy.com/forum/viewtopic.php?f=21&t=33214

The color picker allows you to enter colors in sRGB color space instead of linear space, so when you copy colors from other applications the color you will get in Octane is closer to the color you got in the other applications. The node itself always displays the linear value.

--
Roeland

[Zay]

HDRI environment seems to be locked to Z rotation only (UV/3D transformation).

[smicha]

We can populate the pins of the object layer map node with some default object layer nodes if that would help you.

I'm not sure to understand what you mean.
My propose was something very simple, like this:


If you CTRL+click the eye, only that object will be visible, everything else will be hidden.
And then have the Camera/Shadow visibility options in the OBJ properties.
Isn't that easier?

I totally agree with Rikk - adding object layer map and object layer just to turn off visibility is way too messy. It is much easier to unpin a node from a geometry group. The solution with the eye icon looks very neat. Guys please add such a solution (if this is possible).

[smicha]

Guys,
I just want to thank you again for your fantastic work. I just tried how image displacement and instancing work. It is truly amazing that copying the same image texture node is still visible as one texture , which is a huge vram saver. I've been waiting for this for more than a year.

Here is also my suggestion to clean some unwanted nodes when exactly the same texture is applied. One more input would be required for projection in material map.

[steveps3]

I've got a bit of a problem. As you can see I have tons of geometry yet I have zero render. The screen is completely blank. I can move the camera around and it stays blank. This is an export from blender. Oddly if I import the scene directly into Octane then it works so I am going to assume that it is something to do with the command line that is not working.

[FooZe]

Hi Steveps3,

It could be a camera placement issue.
Try some of the preset views (fourth icon from the left in the viewport toolbar) to see if that brings the obj into view...

Thanks
Chris.