Alaskan_Son

That’s actually NOT what he said. Re-read that post.

Elevation Regions are nothing more than a series of elevation lines that have been closed (i.e. a closed elevation polyline). Once closed though, you get a couple extra options, one of which is to set the interior to be flat. For the desired end result in the OP, an elevation region set to have a flat interior is the most logical choice (and what I would personally use), but a person could also either add a series of additional 0” elevation lines to keep the automated smoothing in check, OR set the smoothing to linear. The latter may cause problems elsewhere on the terrain though if you needed the automated smoothing for other areas.

This is not the appropriate channel for that. You should send things like this directly to tech support if you really want Chief to look into it.

I haven't personally used it, but I know its actually required on the soffits for fireproofing in some areas when houses are too close to the property line. And I know I have several friend and acquaintances in the drywall industry who have done TONS of exterior drywall in Washington and Hawaii...ecven just for aesthetics. So yes, it is done, and its not all that uncommon.

Not sure what "WRA symbols" are but I used a large variety of objects for that particular project including cabinet (for the boxes) tons of multi-copied shelves and partitions for the modular storage slots, custom symbols for the diamond bins and wine bottle disaplay racks, and maybe some generic library objects and moldings for a few other things. I needed to draw this one super accurately though because my drawings were being used to produce the custom cabinetry.

I have...

2 ways that immediately come to mind. Open the desired plan view, change the layer set to what it should be, and SAVE PLAN VIEW. Right click on the desired Plan View in the Project Browser, Open Object, and then adjust the various items as necessary

That's where the manual toe kick comes into play. It's more accurate anyway. Those are typically installed as a separate molding and not part of the cabinet.

I feel like I must be missing something because the Cabinets, Module Lines layer should do exactly what you're looking for.

If I'm reading correctly, place a toe kick manually and then you can just use the Module Lines.

Yep. This is another good reason to keep them around. Good point Scott. Although, I will add that if you are managing your Plan Views properly, this should never happen.

You still have to define them one at a time. All the annotation set does is SWITCH them as a group. And this is something Plan Views can do as well.

Just build it as a Half-Wall (Railing set to Solid) and set that to be a Foundation wall using the appropriate wall type. This will keep you from having to drag the wall down in elevation.

Just change them. You almost got it. Here's the thing though. Seriously, just ignore that Annotation Set drop down. It doesn't matter if you change one of those Active Defaults in the Plan View dialog or in the Active Defaults dialog, either way, as soon as the list of Active Defaults doesn't match up to an Annotation Set, the Annotation Set will change to "Currently Using: Active Defaults" . If that list DOES match up to a currently defined Annotation Set, then you will see the name of that Annotation Set in the drop down. So, you can use that dropdown to specify an Annotation Set if you want to, otherwise it serves as nothing more than an indicator as to whether or not that group is already defined as a specific Annotation Set or not. I'll say it one more time. Annotation Sets are nothing more than a pre-defined group of Active Defaults. You can set them one at a time or you can change them all at once by defining and using an Annotation Set. Using an annotation set just helps save the time of switching the Active Defaults one at a time is all. They're nothing special beyond that. Plan Views work on the same concept. They remember the state of your Active Defaults but in addition they also remember more stuff.

Go back and read or re-read this post... ..if you're still not quite getting it, let me know. The point I feel like I'm having a hard time getting across is that Annotation Sets aren't doing the things you say they're doing. It's your Active Defaults that are doing all that stuff. Annotation Sets are just a quick way to change those Active Defaults as a group. Plan Views can change them as a group now too though so whether or not you feel like you need to use both those layers of control is up to you.

You’re more than welcome. And sorry, I meant to answer your question but something important came up so I had to leave for a bit. I believe there are a handful of good reasons to keep annosets around. They can serve a unique purpose still and give another layer of options to work with (Rene gave one good example above). Even if they didn’t though, I think they would likely stick around for quite a while for the “old school” guys and gals, for legacy reasons, and for larger companies with large databases who find it would be too costly to switch systems. Having said all that though, I also think that the vast majority of Chiefers could completely do away with them and they would be better off.

Ya. You could continue to use Active Defaults and optionally Annotation Sets for this purpose just as always. This is one good reason for keeping Annotation Sets around for sure. For the record, I wasn’t actually suggesting they get rid of annotation sets entirely because that can still serve as a good organizational/annotation object group control tool. I was only trying to point out how they’re not really necessary anymore for what most of us use them for and how they’re a redundant control for most people’s workflows.

To answer a few of you guys at the same time re: anno sets... Try to completely forget about the term Annotation Set for a minute. I feel like you’re getting too hung up on that term. Now ask yourself this question...Do I know EXACTLY what Active Defaults are (this is not some generic term I’m making up) and and do I know where that dialog box is? We have always been able to change our Active Defaults without using an Annotation Set. Nothing has changed. Simply set your Active Defaults to what you want and then Save the Plan View. No need to assign an anno set if you don’t want/need to (which most people don’t). I’ve said this many many times before, but an annotation set is just a pre-set group of Active Defaults. Change them all as a group using an annoset or change them one at a time, it’s really up to the user. As I also said earlier in this thread, right click on a Saved Plan View in the project browser. Look at everything Plan Views remember. All the Active Default items are in there. Set them to whatever you want them to be...either right there or in the Active Defaults dialog, it doesn’t even matter which. When you do so though, you are choosing not to use an annotation set. Just because you see an annotation set dropdown doesn’t mean you need to use it. For the less experienced users. Here are all the basics in a nutshell. - Items are displayed using their LAYER and it’s related settings. - LAYER SETS are a way to control the display of those layers differently as a group (roof plan vs. electrical plan for example). - ACTIVE DEFAULTS allow you to select which text, dimension, and other annotation object defaults you want to use at any given time (these defaults may control the text style, dimension format, layer the annotation object is initially placed on etc.) as well as which layer your CAD objects are place on (referred to as the CURRENT CAD LAYER - ANNOTATION SETS are what you get when you choose to save a group of the afformentioned Active Defaults. Change the annotation set and the Active Defaults all change at the same time. The annotation set can also optionally change the Layer Set along with the other Active Defaults. - Plan Views are much like Annotation Sets and can be set to remember EVERYTHING annotation sets remember but they can ALSO remember zoom settings, floor numbers, color on/off toggle settings, whether or not a reference floor is being used, which reference floor is being used, which reference layer set is being used, and there may be more things I’m forgetting. In addition, Plan Views are also stored in the Project Browser which can make for a much more efficient way to manage your plans with or without a layout being open.

I’m not sure I totally understand your question, but I think you’re maybe just overthinking things. As soon as you SAVE a Plan View, it will remember the layer set, the Reference Display settings, whether color is toggled on and off, and all the Active Defaults amongst other things (including the option to remember floor and/or zoom setting). If you save the plan view using a specific annotation set then it will remember the annotation set, otherwise it will just remember your ala carte active defaults. To old and new users alike, I would just suggest that you make sure you fully understand what your Active Defaults are. Annotation sets are not a complicated critter. All they are is a set group of Active Defaults. If you are simply using annotation sets to change your Active Defaults in one fell swoop the Plan Views will do all of that. The big kicker here is that they can also do a lot more than that though. Open a Saved Plan View from the project browser and you can pretty quickly see all the things they can be set to remember. Now to anyone trying to teach or help new users, I would really encourage you to make sure you fully understand Plan Views before teaching or encouraging them to use Annotation Sets “the old way”. Yes, tell them what annotation sets do (change your Active Defaults as group), but I really think you’ll be setting them up with an inferior workflow if you ignore Plan Views.

IMO, teaching annosets at this point in the game only adds unnecessary complication. My primary focus when teaching new users is to first get them to understand layers and layersets...followed by Active Defaults...followed by a very brief description of how annosets are nothing more than a way to change Active Defaults as a group. I put VERY LITTLE emphasis on anno sets since they’re really not necessary anymore. I place emphasis on using Plan Views to change all that stuff. No point in teaching someone how to use a tool that they’ll stop using in step 2 of their learning curve. Yes, tell them what it is and how it works, but I wouldn’t recommend using annosets as a baby step. No reason IMO not to jump directly to Plan Views. When setting up new plans and templates from scratch now, I don’t use anno sets AT ALL. In fact, I would personal be totally fine with it if Chief removed them from the program entirely. I guess they could still be handy when creating new Plan Views but only in a pretty minor way. Anyway, that’s my 2 cents on that subject.

Just a thought, but if you’re pulling back the rafters then they’re becoming pretty inaccurate in both plan and 3D anyway. If you ask me, then I say you should consider just removing framing from the structure of those particular roof planes entirely so they don’t even frame to start with.

Just a side note here, but if you’re fully and properly implementing Plan Views, annotation sets and their optional control over the layer set really become redundant. The plan view will remember all your desired Active Defaults (this was essentially the sole purpose of annotation sets) and your layer set. I don’t even have an annotation set drop down in my toolbar anymore. It’s pretty well pointless now IMO unless you’re choosing not to make use of Plan Views.

I don’t think I ever made a video about that. It was likely just some tips I typed up in a forum post, and more likely than not, I was suggesting a truss base and using trusses that basically resulted in nothing more than the top chords (rafters). Just because Chief is calling it a truss doesn’t mean it can’t be a rafter. Whatever gets it done right!?

You bet.

I haven’t opened your plan, but based on your wording it sounds like it’s possible you’re being a little reckless with your settings trying to find the right combination. See if this clarified things for you at all... 1. You have to have auto regenerate deck framing toggled ON or else your framing will not adjust once you make any changes. 2. You have to divide the different areas up into different “rooms” using some sort of wall (DO NOT check No Room Definition on these walls) if you want to have automatically generated planking running in different directions over different areas. 3. If you’ve been toggling settings willy nilly to try and get your desired results then you should probably check ALL your deck rooms one at a time to make sure the rotation is set appropriately, that auto regenerate is toggled on and that auto planking rotation is toggled off (just to be safe). I am away from my computer, but if I recall correctly, this could very well result in two adjacent decks having the exact same angle setting due to the shape of those rooms. 4. Make sure both your framing layers are in the Floor Structure layers and that nothing is in the Room Finish layers.