Joe_Carrick

Members
  • Posts

    11881
  • Joined

  • Last visited

Everything posted by Joe_Carrick

  1. The question is "What are you doing?" We have no way of telling you what you're doing wrong when we don't know exactly what your are doing. This is a case of "Post the Plan" or a video. Then we have a chance of helping.
  2. Richard, The cross-referencing should not be an issue. It should simply be a matter of a "link" to a CAD Detail and the Sheet Number in the Layout where that CAD Detail is located. Chief has all the information it needs for accurate cross-referencing. BTW, if CA were to provide the attribute for the Layout Sheet and allow macros in Schedules I could in fact do accurate cross referencing.
  3. I've always used Detail Callouts/References in my Door & Window Schedules for Head, Jamb & Sill. To do this with Chief is a PITB since I need custom columns and then have to enter the reference data in the "Components" dbx. In addition, I have to manually check the Layout to make sure I reference the correct detail. There must be an easier way.
  4. I've not been able to find 3D Symbols from either of those. I created the entire Andersen Bay Window set from scratch. It's a little complex but.....
  5. The reason I asked is that for the Manfactured Units I prefer to use a "Window Symbol" rather than Chiefs' Window Tool. I can create the Symbol to the exact size and specification. As far as Sections and Details are concerned I totally use Chiefs' Tools to create and detail those. It's pretty remarkable how fast and accurate they can be. Now if only we could get automatic annotation to go along with that it would be really great.
  6. Christopher, Do your projects generally use "Site-Built" Bay and/or Bow Windows? Or, as is commonly the case are those manufactured units like Andersen or Pella make?
  7. There is no problem using X6 and X7 at the same time. You have a license for both. Also, you don't need a Hasp.
  8. Tommy, My reason is that I want to do a calculation (using Ruby of course) to get the area of Attic Vents compared to the area of the Attic. I've been working on some automatic tabular reports using Ruby that display such data. Window Area vs Floor Area Foundation Vent Area vs Crawl Space Area Garage Vent Area vs Garage Area The above are no problem since it's possible to get all the values and store them in Ruby Global variables. The problem comes with Attics because there's no easy way to get the Attic Area. All of these things are required by code to meet certain minimum standards. Having Chief automatically calculate and display the date makes it much easier to meet those standards. It also eliminates the need for met to manually calculate and enter the results as text, not to mention the fact that any changes to the Plan result in the data being automatically updated.
  9. Member Name is Tommy1. You can select him from the Member List and send him a message.
  10. Elaine, I am not sure what HD Pro's capabilities are, but a Perspective View would never be "to scale". You can only print Plans, Elevations, Sections and Details "to scale". If you want the "Materials" as in your pic, just change an Elevation View to "Standard Render" and send to Layout at the Scale you want. btw, a model built at 1" = 1' is going to be pretty big.
  11. Andy, I can't get that to work. I can't select the Room.
  12. Why can we have an "Attic" room on a normal Floor but not on the Attic Floor? -and- Why are there not a "Crawl Space" and "Slab on Grade" rooms for the Foundation Level? If the Foundation is a Floor like any other then the Rooms should default to these types, not some arbitrary room from the 1st Floor.
  13. Please explain. The Attic Floor doesn't provide "Rooms" so there are no Labels.
  14. Without creating an extra floor or using a closed Polyline, does anyone know how to get the "Attic Area" ? There is an "Attic Floor" but there doesn't seem to be any way to select the "Room" to determine what the area is.
  15. Been doing it that way for years
  16. A picture may be worth a thousand words - but the proper set of words can be more precise. Proper annotation is critical for construction documents.
  17. Scott, Jared is correct. I wasn't aware that the Floor/Ceiling Truss didn't allow Specify Label. However, if you use the "I-Joist" for Floor Joists you can label them as you want in the Plan View. They won't look right in the Section (no webs) but you can "fake" that as needed.
  18. Usually just a shut-down and restart will fix this. Sometimes a file can get left open and that will cause the problem.
  19. I was talking to Jared yesterday and he asked if a macro in his Plan could set the framing spacing text so that his Detail Plan would match. That way he could have his Details labeled to match his Framing Plans. So I put together a set of macros for 12", 16" & 24" spacing of Ceiling Joists, Floor Joists and Rafters. So it's only necessary to have the macros that set the spacing located one place in the Plan. I would use the Structural Notes to embed those macros. Then the display macros could be located in text boxes - or even in conjunction with the Framing Members(s) macro - anyplace they are needed: Framing Plans, Details, etc. and for16" spacing will display the text as: @ 16" o.c. Since there is a different set of macros for CJ, FJ & R it allows flexibility to use different spacing for the 3 member types. I have attached the macros - I think the names are pretty much self explanatory but if you have any questions let me know. Framing Spacing.zip
  20. Now if I could just exchange them for "Bit-Coins"
  21. So where are my extra "green reputation points" ?
  22. Attached is a macro that can be used to show all the attribute names and values for any object in Chief. This is pretty handy since it shows just what has been made available by CA as Ruby attributes that may be used in other macros. I'm not sure where I got this macro - I think it was Gerry but IAE I modified it to suit my taste. It can be used in a Referenced Macro. It can also be used by selecting an object and then hi-lighting the macro in "Text Macro Management". Since Labels do not have word wrap capabilities it doesn't work in a Label very well. _Object Properties.zip
  23. It would be nice but for now it's just a real simple detail or even a note.