Joe_Carrick

What are you using to export? Why not print to PDF?

This ensures accuracy in the layout. Layouts may feature views at varying scales and can be printed on sheets of different sizes.

I would need to tell what's wrong.

Without the plan there's no way to tell.

What Format? Ft, Ft-In, in, etc.

So at the beginning of the macros add this: referenced ? obj=referenced : obj=owner then add obj. in front of each of the lines that are displaying the data That will make the macros work for whichever way they are being used. You might want to look at my template in https://chieftalk.chiefarchitect.com/topic/39977-macro-coding-template/

custom_fields["field name"] is the way to get the data. Of course you'll need to specify the object in your macro. Owner would be typical if you want the outpt in the object's label.

I can't find the NKBA Dimensions in X16. Does anyone know if it's still available and how to get it?

For purposes of the plan, yes. In reality the electrician may not use GFCI outlets if the circuit itself is protected. However, he or she will place labels on non GFCI outlets where they are protected.

Find an archive version prior to your save that you can open. Then save it with a new name or save it as the original.

They work the same way. Either HDMI or Display Port but must be to GPU.

I use a 55" 4K TV

I concur. Most dropdowns should be alphabetically sorted. I'm not sure how this ond got scrambled.

I just use the "Stackable Washer" and change the name, etc. It's pretty close.

To elaborate on Ben's statement: ".rb" files can be stored there and "required". I think the Ruby "Tutorial" is one such file.

If you use "Saved Plan Views" and name them in the Project Browser, then you can use the Atomatic Label as the label of the Callout Boxes in Layout. Note that Chief uses "Floor Level" simply as an identifier. It's not intended to be the name of the floor.

I don't use it. It could be useful if you wanted to write a macro (on the fly) and save it into the scripts folder - or something similar in the data folder. But really it's just used by Chief internally to know where to get things.

FWIW, I always try to put pet doors in a wall rather than a door. If the house is later sold and the purchaser doesn't have a pet then the door doesn't have to be replaced. It's much less expensive to just close up the opening in the wall.

I have a macro that can display the height of a wall. However, it only displays the height of the wall correctly if there are no openings in the wall. I could probably set up some global hashes to store the opening areas for each wall and add that to the wall's reported area. This would make the calculation pretty accurate. But it would be far easier for CA to simply include an NVP for the wall "height".

Chief doesn't provide wall attributes (NVPs) for top_elevation or bottom_elevation. The best you can do is use the room finish schedule for this information. IAE, you should check my macro template in TIps & Techniques for the proper way to create macros in Chief. The format you are using doesn't work in chief.

I'm using a custom macro that displays the inch value as a superscript. I actually include several macros to include additional information such as: type egress tempered etc.

I'm pretty sure you can do this just using a standard wall cabinet and adjusting the face items.

No. I just enter the label and use that. ie: 42" Tall Glass Railing

I suspect that your floor height is set to zero or slightly more.

It's in the Layout. The same toolbar icons in Layout are pages while in the Plan they are Floor Levels.