OctaneLW 3 crashing lightwave when using IES

[Draydin_r]

Hi Guys,

I don't know whats going on but the attached IES files are crashing lightwave when applied to an octane light (texture mat + emitter in material panel works fine!) before even getting to IPR. Is this plugin problem/lightwave problem or is it the IES files?

If someone knows whats up and has a solution this would really help! Currently, I 'm currently working around that by building my distance lights out in modeler and and applying my emitter through material. The demo IES files that ship with the octane demo scenes don't have this issue.

Draydin_r

[juanjgon]

Can you send to me the scene with this problem? I am testing your IES files here and they work fine.

Thanks,
-Juanjo

[Lewis]

Could it be old bug (now fixed in 3.0.4) when path for loading IES is too long ?

[juanjgon]

Yes, can be something related with a long path/filename. I think that now this problem is fixed in the Octane 3 builds.

-Juanjo

[Draydin_r]

Unfortunately, not. The build I was using was the one available at the time of the sending. I currently can't send the scene that I was building (client ixnayed that) so I had to use a model and material setup to get it working. (sorry for the late responce, work was nuts for the last couple weeks!)

Also, I've been noticing bizarre video card crashing with LW 2015.3 and Octane 3 Builds, but not with octane 3 standalone builds. Octane 3 standalone can run for hundreds of hours no problem , LW plugin causes the primary video card running the desktop to lockup, artifact and continue rendering (so no crash report, as of right now I'm not certain if it is a LW error or Octane Plugin Error :S ) requiring me to hard boot the computer. This has happened 4 times now.

As a result I've been having to send all renders to standalone. Unfortunate, but functional.

[juanjgon]

Unfortunately, not. The build I was using was the one available at the time of the sending. I currently can't send the scene that I was building (client ixnayed that) so I had to use a model and material setup to get it working. (sorry for the late responce, work was nuts for the last couple weeks!)

You are right, the last build can have problems with large IES file paths in the Octane light (>300 characters). It will be fixed in the next build.

Also, I've been noticing bizarre video card crashing with LW 2015.3 and Octane 3 Builds, but not with octane 3 standalone builds. Octane 3 standalone can run for hundreds of hours no problem , LW plugin causes the primary video card running the desktop to lockup, artifact and continue rendering (so no crash report, as of right now I'm not certain if it is a LW error or Octane Plugin Error :S ) requiring me to hard boot the computer. This has happened 4 times now.

I have never seen a problem like this, but anyway perhaps the problem is that one of the GPUs used for rendering is also used for display, and Octane is running out of memory because the Layout is using some GPU memory for the OpenGL viewports. Standalone doesn't have this problem, it doesn't need OpenGL buffers for the viewport (only a small buffer for the image data).

I think that if you load your scene with all the Layout viewports disabled, or you disable the display GPU, the scene should be rendered without problems. You could even try to render your scenes using LWSN, that doesn't fill OpenGL data in the GPUs at all.

-Juanjo

[Draydin_r]

I'll give it a try when I get the chance, though the only thing to mention is that they display GPU is not be used for the renderer. Hence why the render continues without crashing when the error pops up.