OTOY Forums

Jaunigo i swear this time i have all set to linear but notwithstanding that i bumped again into a ram ( not vram) problem,,, at every rendered frame ram usage grow up until system run out of ram and chrashes... that problem dont appeare when using ipr ... i am on a deadline i need an urgent answer,,,,,,

So do you have a problem with the computer CPU RAM? ... try to render the scene in full reload mode to see if this help.

It is hard to say what could be problem. If there is a memory leak in the CPU RAM the problem can be in LightWave or in the plugin.

Please, I need more information to know what could be problem, or the scene to test it here.

-Juanjo

I have a same problem with final render! LW starts to consume more and more memory and then crashed when it reaches my 32 gb limit. Scene is quite complicate, with realflow water included. IPR works just fine.2015.2, win7ent, Octane 2.23.2.1.

kostache wrote:I have a same problem with final render! LW starts to consume more and more memory and then crashed when it reaches my 32 gb limit. Scene is quite complicate, with realflow water included. IPR works just fine.2015.2, win7ent, Octane 2.23.2.1.

I am going to need more information or the scene file to know the source of the problem. Are you rendering in update or in full scene reload mode? ... perhaps the problem is the realflow simultion, so do you have the same problem if you remove it from the scene?

-Juanjo

I've found a problem - uncheck "Enable deformation MB"! But I think the issue is still actual, because RF Importer plugin loaded right into Deform tab as Displascemet plug-in and I think it's requiered "Enable deformation MB" ON to use water vertices velosity info. Is it right?

kostache wrote:I've found a problem - uncheck "Enable deformation MB"! But I think the issue is still actual, because RF Importer plugin loaded right into Deform tab as Displascemet plug-in and I think it's requiered "Enable deformation MB" ON to use water vertices velosity info. Is it right?

As far I know the only way to render the motion blur from the Realflow simulations is to use the multipass motion blur:
http://render.otoy.com/manuals/Lightwave3D/?page_id=400

LightWave doesn't understand the concept of "velocity" vectors, and the Octane plugin can't get this information from the Realflow plugin. Only a multipass technique can render MB from this kind of simulation plugins.

Anyway if you have a memory leak enabling the deformations MB, then we have a bug in the Octane plugin that I should fix. If you can send to me a sample scene with this problem, please let me know. You can send it to [email protected]

-Juanjo

No, it's possible to get RF velocity vectors info into LW for water MB over next limit plug-in manager, but you need to check "Enable deformation MB" on for it! My scene is quite big, but I'll try to reduce it for sending. B.t.w., if you load only water to an empty scene via next limit plug-in manager and set "Enable deformation MB" to "on" render works.

Ahhh, Ok. Really I don't know the internals of the Realflow plugin, and I was thinking that the deformations MB can't compute the velocity vector from this kind of simulation plugins.

Yes please, I don't have the Realflow plugin, and could be very helpful for me a sample scene with the memory leak problem.

-Juanjo

hi the problem is still here yet but now ....ì have onother one...
bought a 980ti besides my old titan ... if i render with just one of them ipr goes ok, if i render using both it crashes.....

Final part of render log
00:02:33 (0153.86) | Scene loaded
00:02:33 (0153.86) | Render resolution: 900 x 450
00:02:33 (0153.86) |
00:02:33 (0153.86) | IPR: scene loaded
00:02:33 (0153.86) | IPR: CalculateAllNormals 0
00:02:34 (0154.57) | IPR: Enable IPR events processing
00:02:34 (0154.57) | IPR: init rendering
00:02:34 (0154.57) | IPR: set IPR camera options
00:02:34 (0154.57) | IPR: set image callback
00:02:34 (0154.57) |
00:02:34 (0154.57) | Render scene, set renderTarget and update
00:02:34 (0154.57) | ... first update
00:02:34 (0154.57) | ... setRenderPriority
00:02:34 (0154.57) | ... RenderPriority set to 0
00:02:34 (0154.57) | ... set Motion Blur parameters
00:02:34 (0154.59) | ... setRenderTargetNode
00:02:58 (0178.07) | ... second update
00:02:58 (0178.07) | ... isRenderingPaused
00:02:58 (0178.07) | Render setup Ok.
00:02:58 (0178.07) |
00:02:58 (0178.07) | IPR: enter into the rendering loop
00:03:00 (0180.54) * OCTANE API MSG: CUDA error 2 on device 0: The API was unable to allocate enough memory to perform the requested operation.
00:03:00 (0180.54) * OCTANE API MSG: -> failed to allocated device memory
00:03:00 (0180.55) * OCTANE API MSG: CUDA error 2 on device 0: The API was unable to allocate enough memory to perform the requested operation.
00:03:00 (0180.55) * OCTANE API MSG: -> failed to allocated device memory
00:03:00 (0180.57) * OCTANE API MSG: CUDA error 2 on device 2: The API was unable to allocate enough memory to perform the requested operation.
00:03:00 (0180.57) * OCTANE API MSG: -> failed to allocated device memory
00:03:00 (0180.59) * OCTANE API MSG: CUDA error 2 on device 2: The API was unable to allocate enough memory to perform the requested operation.
00:03:00 (0180.59) * OCTANE API MSG: -> failed to allocated device memory