Out of system memory......

[splittmatt]

I am getting an error message on opening Octane.
'Out of memory (System RAM) - Reduce the Max Number of Polygons in the plugins settings'

I then get another error. 'Cuda Error Loading Scene : CUDA error 2 on Device0 etc etc etc. It then crashes Rhino.

My system has 32Gb RAM and when watching the monitor when I open Octane it only ever maxed at 11.7Gb.
My GPU monitor isn't showing the memory maxing out either. I have a 4Gb 670 and 2x 580's with 1.5Gb each.
If I reduce the Polygon count in the plugin settings I get the other error telling me to increase the Polygon count.

Is there a 12Gb system RAM limit on Octane?

At the moment I am stuck with a scene I can't render. Any ideas?

[face_off]

There is no System RAM memory limit in Octane or the plugin, however there might be a limit in .NET (which RhinoCommon uses). Plugin memory is consumed as follows when loading the scene into the Viewport:
- the memory required to store Max Polygons (set in the Rhino preferences) is allocated in RAM <- all non-live, non-block instance geometry is stored in here....
- for each live geometry item and block instance, the memory required to store Max Polygons is allocated in RAM for loading that mesh item and then released.

So at any one point in time you need RAM to store 2 x Max Polygons.

If EVERY mesh item in your scene is live, then Max Polygons only needs to be large enough to store the polygons of the largest mesh item.

If you are hitting the limit.....
1) Lower the Max Polygons and then also reduce the triangulation settings (tick Custom mesh, Adjust, reduce Density, etc) for the mesh in Rhino (so there are few polygons), OR
2) If you have a big mesh item in the scene, make it Live - then it won't use the RAM needed for the static meshes

When I last checked, there was a hard limit of about 50million polygons in Octane, and very roughly, you can get 15million polygons into a 2Gig graphics card if you have minimal texturemaps.

Hope that helps.

Pls feel free to send me the scene, and I can test it - there might be some smarts I can add to the plugin to help load these types of scenes if I have a test scene to work with (for example, maybe a "Load all meshes as Live" option).

Paul

[splittmatt]

Thanks Paul.

I think it's down to a particular piece of insane geometry that was made in Solid Works.
Hopefully I can work around it.

The crashes I had were totally killing Rhino and also affecting my display drivers, on one occasion resizing my display resolution?

I will let you know how I get on.

[prehabitat]

I am getting an error message on opening Octane.
'Out of memory (System RAM) - Reduce the Max Number of Polygons in the plugins settings'

I then get another error. 'Cuda Error Loading Scene : CUDA error 2 on Device0 etc etc etc. It then crashes Rhino.

I just this exact same issue with a scene I exported from Revit - (don't ask).. no rhino crashes though.
The strange thing I noticed (or perhaps not) As lowering the poly limit in octane from 100k to 10k I received the Poly Limit reached error.
so I slowly upped the poly count until around 90k where it began working again, loaded the scene into rhino, and only consumed 185mb at 6000x3000 . seems strange that such a small (in VRAM) scene would max the system memory out?

As above - it was exported geom from Revit, which is notoriously terrible no matter how you recook it on import. (we have the similar problems with 3DS in the office - random verticies on 20-50 sided rectilinear volumes)

[face_off]

seems strange that such a small (in VRAM) scene would max the system memory out?

The next version of the plugin requires vastly lower memory amounts to load scenes - so will most likely fix your issue. The current version of the plugin has a problem where if you have say 200 live geometry object, plus one really big object, the buffer required for he large object is used for the 200 live objects, so you run out of memory. But this will all be fixed in the next day or two - just waiting for the next Octane API.

Paul

[polywog7]

I have been having this same problem with a model exported from solid works, runs out of memory, then crashes rhino to the desktop. The model is actually not very complex though... It did import every single polysrf as its own block though, could this be causing the problem? I'm still trying to wrap my head around the concept of the live geometry and if blocks help or hurt your memory requirements.

Thanks

[face_off]

I have been having this same problem with a model exported from solid works, runs out of memory, then crashes rhino to the desktop. The model is actually not very complex though... It did import every single polysrf as its own block though, could this be causing the problem? I'm still trying to wrap my head around the concept of the live geometry and if blocks help or hurt your memory requirements.

Have you tried the latest version at http://render.otoy.com/forum/viewtopic.php?f=41&t=39099? It should fix this issue.

Paul

[polywog7]

Just installed the update, and that same model from solidworks seems to open fine now! I'll let ya know if anything else happens. Ive been having quite a few crashes to desktop on this last build, but I added a new gpu at the same time as updating, and have some hardware issues so I assumed it was the hardware... Looks good!

Thanks Paul!

-Nick

[face_off]

Hi Nick - Yes, I am getting a couple of crash reports from McNeel on the previous version of the plugin. The crash is caused by the method I'm using to ensure the refreshing of the Viewport does not memory leak (due to a bug/issue with .NET). I made a change with this on the latest version. I would be very interested to see if the latest version resolves this.

Paul

[polywog7]

Sounds good, I'll keep you updated. I've been in and out of the octane viewport a bit today, and its been great still. Thanks!

One random note, we talked about it a while back, but if you look at the live DB copper color, it still renders as black in the rhino viewport since it is the first diffuse color in the tree. Is there any way for us to specify which source to use for the rhino viewport? IE if I wanted it to show up as the specular color instead? (which is a bit closer to what the octane copper looks like)

Thanks