Skip to main content
P
pstapler1-Visitor
1-Visitor
February 6, 2015
Question

Annoying Regens

  • February 6, 2015
  • 1 reply
  • 1143 views

I have several parts with a couple thousand features each. Each also has family tables including two instances with maybe a dozen columns each. I have having a couple regen problems.

Problem 1: When redefining features high in the tree (lower feature numbers) I always insert just below the features I want to redefine or suppress all other features below that in the tree. However, upon completion of redefinition, Pro/E regenerates the the entire model...every single feature...even the suppressed features.

Problem 2: Related to Problem 1, when Pro/E regenerates the model, it regenerates it multiple times...every feature.

Anyone have any ideas what might be causing these problems.

Thanks,

Patrick


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

1 reply

P
pstapler1-VisitorAuthor
1-Visitor
February 6, 2015

I forgot one other related issue. When I redefine a feature low in the tree (higher feature number), Pro/E again regens all the features above it.

Also forgot to mention I am on Creo 2.0 M130.

Thanks,

Patrick

T
TomD.inPDX17-Peridot
17-Peridot
February 6, 2015

Creo uses the concept where - when in doubt, regen! Even opening relations and accepting will flag the part for regeneration.

There are several recursive operations in regen mostly attributed (as far as I can tell) when merging features into a solid body. This was a real problem with the "Borg Cube" Feature Failure with Repeating Patterns

It should not be regenerating suppressed features. This happens only when they are made active again.

I am sure there is more rhyme and reason and hopefully someone will find a previous discussion clarifying this fully.

Terms & ConditionsAccessibility statement