OctaneRender for Rhino 1.32 [OBSOLETE] (RhinoSR7 31213)

[face_off]

1- On 2 live projects we had this situation - Scene 1 [large interior]: We had to up the max poly's in the Rhino/option dropdown to allow it to load into the Octane render window. Scene 2 [different large interior]: This loaded into Rhino Octane fine at default max poly's. When we voxelized it on the higher max poly's setting (as Scene 1) we received an out of memory error and Rhino crashed.

Question - Does Octane up the poly density if the Rhino/option poly max is set higher?

Answer : No.

The Max Polygons settings is used the determine how many polygons to pre-allocate in your PC' RAM for preparing the scene for loading into Octane. A higher number means you need more RAM. So I would guess that your second PC has less RAM than your first, so when you used the higher Max Polygon settings on the first PC it ram out of memory (that will happen regardless of the Rhino scene size).

How much RAM does that second PC have?

Rhino shouldn't crash if you run out of memory - so this looks like a bug in the plugin which I need to look into.

2- We are now working as teams on Rhino Octane and need all Live DB textures saved and linked from all Rhino seats to our main server. How do we change the default live DB location that we have added to our scenes?

The best option is if I add a "LiveDb Texturemap Location" folder setting to the plugin settings. Then you can all set the same location (it will need to be the same drive letter for each of you), and the texturemaps will be shared.

Paul

[Tipperz]

Hi Paul,

1- Out of memory issue: This is on one PC, not 2, and has 32gb RAM. So this seems strange that when the same scene has the Octane Options max poly's increased the scene crashed Rhino, even though the same scene at a lower max ploy's opens OK... over to you?

2- Yes a 'Live DB Texture Map' location choice within the Rhino Options would be perfect.

[face_off]

1- Out of memory issue: This is on one PC, not 2, and has 32gb RAM. So this seems strange that when the same scene has the Octane Options max poly's increased the scene crashed Rhino, even though the same scene at a lower max ploy's opens OK... over to you?

Ah, OK. I suspect it's still running out of memory. Perhaps that Rhino scene is very very large and taking a lot of RAM, so there is less left for the plugin? Very hard to diagnose without more detailed memory usage stats. Perhaps open task manager to see how much memory that scene is taking (ie. the total memory being used by the Rhino process). Also - what Max Polygons are you using where the scene is failing?

If in doubt - send me the scene and I'll try to load it on my 16Gig PC.

Paul

[Tipperz]

Large scene memory issue; I won't upload as it is 400mb +. the scene is a 2 floor 1000sqm / 10,000sqf store so a lot of geometry. We will keep you updated if we have any further issues. We have produced 4 full retail interiors to date using the Rhino Octane beta with great results. Once they go live in-store I will share some renders. Is it best to post in this thread or the gallery section?

Matt

[face_off]

Large scene memory issue; I won't upload as it is 400mb +. the scene is a 2 floor 1000sqm / 10,000sqf store so a lot of geometry. We will keep you updated if we have any further issues. We have produced 4 full retail interiors to date using the Rhino Octane beta with great results. Once they go live in-store I will share some renders. Is it best to post in this thread or the gallery section?

Thanks for the info. I have a very very large Revit file sent to me, which I used to stress test all the geometry loading code. It transposed that code to the Rhino plugin, but was never able to get a scene big enough to run out of RAM. So there could potentially an issue there, which is probably easy to fix if I have a scene which reproduces the issue on my system.

I would love to see the sample renders. Suggest posting in the gallery, but let us know when you do it so I can take a look.

Paul

[face_off]

I have refreshed the installer at the top of this thread with:

1.25.0.5
- Zooming out of the Viewport (via the zoom combobox) now works if the render is paused
- Added a LiveDb Texturemap Folder field in the Configuration - so you can now better control where the LiveDb texturemaps are stored and share them between you PC's (so the Rhino scenes can be shared). Remember that the full path to the LiveDb texturemap location WHEN IT WAS DOWNLOADED is used by the Octane nodes and saved in the Rhino scene file - so the LiveDb Texturemap Folder will need to be the same absolute path on all your systems that share Rhino files.

Paul

[Bendbox]

- Added a LiveDb Texturemap Folder field in the Configuration - so you can now better control where the LiveDb texturemaps are stored and share them between you PC's (so the Rhino scenes can be shared). Remember that the full path to the LiveDb texturemap location WHEN IT WAS DOWNLOADED is used by the Octane nodes and saved in the Rhino scene file - so the LiveDb Texturemap Folder will need to be the same absolute path on all your systems that share Rhino files.

Paul

Thank you! This is a big help!

[justix]

Paul, is the Export to OCS actually work as it should? I mean, I did try to export it to OCS but this is as far as I go, other exporter does open the scene by itself while on this installer it does not, BUT is not the issue, more like that It does not seems to render the scene at all, only materials and nodes seems disconnected? clicking on the render target does nothing...

edit: upgrade to Octane 1.27 works BUT camera coords seems lost AND navigating to recover camera position make octane hang...

[Area D]

Paul, is the Export to OCS actually work as it should? I mean, I did try to export it to OCS but this is as far as I go, other exporter does open the scene by itself while on this installer it does not, BUT is not the issue, more like that It does not seems to render the scene at all, only materials and nodes seems disconnected? clicking on the render target does nothing...

edit: upgrade to Octane 1.27 works BUT camera coords seems lost AND navigating to recover camera position make octane hang...

it seems that you have not exported the mesh node.. in the 1.25 it works fine...

[face_off]

Paul, is the Export to OCS actually work as it should? I mean, I did try to export it to OCS but this is as far as I go, other exporter does open the scene by itself while on this installer it does not, BUT is not the issue, more like that It does not seems to render the scene at all, only materials and nodes seems disconnected? clicking on the render target does nothing...

edit: upgrade to Octane 1.27 works BUT camera coords seems lost AND navigating to recover camera position make octane hang...

Until things settle down with Octane Standalone - I think you will need to open the exported OCS file in the same version of Octane Standalone as the Rhino plugin. So export from the 1.25 version of the Rhino plugin and import into Octane Standalone 1.25. This /should/ work. If it does not, pls let me know the details.

Paul