The new Parametric cells when placed in a design, don't seem to be able to accept byLevel:Colour material assignments. This may have something to do with the cells definition being a bit like a shared cell. And the instance sitting on the default level???
If I pre-define materials, and pre-assign them in the cell itself, then materials are respected when placed in a design - but this workflow isn't all that useful if I want to test out a couple of different materials in the placed design.
Am I missing something obvious?
Hi Robert, we are working on some changes that will have parametric cells support bylevel symbology, including materials. The cell will place with all its elements on the same levels as in its definition model and you will be bale to toggle elements on/off via their levels and the whole cell by toggling the level this has been placed on on/off.
You can assign a material to the cell levels in the definition model and then use the "attached material" property together with override symbology (set to no material) to see how other materials could play in a design.
Product Manager, MicroStation
Bentley Systems intl
Answer Verified By: Robert Jones
Hi Marco - I only saw your response after I posted the material hook idea....;-)
To be able to turn off levels to control the display of the sub-components in these cells would be great. and I agree that materials can be preassigned in the cell definition, my only gripe with that is it locks in that material which must be itself predefined and in a known dgnlib / pal.
Hi Robert, I think we should be able to override the pre-assigned material for an instance using "attached material" and level overrides.
What i do is i drop the elements of 1 PC and assign materials to the dropped cell and then the rest follow suite. its not ideal but it works