Alaskan_Son

A Plan Footprint is a special object type on Chief. If you're not familiar with it, search the Help files for Plan Footprint.

The Plan Footprint is controlled by the Layer Set being used in your CAD Detail, not the layer set used back in your Plan View.

We have handles for Leaders and for Callout Arrows but not for Section Arrows. A suggestion for the Callout Arrow to be used along with the Alt Key to pull a Section Arrow might be a good one.

I don't typically donate time to troubleshoot or advise on scripting issues on here anymore, but I decided to make a one time exception this morning: There are all sorts of little problems: source_information = %room.area.internal% numeric_part = source_information.match(/\d+/)[0] numeric_value = numeric_part.to_i result = numeric_value / 20 puts result 1. %room.area.internal% isn't a Ruby accessible object attribute (name:value pair). It's just a Chief Architect string substitution macro. If you want to use this macro in a text box placed in the room, the name:value pair you should be using is simply room.internal_area without the percentage signs. 2. The match method is a Ruby method used to parse a string. The internal area attribute however is not a string. Its a Measurement. If you want to use the match method, you first need to convert the source_information to a string using the .to_s method. 3. Just an observation, but you may not be getting the results you think. The .to_i method is converting your results to an integer which is the whole number rounded down. 0.999 would become zero, 559.9 becomes 559, etc. What's worse though is that because you're diving by another integer (20) the results of your calculation would also become another integer. So, instead of 559.9/20 = 27.995 you would get an even 27. This one can be solved by just converting to a float (which contains decimal values) and then rounding the result. This can be done a number of ways, but one of the easiest would simply be to replace .to_i with .to_f. 4. puts isn't used in Chief's text macro environment. It's simply not needed. If you try to use it, your results will by nil (empty). So, the corrected macro becomes: source_information = room.internal_area numeric_part = source_information.to_s.match(/\d+/)[0] numeric_value = numeric_part.to_f result = numeric_value / 20 result.round Although the above macro would work, it still has a handful of totally unnecessary code and could be reduced all the way down to: (room.internal_area.to_f/20).round

Are you sure you used the Hole in Ceiling Platform tool and not the Roof Hole or Hole in Roof / Custom Ceiling tool?

Have you looked at the Hole in Ceiling Platform tool to see if that does what you want?

To get additional items into the Material List, you need to use the Components tab.

What happened to... ??

Open the Garage and Porch Rooms up on Floor 1, click on the Structure tab, and under Floor, uncheck Build Foundation Below.

I think the answer to this depends a bit on HOW you are drawing up your site plan and on what needs to be shown on that plan. If its all CAD, then I would suggest you look into using the Plan Footprint tool in a CAD Detail. The Plan Footprint is essentially a layout-box-like viewport sent to a CAD Detail so that the house can be freely moved around on your site plan. If however you need to include a lot of 3D information, then that changes things a bit. I usually draw all that stuff in the current plan file and then if the house needs to move, just group select or Edit Area and move the underlying site plan stuff in relation to the house instead of the other way around.

Study the Materials List Polyline and its settings. Its a super powerful feature and is the best way to utilize the Materials List in my opinion. It can be used in concert with the various tools you already know about (Layer Sets, Layers, Material Definitions, Components, etc.) and you can even group select them to produce a single combined materials list using different polylines with different settings.

Non macro solution for quick totals: Much like we already do with schedules, you can optionally consolidate items by using only columns that will cause items to group together (like Group Similar Objects does). In your case for example, you could turn off the size and description columns to get a total count to display instead of individual counts. There are various ways you can use other columns to help consolidate items this way for quick calcs. You could also optionally copy and paste any given selection to excel.

I don't know, but not sure why they would. Anyone needing to work with the object in Chief could just as easily and much more effectively use a more appropriate file type like obj, dae, or 3ds. I don't believe there's any extra information in an fbx file that Chief could make use of and I imagine any software you're using to produce the fbx file could also be producing one of the aforementioned and less bloated file types.

We currently can't. I would either suppress the text and add manually using a text box OR (if the dimensions needed to be dynamic) use a single segment polyline with arrows and macros in the label.