Joe_Carrick

Kate, I don't know of any file type that can be imported into Chief to do that. Perhaps a 3D file like SKP or OBJ but from AutoCAD you can't get that. You are unfortunately going to need to build the model in order to do a rendering. Tracing over the DWG using walls, doors, windows, etc will get you close.

Rene, Inevitably an Evaluation Error is caused by some variable (NVP) not being initialized. I find this most often with macros in a Schedule column. In which case I have to open & then close the Schedule. It really depends on the macro and what "error handling" is being done in that macro. In my case I have 2 schedules and one of them isn't initializing an array that the other needs data from. I would need to see your macro that's producing the error to be able to identify what might be causing it. I agree with you it's most likely a bug in how Chief updates macro execution. They specifically tend to minimize so performance isn't degraded. Repeated macro execution can slow Chief down.

Preferences > Appearance > Toolbars - Button Size.

Just don't include it in the Wall Schedule. You can label it separately.

Notes are not the same as Callouts so: I want separate tools. A combination tool could be useful as well. I want separate defaults for Callouts in Plan vs Layout. Layout Box Labels have a Callout Option. This is the primary use for Callouts in Layout. Callouts (Stand Alone and Camera) in Plan are used to reference the Views sent to Layout. Notes are typically used to minimize the text on a Plan View. They provide a reference to the Note Schedule(s). That said, I prefer actual text in my CAD Details to minimize contractors & subs from having to search for the information. I've seen too many ConDocs with Notes incorrectly cross referenced.

That's because CA keeps making changes to their Catalogs. You can of course skip the updates and just do them at a more convenient time.

Eric is correct that it works in a text box - but you have to put it there as a macro evaluation. ie %...........%. You can even use a RTB and get all sorts of formatting. The advantage however of using a custom macro is that it can get data from the owner or referenced object and use that to return results.

The wall in the 6th row is controlling all the row heights. Why is that wall so thick?

I just tried the following in the Ruby Console: y = 450.00 ; x = Math.sqrt(y).round(4) ---> 21.2132 It works fine. However, the data in the parentheses has to be numerical. Otherwise you'll get an error. Also note that Ruby is case sensitive. So as Eric said, Math works, math doesn't.

You would need a custom macro. It's not a difficult one to create.

This is why I don't like the Schedule method. The Detail Callouts should be based on their position on the Layout Page automatically. Then any Plan Callouts linked to the view sent to Layout will automatically be correct. Detail Callouts should be based on their position on the Layout Page & Plan Callouts should always be correct.

Convert them to Symbols. I would use "Exterior Fixture". Then you can use a Schedule.

I use a custom sheet size for my Interior Elevations. Typically 4" tall x 7-1/2" wide with a corresponding CAD Box (invisible linestyle) When I send the view to layout it's automatically that size and will snap to other layout boxes. The Layout Box can be resized if needed but I only need to do that for the width in most cases. I also have a default set for my layout boxes so they are labeled to match the project browser name.

Actually using the "Match Properties" tool works. OTOH, the "Object Painter" tool really should match the "Arrow Style". Submit a request.

Unless you have birds that perched on the clothes line and left their calling card.

Use a "Working Layer Set" with the "layout lines" displayed and a "Print Layer Set" with them not displayed.

That's more understandable with the above picture.

Assuming the doors swing outward. Otherwise it will be a problem because the one on the right will not open no matter what the shape.

Can you reference the Code Sections for this? The CRC (California version of the IRC) only specifies a slope for drainage. I can't find anything about a height difference. The 4" height difference was a requirement at one time in the old "Uniform Building Code" but I'm not sure if it was even required in the last UBC. I don't think it's ever been required in the IRC or any version thereof. Fire protection is another issue entirely covered by Doors and Walls.

When will the X15.3 update be available? I sure hope it will be this month. --- and of course that it includes all the NVPs I've asked for.

Just use "Text" or "Rich Test" and drag the diamond icon to create the line with arrow.

Search for Roll Up I posted one in a thread that comes up.

Have you "Updated" the view?

Make sure the "Show Open in 3D" is off.

It could be done with a custom macro in a text box with an arrow connected to the cabinet. For a more comprehensive automatic method a custom macro would have to be created that would rely on the name of the layerset so that the label would only display that in an elevation view. OTOH, the "Comments" field can be shown as a column in a Cabinet Schedule. That's probably the best way to deal with it.