@barthbradley wrote:
@twallVCXPH wrote:
I know there are plenty of third party things to load in but why should I have to do that when commonly used things should already be in the program.
Revit Families -- RFAs --are NOT Third-Party Content. Nor are RFAs built by another person Third-Party Content. They're just RFAs that you don't have to build yourself. Hooray!!!
Since this post of mine came back to me with red-lines, let me make corrections and resubmit.
Revit Families -- RFAs --are NOT Third-Party "things", as you characterized them. Nor are RFAs built by another person Third-Party "things". They're just RFAs that you don't have to build yourself. Hooray!!!
@twallVCXPH: If your frustration with Revit is that the stock Content Library and Project Templates are not all-inclusive of every single "thing" that you need for your job, then add “things” to it as you go along – like we all do. You can add “things” to your warehouse of “things” stored offsite (e.g. Content Library) and/or, you can add “things” to the toolbox (e.g. Project Template) that you bring to every job. You can even have job-specific toolboxes.
Help | Project Templates | Autodesk
P.S. the RFAs in Revit’s stock Content Library and Project Templates are “third-party content” if we go by the definition posted above. My initial read was that you meant third-party as a “thing” that was not the “real thing”. Kind of like the difference between Coke and Pepsi. I stand corrected, if need be.