Originally Posted by EricM
Control is good, but so far I'm curious to know why to create a simple emitter you need up to five or six objects linked together : Particles Grid Emitter + Particle Emisison Settings + Duration + Rate + alignment + particle groups...
You only need two objects in that case.
The Particle Grid Emitter and the particle emission settings.
Duration, Rate (which only makes sense with a Particle Mesh Emitter) and alignment are all optional for further control.
Alignement for example is used when emitting vorticity particles only (so you can give them an initial spin direction).
Particle Group...well, you need a particle group to store particles. No way around this. And the emitter needs to know the target particle group (just as in TP).
The reason is the same as in a node based system (that's how it's internally structured), reusability. Just as you do in Xpresso to control several other nodes with a single one.
For example using a pmesh emitter with a pgrid emitter allows reusing durations, alignments and rates for both emitters and only changing one emission settings. This concept therefore gets more advantageous with complexity. In simple setups it seems over the top but with more complex setups the framework actually shines.
|Why not have one object with 5 tabs for such common settings with basic settings already dialed in?|
Because it destroys the advantage of in-depth modular control approach and it makes reusability impossible or only possible with hard-coded (even if dynamic) code. Also it makes extenting from the outside (other developers for example) way harder. And the new framework makes developement easier too (bug finding and fixes, faster updates, extensions..).
One has to keep in mind that the framework is not specific. It only provides an time and space integrated environment for any kind of stuff. The user could calculate orange growth using available structures or incorporate own algorithms or even extent the existing ones! Empowering this is only possible if deep access is given and that's what the framework has in mind.
|I'm eagerly waiting for more documentation and tutorials, because as of now I find it a bit puzzling to say the least.|
Yeah, no doubt in the beginning you have to get your head around it (also because there are so many nodes) but once you get the hang of it you'll see it becomes quite simple and powerful.
Please feel free to post any questions in our forum or here, we will gladly help. Also it's good to check out the example files. But yep, tutorials and docs will follow definetly! We are urging promised