Skip to main content
M
MasterDrew1-Visitor
1-Visitor
February 28, 2018
Solved

Creo 3, strange bug with draft dimensions not updating properly

  • February 28, 2018
  • 1 reply
  • 6201 views

Hello! I'm looking for some help tracing down a really weird error; On a few of our template drawings, (drawings & models that we save-as from repeatedly), certain dimensions on the drawing don't update properly after the model is updated.

 

That is to say, we'll update the model and regenerate, then switch windows to the drawing and most of the dimensions will have already updated. However one or two will sometimes change to some garbage value, neither what the dimension was before nor what it should be now. A manual regenerate of the drawing will then update these wayward dimensions to the proper value. The problem is that most of the dimensions will update correctly leading the user to think the drawing is fully updated and ready to print without doing a regen of the drawing.

 

We are currently running the following config.pro options, which makes me think it’s not an issue that the drawing itself isn’t updating.

save_display no

auto_regen_views yes

I'm trying to figure out the root cause of this issue, and ideally there's some sort of config option to fix this... As it stands a small percentage of our thousands of template files seem to be affected. However I can't seem to figure out what the pattern is between the affected dimensions. on affected drawings, deleting and re-creating the dimension seems to fix this issue... However to go through all of our templates, and previous jobs that we save-as from would be tens of thousands of drawings to completely re-do the dimensioning to track down this weird little bug.

 

I've attached an example if you want to recreate the error. on first opening the drawing should look something like this:

 

error capture1.PNG

 

 

 

 

 

 

 

 

 

Then switch over to the top level assembly and change the overall length. That can most easily be done by changing the parameters QTY or DIA in the relations. Then regenerate the model to update it.

 

Then switch back to the drawing. All changed dimensions on the drawing should update automatically, except the overall length dimension will have updated to a junk value:

error capture2.PNG

 

 

 

 

 

 

 

 

Then regenerate the drawing, and the overall length dimension will update to the correct value:

error capture3.PNG

 

 

 

Best answer by TomD.inPDX

I'm going to suggest you create a support case.  You have all the evidence you need to have a qualified tech explain exactly what is going on.  I've had good luck with this with PTC support regarding the functions under the hood.  If the reply is not satisfactory, you can escalate the case.

 

Obviously you are not seeing things and you also see what it takes to have a reliable drawing update.

PTC owes you an answer. 

Community members may know as well, but getting a clear understanding may need to come from the source.

1 reply

T
TomD.inPDX17-Peridot
17-Peridot
February 28, 2018

Sometimes references require a double regeneration.  Could this be your issue?

M
MasterDrew1-VisitorAuthor
1-Visitor
February 28, 2018
@TomD.inPDX wrote:

Sometimes references require a double regeneration.  Could this be your issue?

Hey Tom,

I guess so... Regenerating twice does seem to make the dimension update to the correct value. The confusing thing though is the vast majority of the dimensions all update properly after one regeneration. So it's relatively easy to miss one dimension. Especially because this only seems to occur on a small subset of our drawings.

What makes a dimension require a double regeneration? Especially when the model is already fully regenerated before even going to the drawing?

T
TomD.inPDX17-Peridot
17-Peridot
February 28, 2018

You have the opportunity to create associated dimensions to many things.

Just shy of a circular reference is the relation reference that updates and has another relation reference tied to it.

If you work a lot with relations, this is easy to do.

 

A relation reference as noted here is a value driven by relations.  Relations within a sketch are the likely culprit.  Moving these relations to the feature level may help.

Terms & ConditionsCookie settingsAccessibility statement