Talk about timing- I have recently been dealing with a .igs file as well. Deep Exploration did not import it well at all and 3D Max just choked on it.
I imported it into AutoCAD where it looked relatively decent and exported it as .fbx. SoftImage imported the .fbx really well with just a few pieces out of place. I think I got lucky this time since in the past I've had a hard time wrangling with .igs files and know how messy they can be. Thank you, Oliver for the question and thank you all for the responses and advice, I'll be checking into the recommended file formats and MoI since I'm sure I will end up more of these file formats to work with in the future. Christy -----Original Message----- From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Leoung O'Young Sent: Wednesday, August 14, 2013 10:57 AM To: Stephan Hempel; softimage@listproc.autodesk.com Subject: Re: Dealing with CAD files format Thanks for the info. On 8/14/2013 10:55 AM, Stephan Hempel wrote: > I don't know. As far as I know MoI imports only 3dm, iges, sat, step, > ai, eps, pdf and dxf. > > No Parasolid files. > > >From MoI I export obj. And with the export options you have good > control over the resulting mesh. > > Stephan. > ______________________________________________________________________ > eisblau | produkt + prozessvisualisierung | animation + visual effects > > Stephan Hempel > stephan.hem...@eisblaufx.net Tel +49.(0)3643.251186 Goetheplatz 9b > www.eisblau.de Funk +49.(0)179.1356295 99423 Weimar > > am Mittwoch, 14. August 2013 um 16:36 schrieben Sie: > > LOY> Stephan, > > LOY> So Step files are better than Parasolids files? > LOY> Are you exporting obj from MoI to bring into XSI? > > LOY> Thanks, > LOY> Leoung > > LOY> On 8/14/2013 7:43 AM, Stephan Hempel wrote: >>> Hi would strongly recommend step-Files and convert them with MoI. So >>> you have full control over how the geometry gets meshed (MoI has >>> quite some options for tuning). And ask the client to keep the >>> assembly groups intact. So you have all building blocks properly >>> named as separate objects and don't have to deal with one single >>> piece of geometry. This way I had never any problems. >>> Try to stay away from IGES. I had always problems with missing >>> surfaces. >>> STL and WRML exports are already meshed. So it can be a bit of an >>> problem to clean the geometry. >>> >>> Stephan. >>> >>> am Dienstag, 13. August 2013 um 22:15 schriebst Du: >>> >>>> Hi guys, >>>> Next week I shall receive a mecanical pieces generated with Solidworks. >>>> Because I'm dealing with an agency, they might won't be able to >>>> send an obj or fbx file. >>>> They propose various formats : >>>> Assemblage or Assembly (.asm) >>>> Part (.prt) >>>> Parasolid (.x_t) >>>> Iges (.igs) >>>> Step AP203 or AP214 (.stp) >>>> IFC 2x3 (.ifc) >>>> ACIS (.sat) >>>> STL (.stl) >>>> VRML (.wrl) >>>> Universal3D (.u3d) >>>> 3Dxml (.3dxml) >>>> Catia Graphics (.cgr) >>>> So my question is, what format should I ask and what software would >>>> you recomend to open and save it in a classic polymesh format ? >>>> (preferably >>>> free...) >>>> I have an old Deep Exploration, I was thinking giving it a try. But >>>> if someone has a cool winning format + software to advice... >>>> Thank you ! >>>> Olivier >>> >>> > > CONFIDENTIALITY NOTICE - THIS E-MAIL TRANSMISSION MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL, PROPRIETARY, SUBJECT TO COPYRIGHT, AND/OR EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. IT IS FOR THE USE OF INTENDED RECIPIENTS ONLY. If you are not an intended recipient of this message, please notify the original sender immediately by forwarding what you received and then delete all copies of the correspondence and attachments from your computer system. Any use, distribution, or disclosure of this message by unintended recipients is not authorized and may be unlawful.
