Skip to main content
A
akantor1-Visitor
1-Visitor
February 15, 2016
Question

Is it possible to assign a different color for each family table instance

  • February 15, 2016
  • 1 reply
  • 2818 views

Hello.

Beeing a rookie to Pro/E world, got a quesation: Is it possible to assign a different color for each family table instance?

Very easy task for SW, but I have no idea how to do it in Creo...

Could somebody help?


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

D
dschenken1-Visitor
1-Visitor
February 16, 2016

Of the longest running unfulfilled requests, color in family tables has got to be #1.

The usual answer is to copy/paste a large number of copies of the desired surface(s), assign them the desired colors, and then suppress all except the desired color in each instance.

One answer that should work, but supposedly doesn't, is to assign a different material to each instance, and with it, a color assigned to the material. Seems like it should work, but apparently only the mass properties/related characteristics are made accessible in the instance. The color is whatever color the generic is.

T
TomD.inPDX17-Peridot
17-Peridot
February 16, 2016

You might also wish to learn that animations using transparencies has trouble with texture-assigned surfaces.  Only the body color goes transparent, not any of the subsequently assigned surfaces of the solid body.

But as David was suggesting, it has long been requested and promptly ignored.  The material option in a family table does work to some extent, but it fails if you have two members set to different instances.  It only uses one texture for both members.  A lot of support cases quoted and :works to specification"  is always the answer.

Creo tries to be many things.  Just stuff this and that into its gut and it can do anything!  Right?  The devil is here, in the muck where someone in their infinite wisdom decided the specification was met and it has stood time.  The functionality will simply never be improved.  The ripple effect and the significance of such a change is unattainable in today's environment.  Many of these "little nits" will have to be addressed on a case by case basis.  All the more reason to be satisfied with core Creo and not worry about the fringe.

Terms & ConditionsAccessibility statement