Joe_Carrick

You can uncheck "Reflections" in the Camera Defaults or in the individual Camera dbx. The other option would be to make one of those Mirrors a non- reflective material.

Hi Mark, I looked at the catalogs and IMO these Manufacturers have gone way out in left field. It seems they have a CODE for every possible condition rather than a simple system for the box and door/drawer configuration. Since I'm concentrating on Conestoga (Youngdale is a Dealer) the Codes are much simpler. Almost every CODE can be represented based on the existing Cabinet attributes. Basically there are just 3 primary Box Types: B = Base W = Wall U = Utility Then there are some qualifiers such as: S = Sink C = Corner O = Oven (replaces the "U") FD = Full Door FC = Filler 1D = 1 Drawer, 2D = 2 Drawer, 3D = 3 Drawer, 4D = 4 Drawer LS = Lazy Susan Followed by size (usually w x h but sometimes w x d x h) Followed by "BD" for Butt Doors If the cabinet doesn't fit a standard size or configuration the CODE is prefixed with a "C" for Custom If it's a Vanity Cabinet the CODE is prefixed with a "V" Some other Cabinets such as Desk, Open Shelves, etc may be prefixed with other characters but generally it's possible to just use one of the 3 basic types. IAE, the most complex CODE would be something like: CBCFD32134.5BD [ Custom, Base, Corner, Full Doors, 32" wide, 21" deep, 34.5" high, Butt Doors ] while a stock Base Cabinet would be: B2434.5 [ Base, 24" wide, 34.5" high ] Single Door and 1 Drawer Door Styles, Pull-outs, Finishes, etc are not a part of the CODE. There are still a few configurations for which it's easier to just enter in the CODE field manually rather than trying to program into a macro, but those are special cases. In addition I can specify a Custom Front and Box with whatever Doors, Drawers, Openings needed. Those would also be entered manually in the CODE and Description Fields. In summary, I don't think it's going to be feasible to do a macro to automate the CODE for the majority of your Cabinet Brands because of the complexity of those catalogs.

Marc, I've got most of the Conestoga Codes done in my macro based on the Cabinet attributes and sizes. There are a few that simply have to be manually entered and saved in the Library - but only a very small number and nothing that's very often used. I would like to have an cabinet attribute for the "room" which would facilitate identifying Vanity and Office cabinets as opposed to Kitchen cabinets. I have my macro set up so that depending on the contents of the Manufacturer Field the Code is set. This includes both stock sizes and Custom sizes. Anything that's not stock is prefixed with a "C". I still need to take a look at the catalogs you sent. It just seems that CA must have had something as a starting point for the automatic_labels. I strongly suspect that most companies use a very similar set of Codes. IAE, it would be great if someone at headquarters could chip in with an answer.

Chief provides an automatic_label attribute for Cabinets. This includes a prefix and suffix which must have been based on some manufacturer's standards. Does anyone know what manufacturer(s) that was originally based on? Most Manufacturers use a CODE that's similar to what Chief provides but there are differences. I want to automatically adjust the CODE in Chief for various Manufacturers but I would just use the automatic_label attribute for the ones that match (if any).

Without the Plan and Layout files I can only guess. Most likely it's because the Camera View Names in the Plan (Project Browser don't match the ones in the Layout - but as I said, that's just a guess.

Unfortunately there are no Defaults for the Label of Layout Boxes so you just have to insert that directly for each Layout Box Label. Personally, I have the Titles and Scale in the Plan Views I send to Layout in most cases. %view.name% and %scale% in the Plan are reliable as long as you edit the view names in the Project Browser.

Set the Text Style for the "Layout Box Labels" layer in your Layout.

The way I do it is to create another floor without a roof. IOW, the Floor becomes the Roof and you can draw railing walls on that floor.

You will need to do a bit of manual work. Edit the Doorway to raise the bottom - or use a Window Pass Thru. Drag the Roof of the Garage back over to the Main Wall Create a PSolid to fill the Wall that's not showing in 3D (create it in an elevation view so you can get the shape right). Create a Slab to fill the missing floor - you could actually check "No Floor below this Room" and use a Slab for the entire area.

In that case, simply open the room dbx and set the floor height and structure thickness. The walls shouldn't extend below that. You will need to make the opening in the Interior Wall as a "Pass-Thru".

If you are using a "Bay Window" - in the dbx select "Has Raised Floor" and set the values there for height and floor thickness. This will preclude it from going down thru the Garage Roof.

Just a followup to this topic. You can use any image as a texture with a % transparency to get the appearance of etched glass. If the image is black and white it works really well.

Val, Contact Customer Support - or just send it in as a bug report. This is definitely a bug and it needs to be fixed.

Open the Schedule dbx and uncheck "Use Callouts for Labels"

Layers can be turned off - Floors/levels can't. If you set up Annosets and Layer Sets for the kind of work you do - it should be fairly easy. You will need Layers for Existing, Demolition and New (Walls, Doors, Windows, etc.)

It's all about the number of surfaces in the overall Model. If you don't need the 3D of the entire project then just create Exterior Room Polylines for one of the buildings and Paste that into the Site Plan If you do need the 3D of the entire project then make a symbol of the building (delete the interior as much as possible to minimize the number of surfaces)

I don't think so. But you should be able to use or create a new Cabinet Door Symbol from one in the Library and adjusting the "Stretch Planes".

There's a couple of ways to do this: Use a separate Plan File for Existing vs New Use Layers and separate Layer Sets to show Existing, Demo & Remodel. There are some other ways such as using a CAD Detail From View to document the existing, but I prefer one of the above, depending on the project.

Ray, I have available the basics so only a small bit of additional code would be needed depending on the field(s) desired.

If you use one or more of the OIP fields a macro could do it. You would need to substitute the OIP field for the normal column in the schedule.

If that's the case, it can be done with Room Fill Patterns or a combination of a solid room fill and Material Regions with Fill Patterns but no texture.

Tim, I assume that you are trying to raise the ceiling height in one room. When you do that it pushes the floor above up. That results in the other rooms below that floor having a higher ceiling because of what's in the Structure definition for those rooms. The correct methodology is to change the Ceiling Structure or Floor Structure above to provide the extra thickness between Floors.

In the Default Room Label add %room.floor.finish.name% or enter that in a text box and place the text box in the room. btw, that's just one of the "Global>Room Info" macros that Chief provides which can be inserted in the Default Room Label or in a Text Box that can be located in the rooms.

Download them from within Chief Architect X9 - or just change the File Preference for .calibz You can do this at Control Panel\All Control Panel Items\Default Programs\Set Associations

Actually, you can use the OIP to include a Comment and/or addition to the Description for that Doorway.