Hi Michael !
Thanks this is the easiest !
Your Merger tool works great !
Thats what I was looking for........
I tried it on the mesh and it works ......fantastic.
The other option is good too.
But I have some 3 dimensional objects that I produce with lots of arrays
and the tool works better with them then making 2d first.
Would be fantastic to see the application built into Moi3d !! : )
Thanks
Peter

Hi Peter, well there is a difference between the methods.

That tool just combines all the polygons together into one big object - this leaves a bunch of polygons on the "inside" part of the mesh - it basically does not generate an object made out of one single connected skin.

In other words, it is not a totally clean single volume.

For some purposes like rendering where you aren't looking at the inside that is not a big deal. For other purposes like manufacturing, this kind of messy interior is a problem.

The 2d method would create a completely "clean" volume without extra pieces hanging around on the inside of it.

- Michael

Thanks Michael !
I understand that ...
If this would be implemented it should only be as
an option with a check .
Its usefull in most cases to have seperate object pieces for texturing
in other cases its easier to texture in one go !
Manufacturing is another pair of shoes : )
Peter

Is the previous OBJ utility added on the Wiki?

>Your Merger tool works great !
Little precision of word!
it's the "Boolean Union" tool
not the "Boolean Merge" tool !

Hi Pilou,

> Is the previous OBJ utility added on the Wiki?

Not yet - I'll add it up there tomorrow though.


> >Your Merger tool works great !
> Little precision of word!
> it's the "Boolean Union" tool
> not the "Boolean Merge" tool !

I think maybe he was referring to that MergeOBJ.exe utility here instead of booleans?

- Michael

Maybe :)

Yes !
Thats what I tried out and it worked great !
I did not speak about the boolean tools they are great too ....
but thats what I started out with ... and had the problems with !
I have so many occasions were this tool is usefull.... ! :)
Thanks
Peter

I've noticed in MOI that at times when I can't get a join or a union to work with something, if I explode everything and then join/union piece by piece, I can then get everything joined together as desired...

-Will

Just wanted to publicy thank you Michael for the GREAT support, your joining fix completely fixed the problem and I just joined a 400MB object made of hundreds patches successfully, and in a really short computation time (rhino failed here).

Thank you very very much.
Erwan

massive attack :)

Massive thanks !
; )
Peter

btw, sorry to get back again and again on multithreading :s
but couldn't MoI use one thread per object when doing such operation ?

> but couldn't MoI use one thread per object when doing such operation ?

Hi Erwan - well the way joining works is not so much on a per-object basis as it is a processing of all the open edges.

The tricky part is that also some edges may be modified during the join process, for example when 2 are glued together, or when an edge is split into multiple edges.

Algorithms that do modifications in the middle of them tend to be more difficult to break apart into parallel tasks that can be handled by multiple threads.

The other thing is that something like "one thread per entity" really doesn't work very well, because that actually creates too many threads to be optimal - to make best use of resources there shouldn't be more threads than CPUs. So the way it usually needs to work is to maintain a kind of queue of work items and parcel those work items out to be processed on different threads.

It is not typically a very easy task to take a chunk of existing code that is not built with this in mind and then change it to do that... It tends to require a significant rewrite of the code, not just a minor modification.

- Michael