What is going on with V3? poly limit crashes...

[darkline]

I have a scene containing 24M polygons. It opened fine in octane 1 and took around 2.5GB RAM.

Octane 2 would not open the scene at all, because of the poly limit. I did a workaround for the moment until Octane 3 fixed this issue.

Today I finally upgraded to Octane 3 with the poly limit removed. Try to load the exact same scene from V1 and the computer hangs. I get warnings of my PC running low on memory and I have to exit 3DSMAX. Just to be clear, there is nothing wrong with my PC. I can reinstall octane v1 and load this scene with no problems.

So to see where this was maxing out, I deleted half of the polys in my scene and tried to load into octane 3 again. It takes it's time but works, taking up a whopping 4GB RAM for far fewer polys. So that gets me thinking that my 24M polys (for some reaon) are now exceeding the 6GB limit of my GTX TITAN.

I assumed it was the parallel samples set at 8 causing the problem , so I reduced this down to 1 - and VRAM usage drops from 4GB to 3.7GB RAM - still seems a lot.

So I finally come to the conclusion that around 22.5 million polys take up 5GB RAM. Over twice that of the original octane renderer. The view port takes twice as long to open too. On top of that if I make any changes in my max viewport the octane window stops refreshing and I have to reload the scene again!!!

What exactly is going on?

[thanulee]

Hey darkline, u found any solution to ur problem? Cause it seems really serious for getting 0 responses so many days.
cheers

[Goldorak]

Would you be able to share the Max file in question with Azen and the devs so we can investigate this directly?

Remember V1 did not account for rendering motion blur, mutli-UVs, displacement, strands and other mesh properties that increase the memory footprint with 2.x+ features. How much system memory are you seeing used by the scene when you load it?

Have you tried exporting to ORBX and rendering in standalone to see if it is any different?