I had originally decided to move my firm back to more OOTB families and just customize what we need. This is partially because we have not made all the detail components like the AISC shapes as the OOTB has and few knew about these shapes and also because programs like Fastrak (structural analysis) does not recognize our custom family names and locations. I figured it would be easier to just use the OOTB than try and repath the linking file to our families every time.
So here are some of my pros and cons to each OOTB and Custom.
My thought until recently was to mix the libraries using shortcuts to the users library, but a colleague of mine stated that my old firm is pretty much all custom now. How does one address changes like the addition of Moment of Inertia as a unit type now in custom families? Where the OOTB would generally have this addressed from the factory?
I still partially like the mixed idea, but even the AISC DC have some modifications I would like made to them. Perhaps most model is OOTB and DC and annotation is custom?
So here are some of my pros and cons to each OOTB and Custom.
- When things are changed from version to version, the OOTB keeps these changes rather than me having to update
- Using the OOTB makes upgrades very easy and family maintenance easy
My thought until recently was to mix the libraries using shortcuts to the users library, but a colleague of mine stated that my old firm is pretty much all custom now. How does one address changes like the addition of Moment of Inertia as a unit type now in custom families? Where the OOTB would generally have this addressed from the factory?
I still partially like the mixed idea, but even the AISC DC have some modifications I would like made to them. Perhaps most model is OOTB and DC and annotation is custom?
Comment