Skip to main content
Jun 26, 2025 3:49 PM UTC
Acknowledged

Color Manager added to View Management

Related products:Creo Parametric

1. Describe the Problem

I would like to have a color management system in Creo Parametric.   This would be similar to simp-reps and styles.   I'm not aware of a tool to save different surface/component colors and quick switch back and forth.    


2. Are you using a workaround?
Just living with having to choose one set of colors or another.

3. What is the use case for your organization?
The main function would be to be able to save different color configurations for a part and assembly.   One use case is that when engineering its nice to have contracting colors from component to component, but when presenting a product to customers its nice to have the design have surface colors which represent the final product.    This would also have applications in communicating design functions such as identifying machined surfaces, or components with different material properties.  A simple Color Manager would be a nice addition, and then advanced features like rule based coloring could be nice as well, such as •In Color Set 1 "if surface is in a specific Data Reference Group (Reference 1), then make it orange" •In Color Set 2 "if surface is in a specific Data reference Group (Reference 1), then make it Deep Candy Blue"

4. What impact does this problem currently have on your organization?
There is a additional work to communicate design intent and different design stages. Or, special assemblies are needed to capture color states.

6 replies

Community Manager
Jun 27, 2025 8:53 AM UTC
Status changed to: Acknowledged

Thank you @N.Barnes 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.

Jun 27, 2025 7:08 PM UTC

@N.Barnes 

 

Hello @N.Barnes ,

 

I think half of what you are requesting already exist.

It's in the View Manager, on the "Appearances Tab".

 

https://support.ptc.com/help/creo/creo_pma/r12/usascii/?_gl=1*1qjk1wd*_gcl_au*OTQ2NDE0MzIxLjE3NDQzMDI2MDIuMjAxNzUyMjg4NS4xNzUxMDQ4NTAxLjE3NTEwNDg1MDE.*_ga*MzU0MzYxNzAxLjE2ODk4NzAyMDQ.*_ga_7NMP2MSYPM*czE3NTEwNDg0OTYkbzQ4MSRnMSR0MTc1MTA0ODg4NSRqNDMkbDAkaDA.*_ga_CBN5QVB9VJ*czE3NTEwNDg0OTYkbzE5MyRnMSR0MTc1MTA0ODg4NSRqNjAkbDAkaDA.#page/assembly/asm/About_Appearance_States.html#

 

The link is for Creo 12.4, but it already exists even in Creo 7 or even earlier.

 

This allows to have a view state where the user can assign different colors, and quickly change state. This allows to have a color scheme with colors assigned for rendering or presentation, and another color scheme with high contrast to better see the different parts.

 

One problem though, is that the View Manager on the Appearances Tab in assembly mode does not allow to quickly select different appearances schemes in the parts or sub-assemblies based on a top level rule. For inistance, the Simplified Reps allow the user to select a simplified rep name on a sub-assembly based on rules, that can be automatically selected, like if the sub-assembly as also a simplified rep with the same name.

 

With current functionality, as far as I know, the user cannot force the sub-levels of an assembly to also switch assembly appearances based on the parent selection. So, the user has to manually change appearance states individually for each part or for each sub-assembly, which is time consuming, but still better than the old ways where the user would have to re-assign colors for each part whenever he needed to switch color schemes.

 

I noted that you already voted for my suggestion to improve Creo to allow to parametrically define surface colors on feature creation or based on parameters:

 

https://community.ptc.com/t5/Creo-Parametric-Ideas/Parametric-surface-selection-as-model-tree-features-to-color/idi-p/762287

 

In that already dated feature request, some of the requests have already been implemented, like "Copy Geometry" feature, that already has a checkbox to better control color propagation, others still need further improvements. Also, there are some inconsistencies between features about which reset colors (assigns default color) and which propagates them. For instance, Flexible Modelling Offset feature preserves the color of the original surface, but regulr offset, uses the default color. Body Boolean operations already have controls to allow propagation or not of the original body colors. But pattern features, do not a pattern the colors of the original features' surfaces. Mirror features or Mirror Geometry, also need to allow the user to propagate (or not) the original geometry colors, to avoid having the user to waste time coloring a mirrored body or mirrored geometry. These inconsistencies need to be taken care of, gradually.

 

But the most important for your requesst, is the parametric generation of colors at a feature level and the decoupling of the current method of assigning colors to surfaces. It would be usefull to be able to constantly have to sets of color schemes, on all the parts, one used for rendering, and one for regular work. For regular work, the user does not need dozens of values to define an appearance, such as "Color", "Intensity", "Ambient", "Shine", "Reflection", etc. This should be only used for rendering. And the "Color" on the Appearance Editor should be parametrically linked to a new parameter type called "Color" that would be a 32 bit number defined as a string to specify a for byte values in hexadecimal) or to 4 Byte values (0.255) to specify the RGB and Alpha values of a color). So, if the user changed a parameter to specify the color of a product,,from red to blue, the parameter value would automatically assign the "Color" value on the Appearance Editor.

 

Another improvment is to allow the user to provide the color at feature creation, on the "Properties" Tab where the user can change the feature name. Add an additional field (or fields) to allow the user to specify a specific color for the feature (or use the default). Also, allow the "insertion" of a feature in the model tree, to specify a default color to be used by the next features, until another feature changes again the default color(s). There are cases where the user might want that a feature use more than one color for the generated surfaces, like in threaded holes, for example (one color for the regular hole, one color (with texture) for the threaded portion of the hole.

 

So, besides allowing parametric specification of colors at the feature level, Creo should provide on a global level, global scope, methods to quickly switch from "Presentation" or "Rendering" color schemes, to regular color schemes without forcing the user to open each sub-assembly or each part to change that. And even in the "Regular" color scheme, there should also be a method to quickly change the color scheme between several possibilities. For instance, if we assign a color "Red" for precision machined surfaces for one client or custumer, and another client wants precision machined surfaces to be color coded "Blue", the user should have the option to quickly change color schemes based on client or customer, wihtout having to open each part and change the part to visualize in that color scheme. This is important for "Library" parts. Since we should assign those colors based on the surfaces funcionality, but we have to assign one color for the library part, but if we use that part in a project for a client with a different color scheme, we should not change the part at all, but simply use a color scheme manager to reassign the colors on the fly, based on user selected color scheme for a particular project.

 

I know this post is long, but I would appreciate very much @mneumueller comments or feedback, becase the color management in Creo is one of the most annoying and frustrating issues, that has the most complaints of my colleagues that work with Creo for almost 20 years.

 

 

Jun 27, 2025 7:42 PM UTC

One of the other annyoing features of coloring surfaces in Creo, is that it's not parametric, despite the name.

 

The user colors surfaces as if assigning color to a dumb solid or dumb set or surfaces. That I mean is that if the user changes a sketch that adds another line to be extruded by an extrude feature, the new entity, the surface generated by the added line in the sketch, is not automatically painted as the user might want, having to constanly change colors "à posteriori". And if the assigned color is very important, like marking surface finishes, it might lead to errors whenever the user has to Redefine a feature or a sketch that generated new geometry. This should be improved as specified in the previous post, to allow the user to parametrically select a default color at a part level, that can be overriden by a parametric feature on the model tree, to speify default color for subsequent features, which in turn should be able to be overriden on evey feature that creates or changes geometry. This could be added on the "Properties" tab of evey feature. Adding a checkbox to specify "override default color", and a field to let the user choose an RGBA value.

 

Besides having a feature to specify a default color (instead of the regular gray) at part level, to parametrically control color generation of specific features or consecutive ser of features, another useful way to parametrically color surfaces, is another feature on the model tree, to be used to parametrically select surfaces based on the various selection methods of Creo, to specify colors in bulk. This would allow the user to color the surfaces at the end of the modelling process, instead of during (at the feature level), but to have the process be parametric, meaning, if the user uses the "Surface and Boundaries" method, when regenerating, whatever surfaces this selects, the feature will change the color of all the surfaces selected. Currently, with the appearances menu, the user can use Seed and Boundary but the process is not parametric, so, if the initial geometry changes, with new geometry created, the user hase to be attentive to color the additional created geometry. Another methog of selection of geometry, is to specify or click on the model tree a feature, and it's geometry will be considered parametrically selected. Or a model tree feature range, from start to end of selection, all generated (ie, extrude, revolve) or modified geometry (ie, draft, offset) will be parametrically selected to be able to change color. 

 

Another improvement, is related to External Merges or External Copy Geometry. Since each surface color appearance has so many, so many attributes assigned, to be able to be used for rendering, ie, shineness, reflection, etc, it is difficult to compare all those attributes when getting external geometry, to check if the color already exists on the new part. So, what ends happening is that Creo will create multiple copies of the sourse appearances, even if in the target part the user already has an appeatance with the same name, and same attributes. (since thet can be changed in the external part, even if the appearance name is the same). If we only use a simple 32 bit value to specify surface color (on the regular color scheme), then the Creo will be much faster to compare if the same color is already used in the existing part, to avoid Copying an appearance or color that is also used in the external part. It only needs to compare the color name (if we use libraries to specify surface finishes) or a single 32 bit value if we consider a specific color value. If we only use a single 32 bit value to specify surface colors, probably regeneration times will be much faster, and allow better real-time change of color-schemes on the fly using an OpenGL shader program, instead of having to change color schemes for individual parts for all the parts in an assembly.

 

Sorry for the long rant, I'm just trying to contribute to improve Creo further.

 

Regards, Sérgio.

N.BarnesAuthor
Jul 1, 2025 8:06 PM UTC

Interesting.   I learned a few things today.   I don't know how I didn't know about the basic functionality.

 

I agree with many of your points about making the color selection should be more parametric and stable.   

Being able to set all the surfaces created or altered by a feature could be very powerful.   

 

Thank you for the response.

N.BarnesAuthor
Jul 3, 2025 7:03 PM UTC

Sérgio,

 

I think to compliment the improved color management system.  There should also be a "Color Query".   Allowing the user to determine "why" a surface has a specific color assigned.     For example is the color being assigned by a copy geometry feature, manually assigned, assigned at a feature level, or is it default from a lower component level.

 

Also, as you hinted at with the mention of  "Intensity", "Ambient", "Shine", "Reflection" there are quire a few color parameter that may need to be managed.   Many more items than a simple RGB values.   Store color data could get quite large if each file has to carry all of its own texture and bump files as well.   Which could mean that only basic number value items are stored "in model" and auxiliary information is stored in the color libary and that is where your proposed 32 bit checksum might help with file size management.     Don't want each assembly to become hundreds of GB of texture and bump files like modern AAA games have become.  

 

-Nick. 

 

 

 

Nick 

 

Jul 8, 2025 10:15 PM UTC

Hello @N.Barnes 

 

I hope the Appearance manager could solve part of your problems and use cases. I'm glad I could help if that was the case.

 

There are different workflows for which one method of assigning colors makes more sense than others.

 

I find it perfectly normal that PTC first devised the current method. In which CAD users first concerns are creating the appropriate geometry, and only as an after thought might consider assigning colors to the parts or surfaces for aesthetics or presentation only, ie, rendering. They don't need to be concerned to assigning colors at each feature, which would slow down the design process, in the same way as we don't assign a feature name in the feature properties tab each time we create a feature.

 

But for the other use case, where we need to color code the surfaces to express for example manufacturing surface finishes or quality, it makes more sense to assign the color parametrically at the feature level, since the designs are subject to changes, with new geometry added all the time, in the same feature, and to avoid errors and uneeded time to manually change colors of newly added geometry. When we know a feature sequence will all generate surfaces or geometry to be machined using the same "surface finish" which is encoded in a specific color, to avoid having to specify colors one by one at each feature, we could simply insert a feature at the start of the sequence which would specify the  "default color" of all the subsequent features, unless overriden at the feature level, or another "default color" feature is specified. We could use the "default color" feature as a way to override even other internal values used by Creo at part level, and two that i could remember at the moment, is the value of "accuracy" or the internal kernel flag to allow or not to simplify geometry after each feature (for instance, removing edges of coplanar faces). There are situations where it would be useful to override the default values at a specific time-stamp in the model tree, and restore those values later.

 

About the colors assigned to surfaces, I don't know the internal structure of the Creo kernel, but I assume that each surface has at least an "hash" value to associate it with all those rendering parameters that show in the Appearance Editor, suitable for rendering. The idea of assigning only a 32 bit value, or 4 bytes RGBA values, is because it's a straightforward way and an one to one association with what the graphics API needs to display the colors on the screen using OpenGL. And for the use cases not associated with rendering, we don't need to assign each color a shineness value, or reflectivity, etc. We should only specify the diffuse color value. Which can be parametrically linked to the "Color" field in the appearance editor as a parameter. The textures and bump maps that can be used in the apperance editor are not internally saved in each surface, only referenced once in the appearance editor, so, my suggestion would not increase file size, probably would decrease it, even though not significantly, even though a method would need to be devised to keep backwards compatibility.