Version 2.23.2 - R6.2 (15.07.2015) - Obsolete stable

[aoktar]

Hi,
i can't find the related post. I saw a question about TR and license. There is a picture to show how can we activate plugin from TR client.

[Gumz]

I have some new ideas about LV in this period. Maybe lot of to do. But i wish to jump to next level in interactive rendering and workflow. Maybe good to hear some ideas/opinions before to dive.

The constant updating LV is really a huge step forward in workflow and thank you for that.
I just had a chance to play a bit with Arnold and one thing I noticed was the updates to IPR window happened while I was dragging sliders and not just when I let go of the mouse.

It's a small thing, but you asked for ideas regarding interactivity and it makes Arnold feel a bit more responsive

[aoktar]

I have some new ideas about LV in this period. Maybe lot of to do. But i wish to jump to next level in interactive rendering and workflow. Maybe good to hear some ideas/opinions before to dive.

The constant updating LV is really a huge step forward in workflow and thank you for that.
I just had a chance to play a bit with Arnold and one thing I noticed was the updates to IPR window happened while I was dragging sliders and not just when I let go of the mouse.

It's a small thing, but you asked for ideas regarding interactivity and it makes Arnold feel a bit more responsive

Are you meaning object's parameters? I have disabled it in latest version by accidently. I'm also checking ipr. It seems nice in starting but not so nice when dive to deep editing.

[Gumz]

Are you meaning object's parameters?

Yes. It works when you adjust stuff in the viewport, but not when adjusting object properties in the attributes window.
Let say you are adjusting power and gamma of an HDRI in an ImageTexture node, the light doesn't update until you let go of the mouse.
It does seem to update instantly with certain things though, if you for an example change power directly in an environment tag node.

But like I said, it's no big deal. I love the way it works now.

[MoGrafik]

Just a quick crash report: Had a crash when rendering using the render queue. This happened it previous versions of Octane, but was then fixed. Seems like it might be back. Using Win 8.1 and c4d R16.

Also, Auto mode is great for small scenes, but it drove me crazy until I found out about it when working on a big scene. Dragged things to a halt! I think I'll turn it off by default.

[aoktar]

Just a quick crash report: Had a crash when rendering using the render queue. This happened it previous versions of Octane, but was then fixed. Seems like it might be back. Using Win 8.1 and c4d R16.

Also, Auto mode is great for small scenes, but it drove me crazy until I found out about it when working on a big scene. Dragged things to a halt! I think I'll turn it off by default.

That's what i wrote in notes. It related with generated node counts. Please read again the following line.

- Automatic mode for check geometry. It's for best experience for real interactive editing and rendering. It will make all objects movable. But be aware of limitation of object counts. Due of making all objects movable can cause high node counts. As you may know that Octane encapsulate all nodes in nodegraphs. There is a limit for count of nodes for each nodegraph as main node graph. It's about 32k nodes per nodegraph. So if you exceed 10k objects + material nodes, this can cause crashes.

[dinf]

Hey aoktar

This version has changes for some parameters which are unit aware. This can cause different results on material outputs. So please don't switch your version in middle of a project.

Can you specify them? I have to switch a huge landscape with distant shots and close ups to 223.2 and would like to know where to look for different material outputs. Thanks!

[indexofrefraction]

it got so silent here .. summer holidays?

[dinf]

I'm hoping very well they all are working on Octane III

[aoktar]

I'm hoping very well they all are working on Octane III

I hope so.