Skip to main content
B
BR_140829071-Visitor
1-Visitor
September 12, 2018
Question

material appeareance - no color when assigning material

  • September 12, 2018
  • 1 reply
  • 6165 views

Dear All,

 creo material appearance

I observe strange behaviour of creo in assigning colour that match material's appearance setup - part turn white after assigning material.

/my version 5.0.1.0, but it also was in previously installed 4.0/

 

Behaviour:

  • Assign material to a part
    • There is no colour - part turns white from default colour
  • I modify the appearance /default appearance/
    • Save this material - by save to library
  • Assign modified material to a part colour was taken from the material appearance correctly
  • When I turn off the creo and reopen it
  • Assign same material modified before
  • There is no colour
    • Part turns white In material properties of this material
    • Nearly all colours in material appearances window, turned white

In my config.pro appearance catalog, color.dmt file - is set to default Creo 5.0.1.0\Common Files\graphic-library\appearances

 

How to fix it? Is there any options that controls this behaviour?

 

Thanks in advance for your help.

 

Regards!

1 reply

M
MartinHanak24-Ruby III
24-Ruby III
September 13, 2018

Hi,

 

I guess that color definition must be present in global.dmt file.

J
jim110-Marble
10-Marble
November 15, 2019

Same thing is happening to me. I can see that the global.dmt is not getting updated when I define the material appearance. Set the global_appearance_file option and made sure I have write access the the file too

 

Is this a bug?

 

Creo 4.0 M070

Patriot_1776
Patriot_177622-Sapphire II
22-Sapphire II
November 15, 2019

I'm on Creo 3

 

I have a family table of parts where I swap out the material (offhand I think it is PTC_MATERIAL_NAME) for each instance.  Creo has ALWAYS had issues with this.  In my case what I found was that whatever the last appearance was in the instance either added to the assembly, or regenerated from the table, it made all the other instances that color but kept the actual correct material properties assigned to each instance.  Whew!  I don't believe that the color has to be in the .dmt file.  It shouldn't, because the model has the definition in the material.  I've changed the material of a non family table part and it updates just fine.

 

I'd say there's still a bug in the system from way back.

Terms & ConditionsCookie settingsAccessibility statement