Skip to main content
A
Adam1310-Marble
10-Marble
July 12, 2018
Solved

Modifying references - Constraint type changes

  • July 12, 2018
  • 1 reply
  • 4852 views

Hi!

When I try to change a Distance reference in the Placement tab, the constraint type changes from Distance to Coincident. It's like Creo treats Coincident as default and sets all new or edited constraints as "THIS SHOULD USE THE DEFAULT VALUE". Is there a way to get Creo to keep the constrain type, after a reference change, when it's previously been set?

 

To clarify: I've got two parts where the bottom of the top part has been constrained to have a distance to the top of the bottom part with a offset value. Let's say I want to change the reference on the bottom part and have the distance to the bottom surface instead of the top. If I make this change via Edit definition > Placement tab Creo changes the constraint type to Coincident (but musteriousluy keeps the value offset value greyed out in the box). Why?

Before reference change

 

After reference change

Best answer by mcestnik

It's a config.pro option. You probably have auto_constr_always_use_offset set to never. That's why it changes it to coincident. If you set it to No it should work OK.

1 reply

D
dgschaefer21-Topaz II
21-Topaz II
July 12, 2018

No, and it's maddening.  The software should not change the design intent on its own.

 

You may want to "Kudo" this idea:

 

https://community.ptc.com/t5/Creo-Parametric-Ideas/Assembly-constraints-should-not-change-to-coincident-when-set-to/idi-p/456284

 

In the comments there is a work around.  It's a bit of a kludge, but it looks like it allows you to keep the value anyway:

 

https://community.ptc.com/t5/Creo-Parametric-Ideas/Assembly-constraints-should-not-change-to-coincident-when-set-to/idc-p/456294/highlight/true#M1661

    A
    Adam1310-MarbleAuthor
    10-Marble
    July 13, 2018

    Thank you! Good to know that it's Creos fault and not mine.

     

    I kudo'd the idea you linked. We'll see what the future holds 🙂 

    M
    mcestnik14-AlexandriteAnswer
    14-Alexandrite
    July 13, 2018

    It's a config.pro option. You probably have auto_constr_always_use_offset set to never. That's why it changes it to coincident. If you set it to No it should work OK.

      Terms & ConditionsAccessibility statement