IPR issues no idea why.

[RyDarling]

IPR/Octane 2.24.2 is behaving strange. and I'm not sure why.

The IPR won't update with all of my objects turned on. I'm trying to render a heavy Stl model (2.8 mil triangles from Solidworks) over another model low poly model with a 4K displacement map. Both seem to render fine separately however rendering then together just won't happen. The IPR doesn't update from the snapshot.

I'm feeling as though I might be having either memory issues or there are setting that I need to work with to allocate more resources.

I've been hacking away at this all weekend and have hit a brick wall. Any help would be greatly appreciated! Btw, I've already changed all geometry types to "moveable proxy"

Scene poly count: 2.9mil faces

Octane Render Settings

This is a wide shot of my scene and the only thing I can seem to render.

Wireframe

System spec's:
Windows's 10
32GB Ram
i7
x2 GTX 970's

___________

Here is an example of the scene rendered via the Maya Plug-in. The anatomy is a decimated mesh (13 mil tri's with texture - No displacement).

[calus]

I'm trying to render a heavy Stl model (2.8 mil triangles from Solidworks) over another model low poly model with a 4K displacement map. Both seem to render fine separately however rendering then together just won't happen. The IPR doesn't update from the snapshot.

Hi RyDarling,

First of all, I can see on the rendersetting screenshot you're using an old 2.24.2 plugin maybe 2.24.2- 7.14, you should use the 2.24.2- 7.24 which is more stable.

I remember also having strange IPR updating with scene involving displacement.

To debugg your scene :
keep only the two objects in a new scene.
On the displaced model start with a lower res for displacement (512x512 for example),
and on the STL object apply a polygon reduction, mesh>reduce, (starting at 90% for example).

Does the problem still occur ?

if yes,
the problem is not memory relative.

If not,
- progressively increase the displace resolution to find out when the problem start to happen.
- and/or progressively decrease the polygon reduction to find out when the problem start to happen.

[RyDarling]

Hi calus,

Thanks for the suggestions. I didn't realize I had an older version. Good call. I tried working with downsizing the stl's, however They took way too long to calculate and I couldn't dial it in to where it would maintain the integrity of the model.

Also, when I disconnect the displacement map I was finally able to render everything together as opposed to being rendered individually. So I know that all of my objects will render and it does seem as though the displacement map was putting it over the top, not sure relative to what though - GPU Mem or CPU Mem. I down sized my displacement map to 512 and it still won't render.

Assuming it is a memory issue, any thoughts on where I should focus on adding more?

Currently I have 32GB Ram and I think 4GB per GPU.

[calus]

Also, when I disconnect the displacement map I was finally able to render everything together as opposed to being rendered individually. So I know that all of my objects will render and it does seem as though the displacement map was putting it over the top, not sure relative to what though - GPU Mem or CPU Mem. I down sized my displacement map to 512 and it still won't render.

Octane doesn't need much RAM (except for hair ),
and with 4GB of VRAM you should be able to render around 38 millions of triangle with octane3 (the limit is 76 milion triangles)...
but for Octane2 the limit is 19 milions of triangles, so maybe your scene with displacement use 10 milions polygons = 20 millions triangles ?

Did you try to enable the "out of core" option ? (it's only 10% slowdown, and free the VRAM used by textures)

Also do you use motion blur ? if yes, try without motion blur, it triggers all kind of problems, specially with displacement.

If nothing works you should try to export your scene to the standalone V3 , but as you have big geometry, the export might crash,
so use "export Octane animated scene" option with "embed alembic in ORBX", even for still image, this is more stable.