Why is generating poitns single threaded ?

[Helli]

Why is generating poitns single threaded ?

Just would like to know ??

[Helli]

I'm asking cause I had this situation quite some times allready:

I had to emit several million particles on the first frame, which for 1 project took over an hour, so I could then simulate them (a blast or whatever).
Simulating the following frames then took only like a minute or 30 sec. So thats quite depressing actually.

So if there are some options to optimzie this process which I don't know yet would be nice to know.
Right now I am using a generate sample set node to create points in a mesh volume, That shouldnt take long actually.

What takes long is generating trails, which I understand somwhow cause the emitter changes over time which leads to a lot of calculating and I figured out cashing the emitter particles before using them for trail emitting safes time. But for my first problem I am rly a bit clueless.

[ace63]

Actually on big meshes volume emission is a time killer. I had to scale down a scene to 100th of the original size recently to be able to work with volume emission at all.

[Helli]

Thats a good tip allready, thanks.

But in my case I allways try to stay in real world scale. So in my actual case I emit from a basic character which is ~2m in scale.
I will try that anyways, just scaling down the emitter and then scaling up the point positions again in the ice tree after emission.

[Helli]

Any other answers ?

[gustavoeb]

the default point emitting compounds suck, imho. I tend to slap something together with "generate sample set" and "add point" nodes, as soon as things start to get slow.

edit: they dont suck, they just tend to do a lot more then you might need, and that may be expensive

[Helli]

I never use the normal emit compounds for heavy simulations, just cause like you said, because of the overhead in the compounds.