Joe_Carrick

English, It's bad form to give yourself the "Best Answer". You should give the credit to the person who gave you the answer, not yourself.

Door & Window Labels will not display in the Plan if the Schedule Callouts are being used.

Scale factor should be 12. Your Contractor seems to be working in feet rather than inches.

Interesting answers. I do use angled corners - but usually for Recycle Bins. It wastes a little space in the cabinet but not much more than a Lazy Susan would. Sometimes I put a Trash Compactor in an angled Front. Of course in that case it really isn't a cabinet but there is a Counter Top. I never use the "L" Corner Cabinet with bi-fold doors. Every one I've ever seen had a problem with the doors getting out of adjustment. A 36" Lazy Susan with full inset doors would be OK but I don't do much full inset cabinetry.

I've been working on a Countertop Area listing macro. It's fairly easy to get the areas except for corner conditions or cabinets that are not just rectangles. So my question is: How do you handle the corner condition? 1. Blind Corner Cabinet? 2. Lazy Susan or Angled Front Cabinet (Actual Corner Cabinet)? 3. Blank Space? Using #1 the WxD calculates the area correcly. Using #2 the WxD calculates extra area Using #3 ignores the corner. Custom Countertops have an area attribute but it's not consistently accurate unless created separately from the Cabinets.

Sherry, Here's one I downloaded from 3D Warehouse Central Vacuum Canister.calibz

Ahhhhh....

Bonus Catalogs, Kitchen Accessories, Canisters Strange Location but that's where I found them.

Johnny, You can have the macro %view.name% as the title in your CAD Detail and whatever you've named the CAD Detail in the Project Browser will be reflected in the Layout. But to answer your question - No, at least not that I've been able to determine. The updated Callouts for Sections and Elevations are the "Camera Callouts" which are basically different than Callouts placed in a View. ie: Elevation and Section Views, CAD Details, etc.

Check your Firewall and AV Settings and make sure you except Chief and Chief Files. If the AV is scanning your Plans it can slow things down quite a bit.

You can also try saving and rebooting your system.

Post the Plan

Is it being copied to a layer that's not displayed? Check your Text Defaults for the Layer that Text is to be created on. I see this when I have the default Text Layer off and I'm copying text from Notepad or some other source.

It could be a Wall Type definition problem. Strange to say the least.

Yep, a 2D CAD App in 1984 would do it that way.

1. 3D Faces (Primitive Solid) can be extruded. 2. Molding Polylines use a Profile and extrude that 3. Solids can be "Exploded", resulting in 3D Faces (see note #1)

Glenn, That's a good method for 2,4,8,16 segments - but it won't work for 3,5,6,7,9-15, etc. Ken's method works for all cases.

Baaaaaddd !!!!

Another thing to check: Click on the Layout Box and then Open the Ruby Console and type "referenced_full_filename" <enter> Does that show the name of the file with the revisions or a prior version?

That should be automatic unless you've converted those to CAD Details and sent the CAD Details to Layout. If you just send the Plan Views directly to Layout they should automatically update as you make modifications.

Larry, If you use Text Styles religiously, you can just go to defaults and check that box for each of your Text Styles. It only takes a few minutes. I think unfortunately that many users have a hodgepodge of text definitions in their plans and layouts. There are so many different places in Chief where the text parameters can be defined that it makes for a mess. I've been spending some time over the last month cleaning up my Templates (Defaults, Layer Sets, Text Styles, Annosets, etc.) Personally, I have some Text Styles that are not all Caps and some that are. I use Arial and Chief Architect Blueprint for just about everything and I have those for 3 scales (1/8", 1/4", 1/2") and 3 sizes (1/8", 3/16" & 1/4").

Jared, This could be done with the following: internal_area * (finish_ceiling_elevation - finish_floor_elevation) I don't think it would be much work to add it to the Room Area Macro Package. Essentially $RoomAreas already has that data stored for each room so it would be a simple matter to create a Total_Room_Volume macro that just goes thru that array and sums them up.

OMG, P found a spelling error by DSH

Johnny, I can make it work in Ft-In - but only using the Label, not a Text Box. It requires custom macros to convert the numerical values to formatted text strings.

Johnny, You are using Chief's built-in Global, Object Specific macros. Those are fixed format in inches. Unfortunately user macros can't be used in Text Box Room Labels so you can't format those to Feet and Inches.