Hi Andreas!
I don’t have a direct solution for the attach/detach problem, i remember having those speed problems with my Legolizer script, too. I “solved” it by splitting the base mesh into segments, so i never have to use the whole object, just parts from it. Don’t know if this is also possible in your situation. But one thing that would speed up the loops when using polyOp functions inside is to store the function in a variable before the loop:
instead:
for i=1 to 10000 do result[i]=polyOp.getFaceVerts test i;
use:
poFunc = polyOp.getFaceVerts
for i=1 to 10000 do result[i]=poFunc test i;
this gives you about 50ms, not much, but its a start
Aha, that is interesting Capt Suic. I will look at it some more. Myself I’m benchmarking every situation. I will do some tests just how fast your script is Capt.
Or even worse, later when I will update the big object with the changes to the new object, then it is VERY slow
Right now I have to move every vertex one at a time, and it’s amazingly slow. Hm, there has to be a better way.
Cthul, yes that’s true I will do that. I just hadn’t bothered, but it will create a difference
What I would like to do is this:
move say 1000 vertices on the object, but the object doesn’t not update. Then I write object.update() and it will update the geometry. I think the mesh object has something like this, but the polyobject seems to lack it. Ideas on this?
Also I think that there may be some clever way of doing this. Especially the attach. Perhaps we could use some weird modifiers to do this? For example update a ffd modifier and apply it on the big object with the selected area, and then collapse it.
/Andreas