Joe_Carrick

That's not the way I've always done the framing annotation. Basically this kind of annotation indicates the extent of framing. If you want it to be parallel you can do one of 2 things: 1. Rotate the Text Box and make an arrow "invisible" by whatever means you like. It just has to connect to one framing member and you can have other arrows pointing in the direction of the joists. 2. Use the macro as the "Label" of one of the Framing Members and add your own arrows.

Spacing I can't do - because CA didn't include an Ruby attribute for spacing of the framing member(s). If they did and the arrowheads would stay locked (but of course Auto Framing kills that because it first deletes the framing members that the arrowheads are attached to). IAE, it just needs a little more by CA for this to be a perfect solution.

OK, here's the results I get: 1. No arrows connected 2. One Arrow Connected 3. Two Arrows Connected

Scott, You need to change the framing members to "I-Joist". They are all "Lumber" in your Plan. Here's the result when I changed them. BTW, I could edit the Macro to substitute "TJI" for "I-Joist" if needed but I think "I-Joist" is more generic.

There are 2 options: 1. You can add "Room Macros" to the Room Label (even in Room Defaults) but that will all be on the same line as the Room Name. 2. You can create a RTB with everything formatted (different fonts, underlining, multiple lines, etc which when placed in a room will display all the data. I use this and set the default room label to 0 height so it doesn't show.

BTW, the "Framing Line Label" macro can also be assigned as the Label for any framing member. That's guaranteed to work. It's great for Beams, Fascias, etc.

Scott, If you got the Ceiling Joist Label to work then you should be able to get any Framing Member to work. Post the Plan I know spacing is not auto - said that in post #1. IAE, I'm using this for annotation of virtually all framing. It really does pick up all the variations but you have to make sure that at least one of the arrows is connected to the correct framing member. BTW, I agree that CA should make it work, but since there's a problem with their current functionality this is a real time saver for me.

I've added a Library Object that can be used in lieu of the Joist Direction Line - but only for Labeling Purposes. https://chieftalk.chiefarchitect.com/index.php?/topic/4871-framing-line-label/#entry41943

I've posted a "Framing Line Label" in the "Content" forum that can be used in lieu of the "Joist Direction Line". It provides a more accurate description of the Type of Framing. https://chieftalk.chiefarchitect.com/index.php?/topic/4871-framing-line-label/#entry41943

Attached is a Library CAD Block that can be placed in a Framing Plan, Exploded and have the Arrows connected to Framing Members. It is smarter than a normal Joist Direction Line in that it will recognize the type of Framing (I-Joist, C-Channel, Lumber, etc) and the Member Type (Joist, Rafter, Fascia, etc). It uses a macro to do this which is a part of the Library Object so the macro is automatically added to the Plan. I've set the spacing to 16" o.c. because the attribute for spacing is not available. You can edit that text as needed. Framing Member(s).calibz

Greg, You can use a Stadard Railing, check it to "Follow Stairs" and move it onto the Stairs. OTOH, one of the things we've been asking for is Stair Railings that have the same capabilities as Guardrails. Maybe X8?

Did you select the Image in the Library and assign the 2D Block there? It should then use it for all subsequent placements in Plan.

Sure, Images are objects. They can be forced to always face the camera or not. If you place one just 1/8" from the surface of a wall and make it so that it is facing the right direction (not always face camera) it will work just fine.

Gerry, I agree on this subject. Chief can obviously do a "match selection" as evidenced by "Select Same". All that would be needed would be to pass this list as an array to a Ruby macro to be processed. It would be easy to do with a named Global Variable.

Gerry's point is well taken. Rooms can be uniquely identified by giving them unique names (I use Room Numbers) but no other Chief objects have that capability. With unique names the data can be written to Global Memory so that the next time the macro runs it can be checked against the existing to prevent duplicating the item or counting it more than once. If there was a way in Ruby to return an "ID List" of objects of a given type so that a macro could process each object in sequence then it would work. At present there is no such functionality.

Symbols - Geometric Shapes

I agree with Scott. That tool is not very smart. However, it is possible to use a macro to create labels for the joists & rafters that will give the correct information, including the exact width, depth, length and type of framing member. The macro can be written so that if you are using dimension lumber it will still say 2x12 Joist but with I-Joists it will say 1-1/2" x 11-7/8" I-Joist The macro would need to be specified as the Label for the Joists. Justin has been doing some work with this in order to get even 2' lengths for his rafters. The procedure is basically the same but the macro itself would need to be written differently. IAE, this is a bug that CA should fix. It shouldn't bee too difficult for them to use the same information to make the Joist Direction Line provide the correct information.

No Plan

Text macros can do this using methods: upcase downcase capitalize but if you are using text macros you probably already have it correct and don't need to worry about this.

Are you sure? Post the Plan........

They are worth watching. The biggest problem is finding exactly what is available for what object....... For example: A Layout Box contains an anttribute (amongst others) referenced_full_filename which is the full path and filename of the file that was sent to the Layout. This can be used to construct additional filenames to read and write. Interestingly, the context for using this is "Owner" because you would have to put the macro in the Label of the Layout Box. Chief has not documented all the attributes available and where and how to use them. That's one of the biggest shortcomings. It would be really nice to have a complete list (indexed and searchable) but at this point the Ruby Console is the only source of that information. The other problem - and it's one I believe will be alleviated in the next release or two - is that a lot of object data is still not available to Ruby. One of those is something Justin asked about - Ridge Height.

Kelly, Try the NKBA Auto Interior. They are much better.

Any good lawyer (oxymoron) would pierce that scam in about a NY minute.

Kelly, Why not use Auto Dimensions? If there are some you don't want you can just grab the extension line and move it - that dimension will disappear. But you are correct that the Manual Dimension Tools are picking up more than just the Main Layer. I don't recall that in X6 - but OTOH, I seldom use Manual Dimensions.

Larry, Don't even think about doing any Condo projects if you don't have insurance. I won't do them anyway just because there is always going to be a lawsuit and you'll lose everything you own if you don't have a lot of coverage. The same thing is true for most commercial buildings. The insurance is one reason that Architects have to charge more. We have to carry coverage on our projects well into the future and it's the client who is going to have to pay for it.