Hi,
I have got a .stp file from FormZ and want to export it from MoI to a .stp file again.
It just nothing happens... No file is writing. Any ideas?
I got a mac version of MoI
-file attached-

Export to step is working here, for windows7.
File, export, select klein bottle, choose file name and set the export extension...

- Brian

Did you actually select something, because..

Thanks for the support.
I don't have any clue what it could be. Maybe the system?
I go over "save as", so I don't have to make a selection. (Export with selection doesn't work neither)
No problem to write an .obj file but iges, sat and step just nothing happens. Seems to be jinxed.
It works with a simple new surface. But if I Paste this "bottle" into the file it doesn't work anymore.
Could you send to me the .step file which you has got of your export?

I have had this before on osx. If i remember rightly, you have to close MoI then open it as if starting a new model, then use the file/open to browse to the file and then open it from there. After doing things this way it exports again. I don't know why it does it, might be a file permissions thing. Just remember not to double click step files even if they are correctly associated - It could also be a folder structure that's not carrying over properly via wine. It's a nuisance though.

Martin Spencer-Ford

hi there!

i've attached the .stp file, exported from MoI 3.0 beta Aug-1-2013 on WIN 7 64 bit

~marco

Hi,

strange that you get this problem. I loaded your file and exported it as .step and also re-imported afterwards as step file and it works fine for me, with the latest beta, under OSX 10.8.5.

Regards
Stefan

Hi Jay, are you using the current Aug-1 v3 beta, or an earlier version?

I just tested using the Aug-1 v3 beta on the Mac version and I seemed to be able to make a STEP file just by loading your object and doing a "Save As".

But I see that the object has a self-intersection in it - there was a bug in the STEP/IGES/SAT import/export library where on some occasions if it saw an inconsistent trim boundary it would trigger an error in the export and the entire export would be aborted. That particular problem has been fixed in the most current v3 beta and instead in that case you should end up with surfaces exported instead of a joined object.

So if you're using an older version, try updating to the latest v3 beta from here http://moi3d.com/beta.htm and that may help.

A solid is not really supposed to have surfaces that fold back over right on top of themselves so you will probably have various issues related to that when you try to bring the object into other programs, some may just refuse to import it. You may need to slice the object up into some separate surfaces and remove some areas rather than having it all as one self intersecting piece.

- Michael

Hi, thanks to all!
The v3-beta-Aug-1 works. Everything is fine.