OTOY Forums

Animation rendering is not advancing after first frame is finished if network nodes are used. This bug happened before also, then it got fixed, now is back again.

ryanroye wrote: 1) Plugging in the environment node always crashes Octane. If IPR is on, it crashes immediately, if I hit f9 to render, it crashes if the environment node is plugged in.

2) Displacement is very unstable and crashes my video card. Specifically, when rendering or using IPR with displacements, the screen freezes for about 10 seconds, then I get this error:

"The NVIDIA OpenGL driver detected a problem with the display driver and is unable to continue. The application must close. Error code: 3.

I am testing the environment node here and all works fine so far. I don't have here in my laptop the last NVIDIA drivers, I will update them tomorrow, but at least with the 335.23 all works without problems. Do you have this problem even with the demo scenes?

About the displacement problems, this behavior usually means that you have a very high displacement distance values, that makes the render too slow and sometimes unstable. Please, try your scene with a very low displacement value (0.001 for example) and increase this value until you get the right displacement. If you have this problem even with a low displacement distances, there we could have other problem.

Do you have this problems only with the latest daily build?

-Juanjo

BorisGoreta wrote:Animation rendering is not advancing after first frame is finished if network nodes are used. This bug happened before also, then it got fixed, now is back again.

Boris, do you have this problem only with the last 2.6.1 daily build? ... perhaps we have a new bug in this release. Do you get any error message in the render nodes?

-Juanjo

There are no error messages it just stops rendering and I have to press abort. I will test it with previous buids.

BorisGoreta wrote:There are no error messages it just stops rendering and I have to press abort. I will test it with previous buids.

yes, please, try also with other scenes, perhaps we have a problem with the scene you are working now.

-Juanjo

juanjgon wrote:Do you have this problems only with the latest daily build? -Juanjo

I handed my scene to someone else and they said they are experiencing no crashing or problems with the scene, so I have some troubleshooting to do on my part; at this point it's unlikely the issue is entirely specific to Octane.

ryanroye wrote: "The NVIDIA OpenGL driver detected a problem with the display driver and is unable to continue. The application must close. Error code: 3.

i experienced for one week this problem on my workstation: after unplug/invert the 780ti, such a bug no more happened: perhaps a bad connection or a bios/motherboard bad combinaison... so it was an hardware problem for me... ( on win64 platform )

is your PC cold enough when cuda rendering ?

cheers

ryanroye wrote:

juanjgon wrote:Do you have this problems only with the latest daily build? -Juanjo

I handed my scene to someone else and they said they are experiencing no crashing or problems with the scene, so I have some troubleshooting to do on my part; at this point it's unlikely the issue is entirely specific to Octane.

Please, test Standalone to see if with it you have also this problems. I am going to update my driver ASAP to see if with it there is some kind of problem.

-Juanjo

juanjgon wrote:

ryanroye wrote:

juanjgon wrote:Do you have this problems only with the latest daily build? -Juanjo

-Juanjo

Still need to test other builds to compare results.

I tried standalone and I could not get displacements or the environment node to crash it at all, so that at least rules a few things out.

ryanroye wrote: I tried standalone and I could not get displacements or the environment node to crash it at all, so that at least rules a few things out.

Please, download again the .zip file with the last daily build and be sure that you have have the last Octane.dll and Octane.dat files in your LightWave/bin folder from the .zip archive. Perhaps you are using an old Octane.* files (or a corrupted ones) with the last plugin .p file.

-Juanjo