I have a part definition, to which I want to attach a material with a Geomety Map defined. When I look in the Render Properties of the Family/Part editor, I see a Render Palette can be assigned. When I go to RMC > Properties, I can open the Material Editor, in which I can open a Palette to see the materials available in dgnlibs. I can go RMC > Assign To Part, which gives me the option to assign it to a part.
I notice sometimes the material seems to be coming from a dgnlib file (see image 1), sometimes from the local file (see image 2). I don't seem to be able to edit this in this menu. It seems once the material is somewhere local in the file, it refers to the local file, which I think you should avoid in the Part libaray (since they are for all projects with that Dataset).
This post is moved to English queue.
does no one know how to add rendering materials, a help file? a wiki? where to find an in detail description how to use material libs for partsif possible: how to add a hatch/ with annotation properties to elevations
I haven't worked much with materials in quite some time so had to search around for the relevant details. First, as mentioned in this thread you can define the variable MS_DEFAULT_TO_EXTERNAL_MATERIALS so that materials are stored only in libraries: https://communities.bentley.com/products/microstation/microstation_visualization/f/visualization-forum-1977638070/57780/how-can-i-stop-local-copies-of-materials/136670#136670
There used be a separate variable MS_LOCAL_MATERIALS but that was deprecated in CONNECT Edition.
After, you can use the commands that Jerry outlines in this Visualization forum thread (near the bottom) to Convert/Export/Copy local materials to shared library versions. https://communities.bentley.com/products/microstation/microstation_visualization/f/visualization-forum-1977638070/90916/local-material/260471#260471
About half-way down Jerry also describes scenarios where you can use local copies to try out changes, and then when ready, either save them to your libraries (vs. messing with the shared versions) or overwrite those local changes with the stored versions.