Scene fails to render but is below memory usage?

[Norton]

I have an scene that has suddenly started failing at frame 303; it seems to fail from 303 ~480 but other frames are ok. I'm trying to figure out why because it looks like it should be well within the capacity of my 6gb Titan Black

--Vram usage (according to nvidia-smi) for frames 0-300 is 1000mb to 3068mb. (Frame 303 fails to increase background vram usage and hangs when rendering through backburner and displayes "RENDER IS FAILED." in 3dsmax)
--If I hide either of the two main meshes, I can render the scene without a problem; octane reports the scene size at 1300 and 1200mb for each version.

Why is this happening? There are no geometry bugs and it looks like the scene size should have an upper bound of 3.5gb which is well below the available memory reported by nvidia-smi durning render. There is only one texture map and changing all materials to default has no effect.

Are there additional Ocane geometry limitations I'm not aware of?

Can someone advise?

[frostfx]

How many polygons you have in the scene? In current Octane version theres is limit how many polygons you can use (has to fit into 2gb i think).

[Norton]

Looks like about 15 million (~ 7m and ~7.6m) for that frame.

If that's the case, that's a pretty big limitation given current hardware is up to 12 gb . . .

These are meshed particles, is there a way to instance one of the particle groups to get it rendered in 3ds max?

[frostfx]

This might be the case, i remember we had same problem. This limitation is removed in OC3.