OTOY Forums

Hi people,
Before doing a 2.16 release i want to ask about a problem for me. As you may heard that Fstop and ISO parameters has been deprecated on version 2.15 and 2.16 for Octane Standalone.
Release link:http://render.otoy.com/forum/viewtopic.php?f=24&t=44074
Reason is in quoted text:

Removed the pins "Fstop" and "ISO" from the camera imager node, since they only control exposure which is done already by the exposure pin. The only thing these two pins added was confusion, since some people expected the ability to control the depth of field with Fstop. You can find a Lua script graph that emulates the old behaviour here: viewtopic.php?f=73&t=43944

At this point i have to choose a way to go.

- One is to remove this parameters and converting old scene's camera tag parameters to keep compatibility. I can do it for a next version except 2.16. Also convertion is hard for animated or scripted attributes.

- Two is keeping them by some internal formula. This can cause some confusion on people. Because standalone will not have fstop/iso.

Please write your ideas about this. Thanks

Oleg wrote:What is that in the bottom corners, some sort of red vignette? Showed in wire mode

Red in wireframe is the backface of polygons.

Hey Aoktar, I am having some issues with the Object tag and the object ID render. I have put together a few images to illustrate the issue. Put short it doesn't work.

Having tags on various objects seems to only sometimes work. I have attatched the test scene for you to look at. Each tag has a different mesh number and if I check Object ID it will just separate each individual mesh as a different color. What should happen is that the object and its children with the tag would be one color. and the mesh number should group all of the other object tag groups (with the same number) into the same color or layer.

What it looks like in cinema: How Octane is seeing it using the edit in standalone. And this is how it should look using the layers node. And here is the file:

shawnfrueh,
"mesh no" is not for generating object ids. Only it distributes the objects different groups to provide better performance on plugin.
If meshes are connected to same "scatter" node, they can generate different colors. I think you are trying to get object ids, right?
If so wait a little until 2.20 and a better solution.

aoktar wrote:I think you are trying to get object ids, right?
If so wait a little until 2.20 and a better solution.

Yes I am trying to get a group of objects under the same ID without having to use a connect object to do so as it would immediately bog down the larger scene this test is for.

Is 2.20 a ways out yet?

aoktar wrote:Hi people,
Before doing a 2.16 release i want to ask about a problem for me. As you may heard that Fstop and ISO parameters has been deprecated on version 2.15 and 2.16 for Octane Standalone.
Release link:http://render.otoy.com/forum/viewtopic.php?f=24&t=44074
Reason is in quoted text:

Removed the pins "Fstop" and "ISO" from the camera imager node, since they only control exposure which is done already by the exposure pin. The only thing these two pins added was confusion, since some people expected the ability to control the depth of field with Fstop. You can find a Lua script graph that emulates the old behaviour here: viewtopic.php?f=73&t=43944

At this point i have to choose a way to go.

- One is to remove this parameters and converting old scene's camera tag parameters to keep compatibility. I can do it for a next version except 2.16. Also convertion is hard for animated or scripted attributes.

- Two is keeping them by some internal formula. This can cause some confusion on people. Because standalone will not have fstop/iso.

Please write your ideas about this. Thanks

I think the best solution is to keep same evolution as standalone. Then the first solution.

aoktar wrote:Hi people,
Before doing a 2.16 release i want to ask about a problem for me. As you may heard that Fstop and ISO parameters has been deprecated on version 2.15 and 2.16 for Octane Standalone.
Release link:http://render.otoy.com/forum/viewtopic.php?f=24&t=44074
Reason is in quoted text:

Removed the pins "Fstop" and "ISO" from the camera imager node, since they only control exposure which is done already by the exposure pin. The only thing these two pins added was confusion, since some people expected the ability to control the depth of field with Fstop. You can find a Lua script graph that emulates the old behaviour here: viewtopic.php?f=73&t=43944

At this point i have to choose a way to go.

- One is to remove this parameters and converting old scene's camera tag parameters to keep compatibility. I can do it for a next version except 2.16. Also convertion is hard for animated or scripted attributes.

- Two is keeping them by some internal formula. This can cause some confusion on people. Because standalone will not have fstop/iso.

Please write your ideas about this. Thanks

Yes. Remove them, as they where always a bit awkward in use and the c4d plugin should stay as close to standalone as possible.

atome451 wrote: I think the best solution is to keep same evolution as standalone. Then the first solution.

+1
ciao beppe

Please stay as close as possible to standalone version. I choose first solution.

aoktar wrote:Hi people,
Before doing a 2.16 release i want to ask about a problem for me. As you may heard that Fstop and ISO parameters has been deprecated on version 2.15 and 2.16 for Octane Standalone.
Release link:http://render.otoy.com/forum/viewtopic.php?f=24&t=44074
Reason is in quoted text:

Removed the pins "Fstop" and "ISO" from the camera imager node, since they only control exposure which is done already by the exposure pin. The only thing these two pins added was confusion, since some people expected the ability to control the depth of field with Fstop. You can find a Lua script graph that emulates the old behaviour here: viewtopic.php?f=73&t=43944

At this point i have to choose a way to go.

- One is to remove this parameters and converting old scene's camera tag parameters to keep compatibility. I can do it for a next version except 2.16. Also convertion is hard for animated or scripted attributes.

- Two is keeping them by some internal formula. This can cause some confusion on people. Because standalone will not have fstop/iso.

Please write your ideas about this. Thanks

Keeping in line with Standalone is nice and everything, and it's certainly going to be simpler to remove those pins, but in doing so you now don't have any *actual* control over your camera. How am I supposed to match my 3D to a back plate if my photographer says "Here is my ISO, F-stop, Exposure, etc" and all I can do is drag a single slider back and forth? Doesn't make any sense.

I'm all for simplifying, but if there was a way to keep the added control in there for people who might deal with physical photography as well as digital, that would be the best solution.