Mutiples Objects Instancing with TouchDesigner
Вставка
- Опубліковано 17 вер 2024
- Welcome to thisTouchDesigner tutorial on Multiple Objects Instancing! 🎨✨
In this video, we explore the fascinating possibilities of instancing through the Copy SOP and other powerful tools in TouchDesigner.
This is part 1 of a 2 part serie.
In this first tutorial we will build the backbone of our network.
You can find the .TOX here:
drive.google.c...
Enjoy
Very interesting way of doing things... I had no idea! I always used Geo comps for instancing.
I would say that it is the best approach 99% of the time. But when you need a more custom approach on attributes, the copy Sop can come to the rescue ! Cheers
The example can only record the instantaneous state of the model, which is obviously not enough, if the action of the model can be retained. Thank you for sharing, I will continue to follow you and look forward to your follow-up
Yes you’re right! This will only export the immediate state of your setup, but in some case that’s what is needed, which is never possible with the Geo Comp. Cheers
@@smoothisfast_design How to interpolate the action of the model, the default is the synchronous state
Not sure I understand correctly your question
@@smoothisfast_design How 3D models are interpolated in the rendering of model animations so that they don't have the same action. I know that planar maps can be interpolated with tex3d. But I don't know how to set up the model animation. Hope it can be answered,
I am going to say the same that I already told bileam:
This is not Instancing. This is maybe instanciating but call it what it is, copying.
(Geometry) Instancing is a very specific approach to rendering geometry where you only send the geometrydata once to the GPU, coupled with a fixed set of directions of how to draw them. This is inncredibly fast and the main reason to use it.
When you copy the SOP-Data using the cpySop and send it then to the GPU. All transformations are handled by the CPU, blocking frametime, you are lso blocking additional time by sending a lot of repetitive data to the GPU (which takes a lot of ime.)
/rantover.
No arguments here; you’re absolutely right about the distinction. I did mention that this technique isn't the optimal real-time approach. However, I believe that there are scenarios where the precision and control offered by CPU-based processing can outweigh the speed advantages of GPU instancing.