HumbleChief

He's referring to the different Layers he's created and wondering why they are not in each set. Look for 'molding kicks and lt blks' they are different in each screen shot.

OK I'm confused. If you add a Layer to a Layer Set it is added to all Layer Sets without the 'Modify All Layer Sets' box checked? Or is it (somehow) checked by default in your set-up?

I just checked this and Chief certainly does add new Layers to every Layer Set without the Modify All Layer sets box checked. Sorry for the confusion. What's that check box for again?

Edit: this is not correct see posts below. Ray that's how Chief is supposed to work. Typically you (I) don't want every new Layer to be in every Layer Set but if for some reason you do, check this box. EDIT: Whoa - I just checked this and Chief certainly does add new Layers to every Layer Set without the Modify All Layer sets box checked.

Don't confuse defaults with templates, they are 2 different things. Defaults need to be set up for each new house configuration and shouldn't necessarily be good from house to house. Templates of course are designed to fit houses that have the same basic configuration. So first thing is to set up the default floors, room heights, roof pitch, foundation type etc. If you can use a template from a previous plan (which include that plan's defaults), fine, but even then you need to check defaults first thing before you even start drawing the first wall.

The reason I have posted 4 or 5 times is because I've been through the ringer with Chief and just recently really understood the importance of Defaults.

I agree 100% with this philosophy of learning Chief. Learn Defaults, Layers and Anno Sets, then start drawing.

Yes, by all means model an existing house but DON'T start without understanding Defaults, Layers, and Annotation Sets.

Then learn about Annotation Sets. Absolutely key to using Chief effectively. Here's one from the great Scott Hall ANNO SETS FOR DUMMIES PART 1

Next Learn about Layers - they rule your every move as you design for different disciplines in Chief. http://www.chiefarchitect.com/support/article/KB-00765/

Here's a great knowledge base tutorial on defaults. LEARN THIS FIRST, it will help with every part of your plans as you proceed. http://www.chiefarchitect.com/support/article/KB-00463/

One problem that you will face is that most tutorials all assume you have a basic understanding of how Chief works and that the default settings are already set-up. Absolutely not so an Sherry's advice is key that you understand these concepts before you even start drawing. I found the video below that will help you with defaults. This is imperative before you start drawing. It's from an older version but you should be able to find the relevant info in the newest versions. I'll see if I can find some more that are most relevant for a beginner.

Agreed and said as much in an earlier reply to Doug. A sleek modern and easy to use GUI will have many unanticipated benefits down the road. Pretty pictures might sell the software today. I don't envy the decision makers at CA

I think accusing the Chief software engineers of picking the low hanging fruit is not entirely off base. They've said many times how certain changes are 'difficult' or expensive.

In my business it's 19 or 20 out of 20. Only making the point that different businesses need different features etc.

Good points Johnny and I agree to a point but remember 'what matters most' is what matters most to the individual user. There is no simple "this is what you should be working on because that's what I think you should working on." Too many users too many methods and client bases to generalize so broadly. For certain business models there's a lot of room for pretty pictures when selling a job in these days of HGTV etc. I have a contractor that I do a lot of work for and we spend a lot of time selling our kitchen and bath designs. These tools help us immensely in selling our jobs. I was NOT a fan of the pretty pictures in Chief for many years and wondered why anyone would want such features. Now those features are working overtime for me and my clients and I've grown to appreciate them. But that's just me and my business model. If someone does very little actual kitchen/bath design then why bother but for those who it has proven to be pretty valuable. To perhaps make your point we also never, and I mean never, use our design to build kitchens from. It always, and I mean always goes to the cabinet guy to do final Layouts and measurements but the tools still really help to sell the job, again within my narrow business model. Is that the market Chief is targeting? If so then bravo, if not and they are trying to capture or retain a different market with users such as yourself then they could seriously be missing the mark. I personally would love to see the changes you've been suggesting but there seems to be a different direction Chief is going in. Doesn't thrill me but like I said have been surprised how the new tools like cabinet stuff has really helped.

Maybe Google Flashing Details - hundreds of sites and hundreds of pictures. https://www.google.com/search?q=FLASHING+DETAILS&biw=1024&bih=751&noj=1&tbm=isch&tbo=u&source=univ&sa=X&ei=9fuRVPGrM9jtoATd84C4Dw&ved=0CB8QsAQ Oops, actually 41,800,000 results.

If I needed help I would hire a 50 year young Chief user in half a heartbeat.

Bob, I wouldn't use a CAD line to align walls. It can work but sometimes even a little off will create some nasty results. If you find you need walls to line up exactly across an opening drag a single wall across the opening and then break it to create the opening. Guaranteed to line up then. Or use Chiefs wall align snaps that will also get them aligned.

Ed, I'm no software engineer either but the 2 or 3 actions needed to update each elevation, which now includes nothing more than opening the elevation, closing and hitting the Yes button for each view, should be very easy to implement in a simple script. It's always more complex than I think but I think I see your point and agree that it's probably not as complex as I presented in a post above. If it really is that easy then not having that feature now is a real shame.

If I were a developer at CA I would be VERY, VERY curious about what this customer is looking for. Curious enough to contact them personally and see what, as an architect, they are looking for then implement something that gets them closer to becoming or retaining them as a customer.

To me the ease of which all tasks can be accomplished should take top priority. It forms the very basis and foundation of the program and will have a cascading, beneficial effect on all other features. If that looks like a modeless interface then so be it, but if it looks like a better idea that your team comes up with then even better. So to me ease of use is priority one.

Here's the link https://www.youtube.com/watch?v=el6IB4-fDrw#t=65

I think we get so used to doing things one way we forget there's a brave new world out there. I would LOVE the ability to select a line and have all the attributes right there for the changing instead of diving into dbx after tab after dbx.

True this.