Skip to main content
Jan 14, 2026 11:22 AM UTC
Acknowledged

Driving dimension should use default_dec_places value when formula is used for its calculation

Related products:Creo Parametric

1. Describe the Problem

Default_dec_places is not working as expected in a specific case - see video attached.

Default_dec_places works correctly, when dimension is defined by an equation in the feature creator.

When driving dimension is modified by the same equation - resulting value has more decimal places.

Result dimension should have the same number of decimal places as specified in default_dec_places, or user should be clearly informed  (maybe with a pop-up message) that displayed and actual dimensions are different.

 

Summary:

 

  1. Feature definition : dimension specified as 360/7, dimension - 51.429. Displayed dimension rounded to 51.429. Geometry length – 51.429 –  Correct
  2. Driving dimension modification: dimension specified as 360/7. Dimension - 51.42857142857. Displayed dimension rounded to 51.429, Geometry length -  51.42857142857 - Incorrect


2. Are you using a workaround?
No workaround available. default_dec_places value is not respected, when driving dimension is edited.

3. What is the use case for your organization?
Using formulas to change position/size of a already created feature.

4. What impact does this problem currently have on your organization?
Difference between displayed and actual dimension can cause issues and wasted time in downstream processes like simulation, manufacturing, etc.

4 replies

Jan 14, 2026 10:58 PM UTC

We actually prefer that calculated values have the maximum possible accuracy, and only when displaying its values do they need to be rounded up to save space on the dimension text.

 

If we use a relation to evenly space some holes, like 100mm/4 holes (3 spaces apart -> 33.3333333333333mm between each hole), we want the distance to be as much as possible eaqual between each hole (within the floating point accuracy). If we display the dimension, obviously it can be trimmed down to for instance 2 decimal places. But if the calculated distance was somehow rounded to only two decimal places, it would mean that the first 3 holes would have a distance (fpr example, 33.33mm), and the distance between the 3rd and 4th hole would have a different value (33.34mm).

 

If you want the calculated value for the increment to be rounded up to only (for instance, 2 decimal places, as in default_dec_places), you could use a relation formula to trim the additonal decimal places, to only use 2 decimal places, achieving what you want. If the calculated values would be automatically rounded up in all cases, you would prevent the users of using maximum precision or accuracy when it is very important and needed.

Jan 14, 2026 11:10 PM UTC

In cased the user wants to achieve this goal, it's better for PTC to provide an additional function that would automatically round (up, down, or evenly) to the same amount of decimal places as specified in config default_dec_places.

 

Otherwise the user can round the formula up with ceil(value, dec_places), down with floor(value, dec_places), or evenly with floor(value + 0.5, dec_places).

 

Here the only problem is that (dec_places), the intended number of decimal places, is available as a config.pro value, but not as a parameter. So, an additional relation function would be advisible and not too complicated to create, which could be named def_dec_places_round(value, dir) <- here the number of decimal places would be taken from default_dec_places from config.pro, and dir would be an integer, with positive values to round up (ceil), negative values to round down (floor), and zero integer value to round evenly (nearest to the default accuracy number of decimal places).

Jan 15, 2026 4:08 AM UTC

In the Creo user interface, the rounding behaviour is definitely inconsistent so I am arguing that the system should be made consistent.

 

I would prefer that the system does _not_ round the value that has been input by the user (whether by typing in the digits, or via specified in-line formula, or in other times when the system auto-populates the input fields)

Seems this "loss of the digits supplied according to default_dec_places setting" occurs when feature is initially being created.

But when modifying established dimensions of a feature, or when making or editing a sketch, the system only rounds the display of the dimension value (the actual value retains many decimal places if necessary)

I'd prefer that they make all inputs work the same way as what happens in the latter scenarios.

 

Clearly, others have other preferences, so a config.pro setting that would govern the consistent behaviour would probably be the best solution.

 

 

@MK_10225854 , you can ensure that the displayed and actual dimensions values are the same by setting the config.pro setting round_displayed_dim_values to no (default is yes).  Keep in mind this only works for new dimensions.

Community Manager
Jan 15, 2026 7:43 AM UTC
Status changed to: Acknowledged

Thank you @MK_10225854 for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.