But there’s no option to export a sequence, just a single OBJ of whatever’s on screen at the time – and I didn’t fancy manually exporting 1200 frames.Īt this point I was nearly ready to just render the entire video in Cinema 4D and forget Element 3D altogether, but I wasn’t quite ready to give up and needed the render speed and extra control I could get in After Effects.Īfter some more Googling, I eventually found exactly what I needed – an amazing little Python script by Owen Lim, hidden away on his Behance profile. > Wavefront OBJ (*.obj) – created exactly the file I needed – it worked exactly as expected in Element 3D. BUT, the Plexus OBJ Sequence Exporter doesn’t include any material ID’s in it’s OBJ files, and Element 3D requires each separate object to have a unique material applied if you want to texture them differently in Element 3D’s interface and generally have much more control over how you render with it in After Effects.Įxporting a single OBJ using Cinema 4D’s built exporter – File > Export. Plexus OBJ Sequence Exporter for C4D (free) exported the bare bones of the animation (including the scaled elements) correctly and if I’d been using Plexus, it would have been (appropriately) perfect.Even when I baked the whole MoGraph simulation to keyframes (using NitroBake) it wasn’t working as I needed it to. Riptide Pro ($50) partly worked, but for some reason – no matter what options I set in the plugin – it had an issue with some of the cloner objects that were scaled – they were coming into Element 3D at completely the wrong size and the scale animation was been completely ignored.

There are two plugins that I’ve found that export a sequence of OBJ files, but neither of those were working as I needed them to for a recent project. I needed a sequence made up of 1200 individual files to bring into Element 3D for After Effects. OBJ Sequence Export (Python Script, No Plug-ins)Īs of Cinema 4D R17, there’s still no easy, built in method to export an OBJ sequence.

Nitro cinema 4d plugins