Hi Corzair - maybe it depends on what you mean by "embedded", but MoI does not really bundle up an input object directly along with its output.

Some constructions may cause a surface edge to be created in the same spot as an original input curve, so that may look like a type of embedding, but the original curve is still there as a separate object.

Every time you create an object, MoI remembers the parameters for how it was created, and one of the parameters is the ID number of the original input curves. So there is a connection that is stored, but the actual curve object itself is not directly embedded into the generated object.

When you update an object, MoI will look to see if there are any other objects that have it listed as an input, and if there are then it will recalculate those objects (and the newly recalculated object becomes displayed instead of hidden).

> the original curve used that isnt imbedded (or so it looks to me) as
> you can move it around without effecting the loft or swept object when used for another sweep

It shouldn't work like that - if you do 2 lofts that use the same curve, when that curve is edited both lofts will update. But if you managed to either drag one of those lofts away that would break the history connection and that would behave like what you are describing there.

- Michael

Yes soory I wasnt eaxtly being clear

the endpoints are created so you have a curve object at star and end of the lofted/swept object that is created that very closely resembles
the original curves used to make that object - sorry that whole hexgon comment threw me of somewhat (hex inherited dynami geometry from amapi which can be colapsed also)

what I was doing was hiding without moving and then doing an ne sweep or loft (tryout ake a a fuselarge)
then the hidden object pops back to be displayed - obviously in the same place as my new slightly refined sweep