Richard_Morrison

This has some nice objects, but now I find that I am getting e-mails from Wayfair. Has this happened to anyone else? Are our e-mails getting forwarded to manufacturers when we download content?

Tommy, This isn't a bug. X9 gave us the ability to place outlets ON cabinets, so there isn't a separate library category for "cabinet mounted outlets" anymore.

No, Chief does not validate anything. (Except a few code issues through the "Plan Check" tool.) You are responsible for designing your own structural members, lateral bracing, foundations/footings, connections, etc. If you don't know what you are doing, the program will help you make mistakes far faster than you ever could before.

In general, I usually like to see the revision clouds and deltas only on the layout page, because it's easier to manage layers. You only have the one layer on the layout page, vs. needing to pay attention to layers if you have them in the plan, say, multiple clouds on a framing plan and electrical plan and floor plan. You also have consistent sizing this way. (Uncheck automatic sizing, of course, for the callouts.)

It only picks up the last revision number, which can be either good or bad, depending on your view. Otherwise, you can just add the number directly. In general, I probably wouldn't want multiple versions of revision deltas, but some people do.

Happily, Chief DOES provide this function -- somewhat. You can add a triangular callout marker in Layout and insert a %revision.label% macro, and the revision number will appear from the Page Revisions table. (go to "Edit Page Information" to get to this.) You do have to add the callout manually, but it's not bad, since you can copy it.

Just for grins, I decided to run a comparison between Archicad 20 & Chief X9. I exported the chandelier in 3DS, and imported as a symbol into Archicad. I checked the number of polygons, and it was about the same: 3.8 million. Taking a camera view, after the initial model building, which took a few seconds to appear, 3D camera views were virtually instantaneous thereafter, even for new cameras created. Generating a new section/elevation, where the view depth included all 400 chandeliers, took about 2 minutes initially, then edits and zooms had maybe a two second lag max to regenerate. If the elevation depth were limited to one row (20 chandeliers), it was maybe 10 secs for the initial screen build, and pretty instantaneous thereafter. Due to background processing and tabbed views, I could make an edit in plan, then jump to 3D view or to elevation with maybe a one-second lag for a screen refresh. It would be no problem at all doing a project with all 400 chandeliers. Graphisoft clearly has paid attention to dealing with large models, and Chief could learn something from them.

You can also assign CTRL to one of the thumb buttons on your mouse, instantly doubling the available amount of one-handed commands.

Clearly someone who used to use Generic CADD. (Probably one of the best CAD programs of all time.)

You young whippersnappers probably don't recall the days of Chief when we were trained by experience to use the F3 key (hotkey for Save) like it was a telegraph key. Most kept a finger on this key at all times, and every couple of actions would tap this for self-protection. I still do this to a certain extent, and have never lost more than a couple of keystrokes worth of work.

This may go over some heads, or others are likely to say "too complicated," but there is a way to create extensive keyboard scripts that are triggered with one click, that will get you what you want. "Back in the day," Rob Fisher was the guru of this: http://www.chieftalk.com/showthread.php?34156-Keystroke-Macros I suspect if you spent some time with this, you could get some amazing results. Macro Toolworks is still around: http://www.pitrinec.com/

I suspect that this is problem is highly dependent on which cloud service you are using. I have had my plan files and User Library on Dropbox for years without a single problem. This also includes all Data files. So, for example, any changes to my hotkeys or toolbars get sync'd, too. I tried OneDrive and had occasional problems, and the sync was much slower. My User Library is currently at 1.4GB, and it only takes a few seconds to sync on Dropbox. I am a huge Dropbox fan.

For U.S. desktop systems, Apple has only about 20% market share. Worldwide, only 11.7%. http://gs.statcounter.com/os-market-share/desktop/worldwide I like Macs, but mainstream it ain't. However, if you're using other Apple products like an iPad, maybe a Mac makes more sense.

Jorge, I get the same results as you, but hadn't noticed it because I was using the same "other program." This is pretty bad, and should be sent to support for their review. However, I can tell you how to fix it. Take the CalCerts PDF and print it AGAIN to PDF, using Acrobat or equivalent. This copy will then import into Chief correctly. It's an additional step, and should be unnecessary, but it'll get you there in the meantime. Also, you should be aware that what is displayed as a PDF preview on the layout is pretty bad, but when it's actually printed, including to a PDF version, usually clears up. This isn't related to the first issue, but may be true with your code book issues.

Eric deserves the point, since his answer is illustrated.

Add a short invisible wall (room divider) at the end of the trench walls. (Well, where you want the trench walls to stop.) You may have to play around with the "Edit Wall Layer Intersections," too.

Maybe a solution would be to change the layer of the window to a dashed line layer after using William's approach, and then add a note similar to Joey's. Everybody wins. Group hug.

To be clear, I meant applying the molding in reality (i.e. the cabinet shop), not Chief. (Although not trivial in Chief, either!)

Johnny has a good point. While it's obviously possible, applying a molding that's curved in two planes is not trivial. Unless you are using flexible molding, there would be a tendency for the molding to separate from the curved substrate.

I suspect this will be easier to do in SketchUp and then import into Chief. There are already a bunch of similar hoods in the 3D Warehouse that you can start with, and manipulate from there.

You should mention in which state(s) the licensed (or registered) engineer needs to be licensed/registered. "Certification" is something very different, and probably not relevant.

It's a really bad practice to add notes with leaders to the Layout. The arrows attach themselves to whatever they are pointing to (and they cannot "see" any information in the view itself), so if you move a layout box or resize it slightly, not only are the arrows going to go all wonky, they probably will not be pointing to whatever you had intended them to point to in the first place.

Steve, people have argued about this issue before, but I personally (and I know that some people here disagree with me) think that it is a mistake to have a single source for standard notes and details because things can change behind your back. For example, you have a note that states IBC 2015 is the governing code. You submit a set of plans during this code cycle. When the new code cycle hits, you update the Code note to 2018. This will then update the Code reference for plans that have already been submitted under the earlier cycle. This is just a minor example where you DON'T want things to change behind your back, but it happens with details, too. Personally, I think it is better to have notes already on your template layout (not in a detail file), where they are not likely to change once you start using a Layout. Also, copying details into a Layout's CAD Detail manager, and sending the details from there, will keep the project's relevant details with that project, as well as keep the main plan file size down. You can have multiple plans referenced from the Layout of course, but it makes your life more difficult, especially if you want to move the project to a different computer or file location.

I think most architects would find this an "odd" set of plans. There are things that would normally be detailed, but aren't, like decorative beams, brackets, and columns, or fascia/rake/gutter/flashings. Seamed metal roof to asphalt shingle transition? Then there are things that are oddly "over-detailed" like framing elevations of standard beams in walls, and some of the kitchen/bath details which include furniture but no manufacturer/model numbers of fixtures. Then there are things that most architects know are fraught with high liability, like dimensioning rough openings. (Window manufacturer gets changed, and then it's all wrong.) Also, no real specifications. (Hardware? Drywall finish? Roofing product? Moldings? Warranties?) I think the set is impressive for what it shows Chief can do, but I wouldn't feel good about sending it out for bids. Then again, I don't know if Chief is representing this as the "real" set of construction documents.

Not sure what the sending to Layout part is about, since that was not related to my point, but as far as opening a Layout goes, if you have a duplicate "Notes.PLAN" file that is in the same directory as the Layout, it does not matter if the view was originally sent from a Notes.PLAN file in a different directory. The Layout will find and open the closest Notes.PLAN file, regardless of the original sending path. (Unless the file isn't there.) See page 1265 of the Reference Manual, or try it. I just did. So Steve, keep all of your in-use files in the same directory as the Layout, or in subdirectories thereof, to avoid confusing Chief, which is Chief's recommendation.