Oh, … no doubt.
Currently the configuration is saved within a special attribute dictionary attached to the component definition (instead of the instance.)
This means (currently) we must do a Make unique command on any instance(s) that we wish to configure differently than the “norm”.
An example might be interior doors. Most of them in a dwelling model would be the same width.
But then you’d have closet doors not as wide. Also depending upon location (proximity to walls, etc.,) some doors will be hinged on the left others on the right.
So (again, currently) after bringing a LC into our model, we may need to do a Make unique command several times to create unique definitions for the different scenarios of instances that are needed.
This means that modelers will need to set the main “common” options on the first instance’s definition (material, finish, etc.) and then do the uniquifying as needed.
But we hope that this changes in the future. Modelers would rather have a “common” definition in which common options could be changed modelwide for “related” instances. (Again using door paint and hardware finishes as an example.)
Imagine an entire condominium building model with many many door instances. Then the customer decides they want all the door finishes to change from walnut with black hardware, to oak with stainless hardware. It could be a tedious task to change them.
And then there is the scenario where you want to have different styling for walkthrough animations. Having to have multiple sets of doors assigned to tags(layers) bloats the model size.
LCs by design will not work this way. The “Live” in LC means that the component changes as you make edits to configuration options. There is no OK or Apply button as there is with DCs.