Joe_Carrick

In Defaults>Rooms>Room Label> insert the Global>Room Info macro %room.type%. Then when you create a Room and specify the Type the Room Label will automatically display that information.

Another option is an angled front cabinet with matching back rotated 180 degrees.

or just very wide stairs ? Of course, when you place the seating you will have to manually set the height from the floor so they are on top of the treads.

Yes but you need to be able to write a Ruby Macro to do it. The macro then needs to be inserted in the Default Door and Window Labels.

True, except the one on the Terrain Level.

Scott, You can always copy/paste-hold position to show the driveway or any other terrain object on Level 1, Level 2, etc. They will show in Plan but not in individual 3D Floor Cameras except on the Terrain Level. One of the nice things about this is that you can control the line-style, layer, line-weight, etc for the copies.

Absolutely. It's all done in "Edit Page Information" on the "Label" line. The nice thing about this is that any page that doesn't have anything on it will simply not be in the "Layout Page Table" and will not take up a number. You can have as many pages reserved without them messing up the Sheet Index.

Alan, You're missing out on the A-#, S-#, P-#, E-# capabilities in page numbering. Perry alluded to this in post #2

I'm not sure if they were on youtube - but they were posted here on the Forum. I'll see if I can find the thread. Try this thread https://chieftalk.chiefarchitect.com/index.php?/topic/8424-customize-toolbar-for-specific-task/#entry74093

Note, you can also create "Custom Toolbars" and place a set of "Library Objects" on them with the buttons having the appearance you want. There are videos on how to do this - Michael (Alaskan Son) had some pretty good ones.

OTB (Outside the Box) :D

Perry, I have a "Vents" package - currently a $25 package that provides those calculations. It handles Foundation, Attic & Garage Vents, calculating and displaying the required and actual areas. The package consists of a total of 11 macros to accumulate, calculate and display the various items. -Joe

The Macro for August 2016 is Vent Labels It provides a 2 line Label for Vents as follows: I. Line 1 a. The first letter of the "Component Code" (upper case) Attic..........A Foundation ....F Garage.........G b. Any preceeding characters specified in the Label Tab of the Schedule V- as an example c. The Schedule Number Examples: AV-01, AV-02, AV-03 FV-04, FV-05 GV-06, GV-07, GV-08, GV-09 II. Line 2 a. The size (width x height) b. @ <height above floor Example: 16x6 @12" Naturally, as with all my macros, if the plan is metric the appropriate units will be used. This is the last macro of the current subscription. At this time I am having trouble coming up with additional macros that fit within the size/scope of the subscription service so unless subscribers can suggest new macros I will not be continuing the "Macro a Month Club". Instead I will develop and refine more comprehensive macro packages which will be offered individually. I appreciate everyone who has joined during the past year and sincerely hope I've made your life a little easier. vty, Joe

Scott's system of using Level 1 makes sense - but so does using Level 0. Most of the time (almost always) I only show Site Features (Terrain Objects) on my Site Plan and use the Building Footprint for the structures. I don't like to show the actual Walls on the Site Plan but if I need to I can use a Reference Layer Set or even a CAD Detail from View. Note: I'm also using Polyline Areas with X-Hatch Patterns for Site Analysis and I have a Layer Set with those displayed so using that as the "Referenced Layer Set" provides a good way to include the Buildings. So, I'm in the Level 0 camp for the Terrain.

Hi Ross, Currently there's really no easy way to do this. The "Room" macros are hard coded in Chief and User macros don't work for Rooms except if directly placed in the Default Room Label. In addition, the Room itself doesn't know what the wall materials are so calculating the exact dimensions to framing is not possible. CA could provide additional "Room Macros" or they could provide a "Room" context for "User Macros" so that Text Boxes placed in a Room would know that the User Macros were to get the data from the Room. I prefer the second option because it allows a lot more flexibility - but for your purposes the first would work.

Automatic works for most cases but not all. That's why there are manual alternatives.

That sounds like a bug to me. Even if there's just a toe-kick and a separation top and bottom it should be classified as a cabinet. Chief shouldn't require anything else to have it show up in the Cabinet Schedule and have a Label.

Your "so called winders" are just "Landings". You might have to do some manual work to get them to fit, but otherwise it's not that difficult.

Appliances show in the "Appliance Schedule". If the Appliance doesn't take all the Cabinet space (Oven in a Tall Cabinet for example) then you will have a Cabinet in the Cabinet Schedule and an Appliance in the Appliance Schedule. OTOH, if the Appliance fills the entire space then the Cabinet essentially doesn't exist and you will only have the Appliance.

Try getting the winders to work and then select the whole thing and rotate it as a unit.

See item #3 on my post above. Any Foundation above Level 0 has to be done manually. But you don't need to use a P-Solid. The Foundation Tools work fine - just not automatic.

Open the Symbol dbx (little chair on the Edit Toolbar) and select the rotate "x" (n degrees)

An easier solution is to use a Wall Material Region for the Beadboard.

Hi everyone, Sorry I couldn't attend the workshop but I was able to watch the video and have the following comments: 1. I currently use Level 1 for the lowest floor that has usable space 2. I use Level 0 for the foundation (slab or crawlspace) below Level 1 3. I sometimes draw additional manual Foundations below Level 2 a. This is because I am often working on a site where Level 1 is a partial Basement b. There are also times when a given "Level" encompasses a "Split Level Floor" 4. I don't consider "Level" to be the same as "Floor Name" 5. More flexibility in showing upper and lower walls (Pony Walls) would be a nice feature. 6. More flexibility in showing "Reference Layer Sets" would also be a nice feature. 7. The ability to rename "Levels" would probably eliminate a lot of confusion. Sometimes it's easier to create 3-4 blank Floors and start with the main floor on Level 3. You can then develop the floors below so walls align as needed. If you only need 1 floor below the main floor you can easily delete floor 1 and everything above will move down appropriately.

FWIW, Regulations don't cause good design. They can prevent unsafe construction and for the most part result in better buildings. That doesn't by any stretch of the imagination mean all regulations are good. Some regulations simply add to the cost without really providing any benefit. Even in covenant communities where there are design restrictions and review boards - sometimes the design is faulty even if the appearance is compatible with the community standards.