Hi and thx for the reply!
"You really can't just go willy/nilly and remove parameters from families. << BAD IDEA Many family parameters are set by template and you need those."
That's exactly what I want to avoid! I probably fail at presenting my issue...
We are using a tamplate originally created by our retailer of revit. we also use some of their ad ins, so some of the parameters in the template is there to make their addins or some of the perks with the template work. I DO NOT WANT TO MESS WITH THAT!
The template is working fine and we have some predefined stuff that we really want to keep but there are also stuff that are simply just cluttering the file. Most of them being projectparameters, like a bunch of instance parameters for doors that we will never use and rather clean the out to make the properties dialogue a little easier to work with.
the problem is, I cant really tell if an instance parameter is a project or family parameter just by looking at it in the properties dialogue.I have to be able to backtrack it to find out its origin. is there no smart way of doing this?
lerning more about parameters is exactly what I'm trying to do. I feel pretty comftable in creating what we need in forms of shared parameters and such. It's the reverse I'm afraid of I dont want to remove stuff I might need.
I guess stating from scratch and use transfer project standards is a great way of doing it, but in the same way as I'm afraid of removing stuff now, I'm afraid I would forget stuff with that method.
|
Search
