Well this will not break anything, but can make things slower, much slower than 55 times. To find which curve belong to point (hair root), compound compares the UV distance between point itself and first point on curve - and 'plain' 'Sort Array With Key' node is used here. In case compound is used with guides, and allowed 8 curves, this is about 300-500 guides * 8 - not that much. But, if higher numbers are used, number of calculations is multiplied. At some point (especially with huge number of hairs), I'm afraid the calculation may take forever.izze wrote:Thanks a ton!
Also, I assume this will not break anything by doing this. I have 55 curves attached so far and it still seems fine.
Thanks.
If you're using multiple compounds, one after another, calculations are split to nodes - a bit better, but not enough.
So I think the best way for such number of curves, is to merge all curves into the one, and create a separate, simple point cloud that contains only points, on first points on curves (that's allow using of much faster 'Get Closest Location' node, which uses a lot of ICE magic, and will stop with searching when target is found, calculation is almost 1*1). I had a compound that works in this way (actually, 'Emit Hair' is something like that), but didn't want to bother people with yet another point cloud, used only for searching.
Also, if only curves are used, creating vectors for later deformations (curls,bend) is a risky business, in some cases everything is nice, in some other cases, deformations become weird.
Anyway, I hope I'll post a working example tomorrow (here's late evening, now).
For merging multiple curves into one, I'm using a good old script by.... Ciaran Moloney - probably you can find this script, or something similar, somewhere on internet.
Cheers