OctaneRender™ 2.1 for LightWave™ - Daily builds

Thu Oct 30, 2014 10:46 pm

If texture image node is not directly connected to the texture (but multiplied with somethig first ) input node of environment texture Octane disregards image rotaion fro daylight node.

Thu Oct 30, 2014 11:09 pm

Changing light type from LW color to black body crashes Layout while IPR is rendering. Actually anythinh I try to do with this light crashes Layout.

I will collect example scenes and send later.

Fri Oct 31, 2014 1:14 am

Well, it happens with this scene I am working on at the moment.
I have the same version because otherwise I wouldn't be able to use the node. It would report wrong version.

I thought that export does not export animation so how can I test sequence rendering in the standalone with this scene ?

The sequence always stops at 146/150 samples on the first frame and I can close IPR and continue working.

juanjgon wrote:
BorisGoreta wrote:F10 sequence rendering leaves me hanging around 97% of the first frame every time. If I disable network node it renders normally.
With all your scenes or only with one?

Please, check that you have the same version of the Standalone in the nodes and the plugin. Also you could test the network rendering from the Standalone in your main workstation, not using the plugin, to see if you have the same problem (you can export an .orbx file from the IPR to test the scene)

Anyway I will test the network rendering again tomorrow in the office.

-Juanjo

Fri Oct 31, 2014 8:48 am

BorisGoreta wrote:Well, it happens with this scene I am working on at the moment.
I have the same version because otherwise I wouldn't be able to use the node. It would report wrong version.

I thought that export does not export animation so how can I test sequence rendering in the standalone with this scene ?

The sequence always stops at 146/150 samples on the first frame and I can close IPR and continue working.

You can export only this first frame and test it as a still image in Standalone to see if the network rendering can finish it.

-Juanjo

Fri Oct 31, 2014 8:51 am

BorisGoreta wrote:Changing light type from LW color to black body crashes Layout while IPR is rendering. Actually anythinh I try to do with this light crashes Layout.

I will collect example scenes and send later.

Yes please. If you have a example scene with this problem send it to me. I am testing the Octane lights here with my scenes and all is working fine.

-Juanjo

Fri Oct 31, 2014 10:52 am

Standalone also stops at 146/150 with network rendering.

juanjgon wrote:
BorisGoreta wrote:Well, it happens with this scene I am working on at the moment.
I have the same version because otherwise I wouldn't be able to use the node. It would report wrong version.

I thought that export does not export animation so how can I test sequence rendering in the standalone with this scene ?

The sequence always stops at 146/150 samples on the first frame and I can close IPR and continue working.
You can export only this first frame and test it as a still image in Standalone to see if the network rendering can finish it.

-Juanjo

Fri Oct 31, 2014 11:05 am

BorisGoreta wrote:Standalone also stops at 146/150 with network rendering.

Ok, thanks Boris, so we have a problem with the Octane network rendering, it is not an plugin issue. Do you have a basic scene with this behavior to test it here?

-Juanjo

Fri Oct 31, 2014 11:08 am

I have a 1.2 GB scene coming your way.

Sat Nov 01, 2014 8:56 pm

Could it be possible to get the frame render time to show the actual render time? I mean in LW image viewer after F9 render the time is now always 0.0

Sat Nov 01, 2014 11:03 pm

atnreg wrote:Could it be possible to get the frame render time to show the actual render time? I mean in LW image viewer after F9 render the time is now always 0.0

The LW SDK doesn't have a function to set the render time in the render window. There is a feature request for this issue, but currently it is not possible.

-Juanjo