command "collapese" (including geometry) creo 3.0

[320i S]

hi to all, I recently had to correct many files of other cad to be able to use them in creo 3.0, on many I used with extreme utility, the collapse command (i.e. "comprimi geometry" for the old versions).
Recently, however, I came across a file, where this command is disabled at the time of importation (.step)
I do not find a reason why some files the command is active and in others not.
Has anyone had a similar problem?
Thank you.

 

[nicksoft]

hi to all, I recently had to correct many files of other cad to be able to use them in creo 3.0, on many I used with extreme utility, the collapse command (i.e. "comprimi geometry" for the old versions).
Recently, however, I came across a file, where this command is disabled at the time of importation (.step)
I do not find a reason why some files the command is active and in others not.
Has anyone had a similar problem?
Thank you.

I never used it.
I throw it there: is not that the step you are trying to import is of only surfaces?

 

[320i S]

Yes, but precisely the flaw when I have situations of imported surfaces, with obvious errors that do not close
in model environment, I create a solid or other surfaces, then normally select what done, and with "comprimes" I have everything inside the import group.
within the import and settlement group and in 99% of cases, I resolve and close.
the problem is that with a couple of files generated, this command is disabled and I have not yet managed to understand the reason (bug, purely technical motivation or that).

 

[BFausto]

Hi, I'm trying to answer you.

I usually happen when, after importing geometries (step, iges ...), I go to create family table on that part. to solve gate from memory any variations, I gate the family on the side, I buy geometry, I regrow the family as it was (however you do tests).

 

[320i S]

Okay, thank you for the answer, it's definitely an element that I'll consider, but in my case, it's not family table, but it's part by itself.

 

[BFausto]

Hi.

if it can be help use creo3 m110 or look at this link
https://www.ptcusercommunity.com/message/230637#230637

 

[320i S]

thanks to the link.
from what I understand, we are talking about recognizing the features in imported mathematics, but it is not my case, because it is peculiarly shaped with complex surfaces of other programs (catea and similar), which makes it impossible to acquire the features directly from creo.

my problem instead concerns the comprim command that "disappear" independently if imported mathematics is very complex or not.

I came to the point of calling into question also the start part that I use for import.
I'm testing you, I keep you updated, but I'm always open to other tips.

thank you all again.

 

[320i S]

update: it seems that the main cause is due to the start part used, now I have the doubt either because it was in family table, or that it was still made with wildfire 3 or both. .

 

[BFausto]

Hi.

a tip that I can give you is to do some tests on copies of imported files (I don't get to touch production files).

 

[320i S]

Hi.

a tip that I can give you is to do some tests on copies of imported files (I don't get to touch production files).

thanks to the advice and in fact you are more than right, fortunately my are always unique orders to lot 1, so the risks are almost zero.