Skip to main content
B
bmancini15-Moonstone
15-Moonstone
November 26, 2022
Solved

Problem with "Make Default" command of combined states

  • November 26, 2022
  • 1 reply
  • 3348 views

Hello everyone,
i have a problem with combined states.
I have defined a new combined state named "NEW" and I would like this combined state to be read instead of the default "Default All".
N.B. my goal is to have a new combined state set by default while preserving the original default combined state.

This is the starting condition:

bmancini_0-1669456835486.png

 

If I right-click on the new combined state "NEW" the program allows me to set it as "Make Default", it would seem a perfect command for my case, and instead even setting it and saving the model, when the model is reopened the combined state is returned the original one by default... why?

This is the result by activating the combined state "NEW" and setting it as "Make Default":

bmancini_1-1669456988561.png


This is the result when I reopen the model:

bmancini_2-1669457092737.png

 


Is it normal for something like this to happen?
How can I fix it?

Thank you.
P.S. I use Creo 9.0.2.0

Best answer by pausob

LOL, you'd think it would work that way.  I kind of expect combined states to behave weirdly as they are related to annotations and PTC has really made a mess in that area.  Though I'm still using Creo 4.0 and assume that they fixed /enhanced some of these functions in newest versions.  For instance, switching to "Default All" state, my system still displays the layer state assigned to the previously active combined state.  Anyway, I do suspect that you are trying to use these combined states in a way that PTC has not intended.  I am not quite sure how it was intended, but these combined states do not seem they are transferrable/shareable/accessible outside of the current model.

 

Anyway, it looks like the "Make Default" function only affects publishing to Creo View format?

See Creo Combination States and Model-Based Definition (MBD)  

pausob_0-1669486261622.png

or this idea: Make default for combined states should work for view manager in Creo Parametric

 

1 reply

P
19-Tanzanite
pausob19-TanzaniteAnswer
19-Tanzanite
November 26, 2022

LOL, you'd think it would work that way.  I kind of expect combined states to behave weirdly as they are related to annotations and PTC has really made a mess in that area.  Though I'm still using Creo 4.0 and assume that they fixed /enhanced some of these functions in newest versions.  For instance, switching to "Default All" state, my system still displays the layer state assigned to the previously active combined state.  Anyway, I do suspect that you are trying to use these combined states in a way that PTC has not intended.  I am not quite sure how it was intended, but these combined states do not seem they are transferrable/shareable/accessible outside of the current model.

 

Anyway, it looks like the "Make Default" function only affects publishing to Creo View format?

See Creo Combination States and Model-Based Definition (MBD)  

pausob_0-1669486261622.png

or this idea: Make default for combined states should work for view manager in Creo Parametric

 

P
19-Tanzanite
pausob19-Tanzanite
19-Tanzanite
November 26, 2022

@bmancini, out of curiosity, why are you trying to have the default state be something other than "Default All".  In other words, why not just work in Default All state?

Keep in mind that Default All state uses the user-defined default appearance and (for assemblies) user-defined default simplified rep (and not Master)

 

pausob_0-1669488486783.png

 

B
bmancini15-MoonstoneAuthor
15-Moonstone
November 28, 2022

Hi pausob,
thanks for the replies,
in one of my procedures, I need to save the look of the model, change it temporarily, and then recall the original look at a later time.
Not being able to use the combined states, I defined two macros that work directly on the "Aspects" and I got my goal.

In short: The procedure I have in mind is to display the non-validation status of the model using its visual appearance.

Terms & ConditionsCookie settingsAccessibility statement