>>interesting idea... If you wanted to send a file to another person, would that mean that you would have to send both an .xml and a .3dm file to them in order for them to get layer data?


I suppose. It does get bloated when you bring all the stuff in. The MoI "Assembly Exporter" could automatically "zipp" the required stuff if needing to share all the "added features" with others. The zip file could have a proprietary extension that then needs never be unzipped, MoI's "Assembly Importer" unzips the 2 files uses them, anytime an assembly is closed, it's just zipped up again. Something only utilized by those that require it. A "Moi.assm" file if you will.

It could get bloated when considering all the possibilities. I would think this could also be a third party tool if later MoI could expose the "Objects" through some kind of SDK. This could open the door (down the road) to incorporate database feature based modeling and have MoI be "third partied" into a full featured high end assembly package.

Seems for the common man, and probably your main target, alot of this kind of stuff is not considered or desired, but you have such a great product, your attracting Solidworks/nx users who want/can utilize the heavy stuff.

It could just be understood that if this is used in the process, there are some steps that have to be adhered to. (the whole reason opposite of your vision of MoI! :) but satisfying your high end clients.)

Again, it's just 2 cents from the peanut gallery!

Burr