OctaneRender™ for LightWave™ 1.5 beta - build 1.31.2 Tweet

[polytek]

I try ed both, in pause and just running, sometimes it reacts, sometimes not....

Poly

[juanjgon]

I try ed both, in pause and just running, sometimes it reacts, sometimes not....

Poly

Currently if IPR is in pause mode or stopped, export functions don't work. Rendering should be working. Anyway I am going to review the code for the next release to see if I could fix this issue. Here in my tests all works fine, but I need to make more tests.

-Juanjo

[polytek]

Thank you,

[BorisGoreta]

I think that limited region rendering is not taking into account camera shift value. So in scenes with camera shift limited region rendering is not possible.

[juanjgon]

I think that limited region rendering is not taking into account camera shift value. So in scenes with camera shift limited region rendering is not possible.

Yes, plugin camera region uses it's own shift system to work, so the camera shift doesn't work. I hope to see soon a native limited region inside Octane API.

-Juanjo

[BorisGoreta]

If I multi select lights and change something while IPR is working IPR restarts rendering for the number of selected lights when it should update all at once

[BorisGoreta]

Is it ok if I create a new node in the node editor like Texture Mixer for IPR to immediatley refresh ? This node is just sitting there and it is not connected to anything. I don't think IPR should reflresh. I have noticed a lot of IPR refreshes when not neccessary.

[juanjgon]

If I multi select lights and change something while IPR is working IPR restarts rendering for the number of selected lights when it should update all at once

Is it ok if I create a new node in the node editor like Texture Mixer for IPR to immediatley refresh ? This node is just sitting there and it is not connected to anything. I don't think IPR should reflresh. I have noticed a lot of IPR refreshes when not neccessary.

Both issues comes from the same functions. When something changes in the scene, Layout sends messages to the master plugin to allow update the Octane scene. Problem is that this messages sometimes are useful and others not, and it is not easy to know if we should update the scene or not ... for example add a node to the node editor send a "change surface" message, but nothing has changed from the rendering point of view because node is not linked yet, and this is something really hard to know.

Anyway I am going to try to fix some of this issues if possible.

-Juanjo

[gigi]

hi, i have a problem, when I launch the Layout this message appears. depends on what?

[juanjgon]

hi, i have a problem, when I launch the Layout this message appears. depends on what?

You are mixing the Octane.dll/Octane.dat files with an older or newer version of the Octane .p plugin file. Please, be sure that you have the Octane.dll/Octane.dat files and the plugin file from the same .zip archive.

-Juanjo