-
Posts
12015 -
Joined
Content Type
Profiles
Forums
Gallery
Everything posted by Alaskan_Son
-
Creating roof plane on 1st floor...goes to the 2nd floor
Alaskan_Son replied to rockyshepheard's topic in General Q & A
Just sent you a PM -
Sounds to me like you need to change your rafter size in the roof structure dialog.
-
Yes, there are a few ways to coerce Chief into doing this. Can you be a little more specific though because the best method depends a little on the specifics.
-
Just turn the primary (and maybe secondary) contour layers off. No need to do any of the rest. You could also optionally just change the color for those layers to something totally different (I like a light blue).
-
That's the space between the top of your roof plane and the ceiling defined for your roof plane. If you were to frame that roof and turn the rafter framing layer on then you would see rafters in there.
-
Doesn't work with the elliptical ("3 centered") arch.
-
Created in about 2 minutes.
-
Looks like all you need is a double door, and an arched window with custom muntins... Door test.plan
-
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.
-
PDF Resource Drag, Why? I'm seeing only 1 core being used?
Alaskan_Son replied to zowie123's topic in General Q & A
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.