I am reporting back with two items, pretty good news!
I see now - the problem is fixed in the early SR6 I was using; this speed problem is only present in 7 SR4 and SR5. I would appreciate if you could test that it’s fixed in this early 7 SR6, or in the last 8 WIP.
In general, MeshMeshFast is an obsolete method but, if you guys feel that it is highly required, we might spend some time optimizing it also in V7 or V8, probably bringing it to being slightly faster than V6, but not much. I don’t think it will ever be very reliable because there’s no way to input a tolerance, and that’s why it was obsoleted.
However, my understand is that a method to intersect all the meshes at the same time and only provide an indication of which ones touch would be much more needed. This is possible, there is code internally to do this, and would likely take a fraction of the overall combinatorial execution.
In organize work around this, I’d need your help stating a wish and an expression of your needs.
Thanks,
Giulio
–
Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com