i built a model with pro-E 3.0 and , when i try to import it into Gambit 2.2.30 as a IGES file, i always recive the message: ACIS error 1015. Sometimes some IGES files works if i put the NATIVE option on import window in Gambit, but i don't know why. Thanks for any help!

hi i think this is because of the version difference.GAMBIT 2.2 is the new version while the PRO Es one is a older one.Try to use the current version of PRO E...also u ll see that many surfaces wont be imported in gambit(i faced that) bcos of the version mismatch and also better to use .SAT format for import(personal experience)..

Hi first thanks to answer me. I though that pro-E 3.0 was the last one version. Despite that, when i export an IGES file as solid from in pro-E 3.0,i recive two different answer. If i use Native translator on Import options section, the answer is: " Entity type 186 has not been implemented". Otherwise using spatial translator: " Scale 1 spatial". If i export an IGES file as surface, with spatial translator:"ACIS error 1015" and,with native, Gambit read the surface. P.S. I still didn't try to export in .SAT

I'm assuming you mean Pro-E Wildfire 3.0... (there's a big difference... Pro-E 3.0 is old... very old... and Wildfire 3.0 JUST came out, so I don't think a lot of people know about it yet... I think that's where the confusion on that came in).

I've always had better luck with step (*.stp) files between Gambit and Pro/E. But it depends on your geometry. Remember, Pro/E works on relative tolerancing for model details (the minimum edge accounted for is a certain percentage of the overall dimensions of the model) but Gambit runs in absolute tolerances (it's unitless, so whatever units you brought in, its 10e-6 of that). If you have a large model with small details, you can run into problems with Pro/E exporting any file (SAT, IGES, STEP, etc) because of the way it interpolates to that minimum relative tolerance. Then, when Gambit reads in the file it will try to interpolate these errors all the way down to 10e-6, which can compound the problem. If this is the case, then you need to simplify your model, or you need to create the geometry in smaller chunks and assemble them in Gambit.

Hope this helps, and good luck, Jason

nice discription jason.Thanks..Hey r u a part of ESI..i think i know you.pls ignore if iam wrong..

thanks, Deepak

Thanks. I'm not even sure what ESI is though, so I think you've got the wrong guy

Have a good one, Jason

Sorry for my mistake and thank you for the lesson! I didn't know that there was this larg difference: of course is a wildfire 3.0. . However exporting in .SAT format gambit reads well. Thanks guys!

ha ha..k jason..no problem..

deepak..