Hi guys.
Cebas Thinking Particles allows user to make a custom nodes. This custom nodes is based on Scripted mxs plugins.So in general custom Nodes have input – output and in it you can change a particles behaviors.
For example: particles can be born on object in all edges include invisible.
So I with friend make a custom node that can place particles only on visible edges. It’s randomly get position between two vertex and give this position to new particle. Couple strings of code.The problem with it of course speed. Basically it works fine.But more particles -more delay.
So here I have two questions:
1.Is it good idea to call a custom functions from writed on SDK plugin for some computations. Let say for example i write before – get a node, give that node to custom plugin. Plugin make a computation on random position and return it. Than this position outputs to the TP.
2. If answer on first question is positive what type of plugin i can use. Need I write a only .dlx plugin or i can use any plugin type I want ?
the c++(sdk) implemented function called from the script might help with performance. but it depends on what you do in the c++ function.
for example if you just calculate a random positions between two points, it gives you a miserable difference against using the mxs.
but if you using c++ function do the getting the edge, checking the edge visibility, getting the edge vertices and their positions , and after that you do the calculation – that’s the different story. It can improve the particle script dramatically.
I would make DLX plugin…
Thanks for answer.
Good to know I’m not in wrong way.