So you're asking yourself "Why would I want to use PDG/TOPs?!". If you're not convinced yet, maybe this straightforward single TOP-node setup will convince you. In this tutorial we'll speed up the remeshing of an animated mesh by a factor of ten. Yes, that's x10!



Still thinks “Space: 1999” is the coolest thing that ever happened on german TV. Be it pixels, hardware, code or cameras – if it’s interesting, Moritz is gonna take it apart. And sometimes even reassemble it. In his spare time he likes to dabble with code and create generative artwork. He claims his early exposure to QBasic is no help at all when working in Houdini, Cinema 4D, Processing or Arduino. But it might have been what started his fascination for the boundaries of code and art. When not wreaking havoc to any intriguing devices around him, he works as a freelance Art Director / Technical Director.

More from Moritz Schwind


  • bdav 10 months, 2 weeks ago  | 

    Really useful thanks !

  • Dav_Rod 10 months, 1 week ago  | 

    Thanks a lot for the tut!

    If the PDG is able to perfectly define 229 processes,
    I wonder if it would be possible to throw them to the graphics card instead of the processor.(?)

  • Petoncle56 10 months, 1 week ago  | 

    exactly what i need, thanks !

  • Dav_Rod 10 months, 1 week ago  | 

    Thanks a lot for that

    The remesh node is using one core as seen in the task manager. But just one or two nodes up, all cores are being already used as soon as you step one frame on the timeline.
    When watching the task manager with PDGs all cores are being used because it is running the full process at each frame. But that doesnt mean that now the remesh is performing faster.

    Am I wrong?

    I would like to know what is the speed increase, but my machine crashes with pdgs and still dont know why. Somebody can give some data about it? Maybe just a time comparison for the first 5 frames with and without PDGs?

    Thanks in advance.

Please log in to leave a comment.