OctaneRender™ Standalone 1.35

[ROUBAL]

I think I found a bug in the mix node.

I'm mixing 2 specular materials. one with scattering and the other was supposed to just be for reflection. However, when the mix slider is 100% the specular for the opposite material is used. IOW the second material's specular value is used with the rest of the first materail, and vice versa when at 0%

Here's the example material and mix node - did I do something wrong? or is this really a bug?

I am not the most experienced to answer, as I have always been clumsy with nodes, but I have looked at your file and I think that it is normal (same behaviour as previously, I mean), but I have never understood why the slider to zero correspond to the second material and the slider to 1 correspond to the first one. It is counter intuitive and confusing at use, even when you know how it works.

Well, I have done my first animation trials with alembic exports from Blender, and I encounter two problems :

1- The first one is that I get a big jitter in the exported camera. First I thought that it was due to the fact that the camera whas moving while tracking an object with a constraint. I thought : maybe alembic doesn't know how to use constraints. So I deleted the constraints and keyframed the camera without using constraints : still shaky camera and random motion blur due to the jitter.
So, I tried again with a completely static camera without any animation, and this time it was steady.

So, is there something specific to know for camera setting when using alembic export ?

2- Each time I reload an alembic file I loose all my materials settings. Is there a way to transfer easily the materials from an obj or an alembic node to an other alembic node ? Currently, I have to copy the node contents material by material each time I modify the scene !

Thanks in advance.

[roeland]

1: Octane interpolates linearly between the keyframes stored in the Alembic file. It depends on what gets written in the Alembic file if the camera in Octane moves smoothly or not. Usually an exporter just writes the camera position for every frame so Octane doesn't do any interpolation. If you are using the Octane for Blender plugin you should ask on the Blender forum how it works.

2: A geometry archive keeps existing material settings, just like a mesh node when you reload it, unless all the material names have changed. The workflow should be the same as when working with OBJ files (reload existing node to import the new geometry).

--
Roeland

[ROUBAL]

1: Octane interpolates linearly between the keyframes stored in the Alembic file. It depends on what gets written in the Alembic file if the camera in Octane moves smoothly or not. Usually an exporter just writes the camera position for every frame so Octane doesn't do any interpolation. If you are using the Octane for Blender plugin you should ask on the Blender forum how it works.

2: A geometry archive keeps existing material settings, just like a mesh node when you reload it, unless all the material names have changed. The workflow should be the same as when working with OBJ files (reload existing node to import the new geometry).
-- Roeland

Thank you Roeland. I will ask in the plugin section. I have rendered with the plugin Inside Blender and the camera movement is fluid. It happens only in Standalone with an alembic export from plugin.

For the materials, each time I load a new alembic file (with same name with updated geometry with unchanged materials) the materials are lost. I will experiment again...

[cakeller98]

I think I found a bug in the mix node.
I am not the most experienced to answer, as I have always been clumsy with nodes, but I have looked at your file and I think that it is normal (same behaviour as previously, I mean), but I have never understood why the slider to zero correspond to the second material and the slider to 1 correspond to the first one. It is counter intuitive and confusing at use, even when you know how it works.

I have been trying to recreate the condition - as of now, I can't re-create it. Even with the original file. Guess I was wrong.

[smicha]

I just found a very strange behavior of the low render priority and the infochannel kernel set to wireframe. Entire image in the preview window is getting brighter and brighter. Can you confirm such behavior?

PS. What is the maximal precision (in terms of number of digits) in obj files that Octane reads? Does it matter that I can turn on double precision in TITAN?

[face]

I just found a very strange behavior of the low render priority and the infochannel kernel set to wireframe. Entire image in the preview window is getting brighter and brighter. Can you confirm such behavior?

PS. What is the maximal precision (in terms of number of digits) in obj files that Octane reads? Does it matter that I can turn on double precision in TITAN?

The API uses only float, so a use of doubles will then cropped inside Octane.

face

[smicha]

The API uses only float, so a use of doubles will then cropped inside Octane.

face

Cropped to 8 digits?

[FrankPooleFloating]

OCS files are just XML and can be opened in any text editor. You can glean a lot from just pokin' around in there for a bit.

[merid888]

hi roeland, i use the native export .obj of max and the plugin alembic

[roeland]

I just found a very strange behavior of the low render priority and the infochannel kernel set to wireframe. Entire image in the preview window is getting brighter and brighter. Can you confirm such behavior?

PS. What is the maximal precision (in terms of number of digits) in obj files that Octane reads? Does it matter that I can turn on double precision in TITAN?

I can't reproduce the problem with the wireframe mode here.

The floating point precision allows 7 or 8 decimal digits of precision.

--
Roeland