i have disabled all istances ad it manages to render the scenes... frankly there ar not many istances... just 108000
any way here the ram usage report...
BEFORe OPENING LW 9%-AFTER OPENING lw SCENE 46%; WITH IPR 64% ( THE USAGE DOESNT CHANGE TO MUCH IF I CHANGE RESOLUTION); WITH RENDER 79%
if i enable istances it crashes again.... octane fills all system memory before reaching updating phase
ram usage problems with octane
Moderator: juanjgon
So if you disable the instances, you can render the scene without problems ... weird, it is really strange that the IPR can render the scene and the F9 not at the same resolution. With the motion blur disabled in the camera options panel, and without render passes, the render should be the same.
Do you have this problem with other scenes or only with this one?
Let me think about it ... can you please send to me the .lws scene file and the objects (I don't need the textures)?, I want to know the render settings and the kind of objects you are using, and try to reproduce the problem here. You can send it to me to [email protected]
-Juanjo
Do you have this problem with other scenes or only with this one?
Let me think about it ... can you please send to me the .lws scene file and the objects (I don't need the textures)?, I want to know the render settings and the kind of objects you are using, and try to reproduce the problem here. You can send it to me to [email protected]
-Juanjo
I could understand that a big scene can not fit in the system RAM, but I need to know why the IPR can render it and the final F9 rendering not. This sounds to me like a bug, or something strange in the scene configuration ... or even a LightWave bug.
What LW version are you using, and in what OS?
-Juanjo
What LW version are you using, and in what OS?
-Juanjo
If it could help, I ran into the same problem with a scene recently. IPR would render the instances but F9 would crash Lightwave instantly.
The problem was a gradient set up to drive the size of the instances. The gradient input was "X-distance from a null", and the problem was that some keys had a very large value, way above 100%.
I had to remove the gradient, and size up my instanced object in Modeler to compensate.
Hope this helps.
The problem was a gradient set up to drive the size of the instances. The gradient input was "X-distance from a null", and the problem was that some keys had a very large value, way above 100%.
I had to remove the gradient, and size up my instanced object in Modeler to compensate.
Hope this helps.
The problem was that the scene had the LW color space functions enabled, specially one very dangerous: the "Convert 8-bit to Float" option, as you can see in the attached image.
With the "Convert 8-bit to Float" option enabled, when you press F9/F10 the Layout loads all the texture image maps, converts all to floating point images and color correct them. The floating image maps are going to eat a lot of CPU memory. All this information is not used at all in Octane, but Layout stores the corrected maps in memory even after finish the rendering, and this is the problem.
As you know Octane doesn't use the LightWave color space functions at all, you get wrong color corrected images in the IPR, and as you can see you can have a lot of problems with them enabled. To work with Octane you should disable all the LW color space functions.
-Juanjo
With the "Convert 8-bit to Float" option enabled, when you press F9/F10 the Layout loads all the texture image maps, converts all to floating point images and color correct them. The floating image maps are going to eat a lot of CPU memory. All this information is not used at all in Octane, but Layout stores the corrected maps in memory even after finish the rendering, and this is the problem.
As you know Octane doesn't use the LightWave color space functions at all, you get wrong color corrected images in the IPR, and as you can see you can have a lot of problems with them enabled. To work with Octane you should disable all the LW color space functions.
-Juanjo
- Attachments
-