Hi, thanks for a good video. I was thinking, isn't it better to generic annotation families for the arrows, circles etc? Then you can skip the scale parameter. When using commas in parameter names I think you need to enclose them with curly brackets or brackets (can't remember). One more thing, maybe one can add a ref.line so that the family becomes symmetrical about the x-axis. I've used that in other families. I'll learned a lot from your compound I-beam video😊
I made this video a while back so don’t remember what you are referring to. But thanks for your input. Also, thanks for the support, I’m glad you liked the I-beam video
It won’t act as a tag. So yes, you will have to add numbers and spacing manually. I built this model because Revit’s built in rebar modelling doesn’t provide rebar tags like these so it is more of a workaround. On a side note, I do not know if Autodesk have changed this in later versions of Revit.
Hi, thanks for a good video. I was thinking, isn't it better to generic annotation families for the arrows, circles etc? Then you can skip the scale parameter. When using commas in parameter names I think you need to enclose them with curly brackets or brackets (can't remember). One more thing, maybe one can add a ref.line so that the family becomes symmetrical about the x-axis. I've used that in other families. I'll learned a lot from your compound I-beam video😊
I made this video a while back so don’t remember what you are referring to. But thanks for your input. Also, thanks for the support, I’m glad you liked the I-beam video
will this behave like a tag or you need to type in rebar size, number and spacing manually?
It won’t act as a tag. So yes, you will have to add numbers and spacing manually. I built this model because Revit’s built in rebar modelling doesn’t provide rebar tags like these so it is more of a workaround. On a side note, I do not know if Autodesk have changed this in later versions of Revit.