another ram usage problem
Moderator: juanjgon
I am sorry for this problem. I am going to try to reproduce here your original realflow scene with the memory leak problem, but at the end without the full scene here to test it, it is really hard to know the source of the problem.
Could be a hardware issue. Do you have a chance to test your scene in other system?
-Juanjo
Could be a hardware issue. Do you have a chance to test your scene in other system?
-Juanjo
Ok. I can reproduce the realflow memory leak problem here. With the deformations MB enabled, Octane consumes all the available CPU RAM while updating the scene in the GPUs until crash.
Something is broken in the motion vectors that the Octane plugin is receiving from the Layout and Realflow plugin. Perhaps this is why all the RF and Octane users are rendering the scenes with the multipass MB enabled, not with the native Octane deformations MB.
I will try to isolate the problem to see if it can be fixed. I am not sure if the Octane plugin is going to be able to get valid and not broken motion vectors from the realflow simulation object. As I say before, the LightWave internal data structures doesn't understand the concept of motion vector, and I am not sure how the Layout is handling this information for the LW native render engine.
Meanwhile as workaround I think that should try to render the scene with the Multipass MB technique, disabling the native Octane MB.
-Juanjo
Something is broken in the motion vectors that the Octane plugin is receiving from the Layout and Realflow plugin. Perhaps this is why all the RF and Octane users are rendering the scenes with the multipass MB enabled, not with the native Octane deformations MB.
I will try to isolate the problem to see if it can be fixed. I am not sure if the Octane plugin is going to be able to get valid and not broken motion vectors from the realflow simulation object. As I say before, the LightWave internal data structures doesn't understand the concept of motion vector, and I am not sure how the Layout is handling this information for the LW native render engine.
Meanwhile as workaround I think that should try to render the scene with the Multipass MB technique, disabling the native Octane MB.
-Juanjo
The problem with the realflow scene and the deformations motion blur is easy to understand. I am not sure why, but the motion vectors in your realflow simulation are too long.
The simulation motion blur vectors are displacing the geometry too far from it's original position in only one frame, you can see it even with the LW native renderer, the motion blur with a 50% blur length has no sense at all. Octane can't process this kind of motion blur without consume a lot of CPU memory while building the acceleration structures.
If you set the motion blur length to only 5% in the LW camera parameters, the scene can be rendered without problems, and even a 5% MB is a lot of MB for this scene.
-Juanjo
The simulation motion blur vectors are displacing the geometry too far from it's original position in only one frame, you can see it even with the LW native renderer, the motion blur with a 50% blur length has no sense at all. Octane can't process this kind of motion blur without consume a lot of CPU memory while building the acceleration structures.
If you set the motion blur length to only 5% in the LW camera parameters, the scene can be rendered without problems, and even a 5% MB is a lot of MB for this scene.
-Juanjo
Hi juanigon
i precise i am not the one with realflow in the scene..
i reduced textures and subsequently vram usage to less that 3gb at my disposal... notwithstandly even if things go better must say i have a certain instability yet.. p.e. after a certain number of frames the scene i'm rendering now ran out of system memory, though the usage of vram was under 3000 of 6000
could it be that the problem with ram ( not vram) depends on the fact i am using raycasdt node for placing many objects in the scene?
also as a whole i think if i have 6gb of VRAM at my disposal instability problem should show up only at 5800 ram usage , not at 4300.. besides i run out of my ram ( though i have 32 gb) and not of my vram
i precise i am not the one with realflow in the scene..
i reduced textures and subsequently vram usage to less that 3gb at my disposal... notwithstandly even if things go better must say i have a certain instability yet.. p.e. after a certain number of frames the scene i'm rendering now ran out of system memory, though the usage of vram was under 3000 of 6000
could it be that the problem with ram ( not vram) depends on the fact i am using raycasdt node for placing many objects in the scene?
also as a whole i think if i have 6gb of VRAM at my disposal instability problem should show up only at 5800 ram usage , not at 4300.. besides i run out of my ram ( though i have 32 gb) and not of my vram
I am not sure, perhaps you are placing a lot of object in the same space, and Octane needs a lot of CPU RAM to build the acceleration structures, like happens with long motion vectors. It is hard to say without see the scene.giacob wrote: could it be that the problem with ram ( not vram) depends on the fact i am using raycasdt node for placing many objects in the scene?
-Juanjo
Hi Jaunigo
i am coming to the conclusion that my problems are hardware related... i tried the same scene on my laptop having a geoforce 635m e 12 gb di ram and, though slowly, it renderee without no problem of windoww memory stability....
in your opinion in wich part of the hardware the problem could lay?
unless.... i had a lot of light ( not used) with ies file thath i didnt changed on my laptop ... could be that ?
i am coming to the conclusion that my problems are hardware related... i tried the same scene on my laptop having a geoforce 635m e 12 gb di ram and, though slowly, it renderee without no problem of windoww memory stability....
in your opinion in wich part of the hardware the problem could lay?
unless.... i had a lot of light ( not used) with ies file thath i didnt changed on my laptop ... could be that ?
I don't think that the IES lights could be a problem, but it s also weird that a hardware problem could consume the system memory. Perhaps the problem is related to the system or the LW configuration, other plugins installed in LW, the drivers, etc.
Can you test your scene in a fresh LW install, with only the Octane plugin (and other plugins if your scene is using them)?
-Juanjo
Can you test your scene in a fresh LW install, with only the Octane plugin (and other plugins if your scene is using them)?
-Juanjo