Item showing in grey

[gbarrettVEH2Z]

Hello!  I have searched all over, tried some suggested solutions... and I cannot get this item to show anything other than grey when I Render in Revit 2023.  This is a downloaded family, so I don't know what program it originated in.

Tried:

1. Phasing settings.  It shows grey whether it's set at "Show Complete" or "None."

2. Adjusted colors in Object Styles.

3. Changed from Generic to Furniture.

4. Re-downloaded a DWG file from the source, changed its color in AutoCAD, re-imported into Revit.

Here's how it looks when I'm inside the family itself, in Realistic 3D (this was all grey before I changed the Object Styles, and you can see the pot still is... not sure why):

Here it is rendered in my Project:

Help, please and thank you!

[gbarrettVEH2Z · Accepted solution]

OMG, I actually did it!  It occurred to me that I hadn't adjusted the Object Styles in the project, but in the Family.  So I tried that, and it worked!

You have to adjust the Object Styles in the Project (Manage tab > Settings > Object Styles).  Also, per other similar advice I'd researched before, I checked all of the Use Render Appearance boxes of each material after adjusting the color in the Material Browser under Appearance > Generic to the right color.

[SteveKStafford]

When a family is first loaded into a project, and that family has new information the project has not seen yet, the family will pass along that data. Once that's happened the project goes into protect-mode and the family will not overwrite all the data it contains with the family's version. There are two options offered when a family is reloaded, the second (bottom) option is the one that will overwrite the type parameters associated with the family in the project using the latest version of the family. Materials however won't be overwritten because the project is trying to protect itself against external input. After the family has been loaded the project takes over management and ownership of the new material that the family originally brought in.

FWIW, it does something similar with families too. If you've noticed some families named like this: DoorFamily, DoorFamily1, DoorFamily2 etc. that's an indication that a family has been loaded with the same name as an existing family but it is different enough that Revit decides to protect the project version and it adds the number to the name. That difference is usually the original location the file was loaded from is different or a different Revit version of the same family has been loaded. For example, if DoorFamily was a Revit 2023 file and then the Revit 2022 version is use by someone to reload a change to the door we'll find that Revit protects the 2023 version and renames the 2022 version to be DoorFamily1. Multiple users loading the same family in a workshared environment can cause this too. If we need a door loaded only one user needs to do that and sync so the other users can start using the door. When more than one of us loads it and syncs Revit treats each of them as a new door family with the same name and adds the incremented number to the name. A warning appears when this happens btw.

[gbarrettVEH2Z]

Thank you!  This explains why what I did above works.  Much appreciated.