Joe_Carrick

It is not a good idea to Copy/Paste Schedules - unless you delete the original. Otherwise you can get double labels in the Plan.

Here are a couple of concepts for "Plan Notes": A. Use a "Plant Schedule" as discussed in some other threads. 1. Pros a. It's pretty easy to implement b. I can be done on a (per floor) or (all floor) basis c. Notes can be edited easily creating new notes 2. Cons: a. You can't have a separate Plant Schedule b. You can't have multi-line or word-wrapped notes. B. CA provides a "Note Schedule" 1. Pros a. It's pretty easy to implement b. I can be done on a (per floor) or (all floor) basis c. Notes can be edited easily creating new notes 2. Cons: a. CA needs to implement multi-line and/or word-wrap capability b. Requires a new Object Type (Note) in Chief C. Use external text files 1. Pros a. Simple to use Text Editors b. multi-line and/or word-wrapped notes are easy 2. Cons a. Must use some method of transferring the text to the Plan b. Coordination with the Plan is manual. D. Special Text Object with 2 parts: Number-Displayed and Note-Undisplayed 1. Pros a. Contained totally in Chief b. Easy to Coordinate with Plan c. Multi-Line and or Word-Wrap can be done using a macro to format the Notes. 2. Cons a. Requires a new Object Type in Chief b. The 2 parts of the Object would need to have attributes available. c. Text macro would be needed to format and display the notes. IMO, Concept "B" would be the best solution. Unless and until CA provides that, Concept "A" is still the best.

Do you have "Line Weights" turned ON? There is a Toggle Icon on the "Modes Toolbar". There's also an item in the "View Menu"

We need "Word Wrap" in all Schedules.

That won't work. You can have a "Notes Schedule" for each floor individually or one for all floors. The Plants would have to be on a Floor that you didn't have a "Notes Schedule". The other alternative would be to use some other Schedule which you didn't otherwise need ("Furniture" perhaps) for the "Plan Notes" but this doesn't work quite as well. The ideal would be for CA to give us a "Plan Notes" specific schedule. Maybe I can create a macro to use instead of a "Schedule" but other than using external file(s) to store the notes I don't see how.

Wrong, the Schedules will still update automatically. It just make is easier to arrange and send to Layout. This makes it possible to send the Schedules (or anything else) to Layout separately from the Floor Plan. CAD Detail Windows are just like Elevations, Sections, etc in that respect. It also makes it easier to organize the data in the Plan File by names which appear in the Project Browser.

Alan, Use a separate Schedule for each floor (put in a CAD Detail Window as Scott suggested) Now you just need to rearrange the rows in each Schedule.

Oh, I misunderstood...... I guess you want the automatic cross referencing in Elevations and Plan Callouts but not in Schedules. IMO it would be appropriate in both.

So you like the automatic referencing in Archicad and are willing to pay for Archicad in addition to Chief so you can get that feature. Why would you not want that feature in Chief?

Richard, I might agree with the masochistic architect part. But let me put this another way. Reference bubbles on the Elevations are just another set of references in addition to the Door Callout.. You would still need to enter the correct data in those bubbles. OTOH, If I select a Door or Window and open the Component dbx a. Select the Sub Category Description field. b. assuming the there was a way to pick a CAD Detail (maybe in the Project Browser) and have the View Name and Layout Page automatically filled in. c. That data was automatically reflected in the Schedule Column Then there would be no discrepancies in the reference and a lot cleaner elevations. ps: I don't do just small residences. Some of my work is commercial but even with custom homes I can have several different conditions for Door and Window Details.

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.

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.

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.

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.....

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.

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?

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.

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.

Member Name is Tommy1. You can select him from the Member List and send him a message.

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.

Andy, I can't get that to work. I can't select the Room.

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.

Please explain. The Attic Floor doesn't provide "Rooms" so there are no Labels.

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.