Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Maxon Cinema 4D Cloner Speed

  • Cloner Speed

    Posted by Glenn Takakjian on March 7, 2007 at 11:04 pm

    Would there be a significant difference in Render Time if I took a Mograph Cloner ovject with 20,000 clones and converted it to 20,000 actual objects.

    This is a simple 4 Point Plane with a texture image. It is taking forever to render in its current state.

    It seems to have to calculate the clones on every frame

    Thanks

    TAK

    Mdme_sadie replied 19 years, 2 months ago 3 Members · 2 Replies
  • 2 Replies
  • Mylenium

    March 8, 2007 at 10:28 am

    Yes, the cloner is evaluated for each frame. Unless you convert the entire cloner to a solid object/ Hierarchy, you won’t see much speed gains jsut by converting the clones.

    Mylenium

    [Pour Myl

  • Mdme_sadie

    March 8, 2007 at 5:37 pm

    Certain effectors result in a recalculation on each frame due to their nature, the texture effector is one of them. The cloner itself makes heavy use of cacheing for speed and in general is very fast, often faster than having seperate geometry (compare it to using a TP Geometry object and you’ll find it’s at least twice as fast there, even more so when used to generate geometry from normal particles versus the particles obejct itself generating geometry) however when if an effector requires a full recalculation (such as often the texture effector) this cacheing can then sometimes go to waste, and the effector itself may require some time to evaluate per frame. Either not using a texture effector or making editable/current state to object can result in your scene being faster in this instance. However a large object count will always be slow in Cinema (in most apps come to that), for instance a thousand cubes will be many times slower than just an object with six thousand polygons.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy