OTOY Forums

Hi,

To cut a long story short; I have a massfx animated gravel and stone with about 5000 mass-fx animated objects. They are instanced and set as movable proxy. It works perfectly in 3DS Max and only takes about 5 seconds to compile the scene there for render. In total there are about 3 000 000 polys in the scene.

When I try to export the animation to Standalone though, it builds it up in batches of 5 kilobytes or something. I left it overnight, so probably about 10, 12 hours, and the ABC file only built up to about 450 megabytes by this morning.

I have a deadline in a couple of days and that is the very last thing in the world that I expected!!!

Any ideas????

Any workarounds?

Alternatively, can I set it up in max to render out individual animation frames and save them?? Even though it takes longer than in Standalone, at least I'll be able to produce something!

Please help!

Could you give me the scene where you have this issue?

Hi Jimstar, thanks for the very quick reply...

I'll send it to you when I get home today, how would you like me to send it to you, i.e. via wetransfer or something else?

Re,
Aljosa

Hi again JimStar,

we did some tests yesterday evening and came to the conclusion that the compiler is actually just that slow with that amount of objects, it actually looks like it's compiling each individual stone and then moves to the next one, which would explain why it's moving in batches of a couple of kilobytes, as there are about 7, 8 000 individual animated objects over a couple of hundred of frames. Are our assumptions correct?

In comparison, taking a snapshot of all of these objects, merging them together, and then exporting still takes a while (but a minute or two compared to some odd 15 hours with individual stones), but you can clearly see how the abc file builds up in big MB chunks rather than a 100 kb at a time.

So we resorted to rendering such parts out through 3ds Max directly and do the rest via standalone. Again, there is no issue with octane standalone or max plugin having any issues with the scene at all, just the compiler takes forever to grind through it.

Is this something that could possibly be addressed in the future or is that, well, simply in the nature of the compiler and workarounds will always be needed for such scenes?

Cheers,
Aljosa

....I'll take that as a yes then:-)

Also, with a different scene, I had about 300 mb orbx file after export. I just did a few minor keyframe changes to a single object, just position changed on about 10 existing keyframes, (this scene doesnt have thousants of objects) and now orbX is 950 mb?????

wtf?!???????

Should I try reinstalling the plugin?