Joe_Carrick

Members
  • Posts

    11782
  • Joined

  • Last visited

Everything posted by Joe_Carrick

  1. Sure, it's just a matter of having the macro that collects the data in the roof plane's label - or not.
  2. Thanks Doug - now we just need to get the powers that be to agree and fund it
  3. In most cases only the Projected and Surface Areas are useful or needed. Some jurisdictions require these for rain water runoff analysis. The Projected Area is considered impermeable and that will effect storm water systems. The Surface Area is useful for material takeoffs - Roof Sheathing, Shingles, etc. I'm not going to provide the Contractor a materials list - but with this information on the Plan it makes it easier for them to do their own take-off.
  4. Thanks Glenn, The definitions you posted are directly from the Help File for the Roof Specification (Polyline Panel). My schedule used the "Projected Overhang Area". All of the values were retrieved and tabulated from the corresponding Roof Plane attributes. If I change any Roof Plane in the Plan - the Schedule is automatically updated. I added the appropriate footnotes to the Schedule.
  5. Curt, Which Column Values are you not understanding?
  6. It takes just 2 macros to create this Roof Schedule - and the Labels for the Roof Planes.
  7. Here are a couple of pics that show just a fraction of the Object Data for a Wall in Chief. Then there is the pic that shows just how little of that information is available as attributes that could be used within a script. That's not just annoying - it's pathetic. Come on CA - open the doors!
  8. You should post this in the Q&A or Suggestions Forum. Then delete it from this Forum because it isn't a Tip, it's a Question.
  9. I can see a way that both could be used. I already have several different Layer Sets that I use for my Layout(s) depending on Sheet Size and for "working" vs "printing". So by adding another set for "reduced prints" I could use the %scale% macro
  10. Doug, Is there any way the name of the macro could be changed to "printed scale" without effecting the prior use? Maybe just a duplicate macro with that name would be useful. At least that way the name would give an indication of what it actually does. I personally do not find the "zooming" aspects useful since I use different monitor sizes and the "zoomed" scale is not always indicative of what it will look like when printed.
  11. Maybe the Text Style assigned to the Layout Box Label ????
  12. My take on this is that "Zoom Scale" is really irrelevant. When working in the Plan - scale means nothing on the screen. When a dwg is sent to Layout is is according to the sheet that it's to be printed on and the scale of the Layout box on that sheet. Check Plots at smaller sizes should be so noted in and check plots are not intended to be to scale. Yes Tommy, I did read that post - in fact I had several postings in that thread myself.
  13. Tommy, I disagree with Doug on this issue. He has his opinion and I have mine. The scale is whatever scale the Layout Box Scale is. If I rescale the Layout Box, the displayed scale is automatically updated.
  14. In Defaults Settings>Rooms>Room Label you can add any of the Global Room Info macros that Chief provides. Internal Room Area and Room Dimensions are consistent. ie: both refer to the inside face of the walls. BTW, if you want to be able to format the Displayed information you can use a RTB instead of the Room Label that Chief provides. The same macros will work in a RTB.
  15. That is exactly what I do - but I have a set of "Detail Plans" with my Details already in "CAD Details" - so I skip the Library. Many of my Details have already been sent to Layout from these "Detail Plans" so when I open the Layout I can go directly to the correct CAD Detail in the Detail Plan it came from.
  16. Basically, when you create a detail in the Plan and add it to the Library it is in "Real World Units". If you then just add it from the Library to the Layout it comes in at the Layout scale (1"=1") so a 2x4 created in your Detail will be much larger than you intended on your Layout Page.
  17. Joey, You can move the Layout Box Label to wherever you want it.
  18. OK, In your Plan with the Floor Plan Layerset displayed: Create a Text Box and Enter the Text you want for the Floor Plan Label - put that on a Custom Layer - Send to Layout With the Roof Plan Layerset displayed Create a Text Box and Enter the Text you want for the Roof Plan Label - put that on a Custom Layer - Send to Layout For the scale in the Layout Boxes - only include the %box_scale% macro. The key is to not use %automatic_label% for the Layout Box Label. Or, you could just replace %automatic_label% with "ROOF PLAN" and "FIRST FLOOR PLAN" in the Layout Box Labels.
  19. Joey, You can put the Label in the Plan (per Layerset) and just use the Layout Box Label for the Scale
  20. Thanks Larry, Since it's all part of my Default Plan - I really don't have to do much other than assign Room Numbers as a Part of the Room Label and copy the "Site Label" for the various "Site Objects". I don't do much remodel work so I will not normally need the "demo", "remodel" & "new" areas. However, I do have the macros available to display those items when needed. Note that the "Room Data Display" is done with just a single macro. That macro retrieves all of the areas - room by room - and formats it into the table. Ruby is capable of doing a lot once you know how to use it. However, CA needs to open up access to a lot more attributes along with Labels for Polyline based objects. If CA would provide the ability to modify attributes from within Ruby there would be a lot more that could be done - like automatic Room Numbers, etc.
  21. If you select the end wall and click on the "Gable" wall icon on the Edit Toolbar it should eliminate the attic wall.
  22. I've posted a video of how I'm doing Site & Building Area Analysis using Ruby in the Chat Forum https://chieftalk.chiefarchitect.com/index.php?/topic/5232-site-and-building-area-analysis-video/