Alaskan_Son

Okay. Then I don't believe the solutions above are really what you should be doing. You should really be setting your wall definitions to reflect the actual real world structure. If you don't have brick on the side walls then that layer should be removed from your new wall definition. Define your walls as they're actually being built...then, and only then (after your wall definitions are correct) should you start futzing around with fixing connections.

Curious. Have you actually conducted any kind of real world poll on this? I've heard a similar sentiment a few different times but I don't recall having ever heard it from a tradesperson...only from architects, designers, and heads of drafting departments. I would be genuinely surprised if you were to ask a few of your local framers and the majority said that they prefer center lines. I can think of no logical reason why they would want that. It just adds an error prone extra step for every contractor except maybe the foundation crew (which would typically have an error prone extra step either way).

Are you actually putting that pebble dash right over the top of brick?

I wasn't actually suggesting that manual entry is the most reliable. I was just saying that I think it might be a better method for this particular user based on the general approach and workflow they are using. The OP was placing an independent object (a text box in this case) on their layout page(s) to display the scale. This means that the scale is being reported completely irrespective of the actual views that it is representing. My view is that any scale macro being used should either be connected to and dependent on the actual view that it is representative of or that it should be entered manually. There are several methods a person could try to use but some are just bad or problematic practices in my opinion (and I am therefore you'll see that I have typed them up and then crossed them out)... Use the %scale% macro in layout. As was already discussed in the thread above, this simply doesn't work. The %scale% macro reports either the onscreen scale of the view it is in (when you're actually working in Chief) or the printed scale of the view it is in (when you print from Chief). When used in layout this macro is almost entirely useless because the view you are working in is a 1 to 1 scale. Use the %scale% macro in plan and in the same view you are sending to layout. This method is great and can be one of the most accurate and automated but can also require some pretty meticulous positioning of the text box in the plan view in order to get it to display where you want it on the layout page. The main thing here is that the macro is actually reporting the scale of the view that it is representing. Use the %scale% macro in plan but send the view to layout twice. This makes it a little easier to position the scale macro where you want it because you can simply crop the 2 views: one where the scale macro is not displayed, and one that only displays the scale macro. The problem with this method is that you have to make sure the 2 views are always using the same scale. If you were to adjust your scale after the fact, you would need to make sure to adjust both. Use the %box_scale% macro in the layout box label of your actual view and leave the label right there with it's layout box. This method is good as well but kinda limits what you can do with text formatting and means that you have to use the layout box label. This kinda sucks if you don't like to use layout box labels or if you are using them for something else. Use the %box_scale% macro in the layout box label of one of your views but drag the label over to your title block. This method is okay if your page only has the one view but it's kinda messy because you have to reposition the label if you move the layout box, and again, you have to use the label meaning you can't really use it for anything else. Use the %box_scale% macro in an independently placed layout box. This makes it easy to place in your title block independent of your actual views. Again though, you're forced to use layout box labels, but even if this isn't a problem to you, your layout box is no longer representative of any of your actual views. It's its own independent entity. This is a case where I believe it makes more sense to simply type the scale in manually. You get more control over the formatting by simply using a text box anyway. Use the %box_scale% macro in a text box and connect it to your layout box with a line/arrow. This is a decent method as well and is another case where your scale is going to accurately represent it's view when printed to scale; however you have to make sure the arrows stay connected and you have to jump through a few minor hoops to make the lines/arrows invisible (using line style or layer settings). This method always allows for an easy way to drag the scale text over to your title block. Again though, this can be a little weird and potentially inarticulate if you have multiple layout boxes on any given page. At the end of the day there are a few main points I would leave you with: The %scale% macro is the most accurate specifically because it will actually adjust to reported printed scale. If you print some 1/4 in =1 ft drawings at 1/2 Scale Check Plot then your scale will read 1/8 in =1 ft. %box_scale% is relatively accurate as well but will not adjust for printed scale. If you print some 1/4 in =1 ft drawings at 1/2 Scale Check Plot then your scale will still read 1/4 in =1 ft. Unless you are using the %scale% macro to report your Check Plot Scale (not something I've actually seen anyone do), then it really should only ever be used in PLAN. Any scale macros you use should really be getting their information from the actual views they are supposedly representing; either by being placed in those views or placed directly with those views. If the scale label or text box you're using is going to be positioned independently of the view that it's supposedly representing (typically in the title block), then I would suggest that manually typing is the most flexible and stable method and that in most cases will be equally as accurate anyway. If your construction documents are such that you are consistently including only one scale on each page, you consistently use the same scale, you want to include your scale in the title block, and you commonly print your plans at 2 different scales, then this is one scenario where you may consider using the %scale% macro in a totally independent plan view and then cropping that view and placing it in your title block. Repeat this for the appropriate pages where you're using different scales and the results will adjust to accurately represent printed scale whether your printing to scale or at 1/2 scale. This is really the only good reason I can personally think of to use any of the scale macros when they're placed independently of the views they're representing. Obviously there are a lot of approaches a person could take and you have to decide what works best for you and your workflow but those are my personal thoughts on the matter.

I'm curious, can you explain how Eric's advice was different from what George showed you 7 posts prior?

You can do this with Box Construction>Cabinet Corner Treatment>Clipped. Just set the appropriate corner width. One little downside though is that you need a cabinet on the opposite side as well to stop that corner from clipping. It cab be a very small cabinet and you can put it on its own layer and turn the layer off, but it needs to be there.

I don't know, but it just looks to me like someone is trying to set up a file sharing group with you. Kinda like a group folder in Dropbox but for emails maybe? I'm guessing its one of your clients or vendors.

OK, that explains it. Depending on how you look at it you are either using the wrong macro in the right place, the right macro in the wrong place, or perhaps the wrong macro in the wrong place. Based on what it seems like you’re doing I would recommend just typing your scale in manually.

What macro are you using, and is that an actual layout box or just a text box? If it IS a layout box with that scale macro in it, select the layout box and see what its scale is set to.

Board Stretcher? I think DeWalt might even be coming out with a cordless model here soon.

Ever have trouble losing the Extension Snaps/Snap Anchors that you really need and instead you keep picking up on others that you don't want? Here are a few power tips to help highlight some of Chief's handy dandy little tools that I think probably get overlooked or forgotten by the vast majority of us...'specially those of us what don't read the 'structions... We have a lot of special snap capabilities to control how snaps behave, but I specifically felt like offering some unsolicited pointers on-the-house regarding 4 of them: Edit>Preferences>Edit>Snap Properties>Options>Objects in History - This number controls how many Extension Line Anchors Chief will remember at a time. By default I believe this is set to 2 but it can be set to anything between 1 and 20. If you up the number to 20 you will probably never lose the Anchor you really want but you'll also have a whole bunch more of those extension snaps jumping out on you, so picking up on the one(s) you want might take a little extra effort. The "S" key - Holding down the "S" key temporarily overrides Object Snaps meaning you can stop Chief from setting any new Anchors while mousing around your plan. For example, you can set an Anchor at Point A, hold down the "S" key, drag your pointer through your minefield of potential anchors, release the "S" key, and then set an Anchor at Point B...and hold down the "S" key again if necessary while you wade back through the minefield again in order to find the intersection of those 2 Extension Snaps. The "1" key - Pressing 1 clears your entire Snap Anchor history (all 1-20 of them). We can use this to quickly clear the slate and start fresh anytime we mess up. The Control key - Okay this one seems a bit obvious but I think its easy to overlook some things about this one as well. The Control Key overrides all Snap behaviors including Bumping/Pushing, Angle Snaps, and Orthogonal Movement. I think most of us use this pretty often, but it can be overlooked as a handy way to allow a temporary override of these 3 items in particular. Holding down the Control key can allow us to drag an object closer to where we want it before releasing the Control key and then taking advantage of Snaps again.

Go into Tools>Toolbars and Hotkeys>Customize Hotkeys, search for "Spin" and you should find the Start Camera Spin tool. Assign a hotkey if one isn't already assigned. You can then simply hit this key to start the camera spinning. The spin speed can be controlled by opening your camera specification dialog and adjusting the Incremental Rotate Angle...the smaller the angle, the slower the spin. Note that the spin speed will only adjust the next time you start the spin (spin speed will not change if you change number after you have already started the spin). You can also simply initiate the spin using your mouse by letting go of the mouse button while actively rotating the camera (done with a sort of flick of the wrist), but the spin speed is extremely difficult to control that way.

I don't believe you're missing anything. As far as I know, those settings don't affect anything unless you specifically place an object on that layer.

In my opinion? There isn't one. You can use all sorts of tricks to coerce Chief into modeling any number of non-standard roofs automatically, but I feel like it's easy to invest more time and expertise in doing so than it would have taken to simply model it manually. My suggestion to you is to learn and master the manual roof modeling tools. I think you'll find that once you've learned the tools, you'll have no qualms about simply turning auto off and manually modeling just about any roof you can think of. From the looks of it, that scenario would take about 30 seconds to accomplish by simply turning auto off and manually adjusting. Heck, I bet the whole roof would only take 5 minutes.

Octagons yes. Hexagons, not quite as many.

Are you saying you have a Hexagon window in your Core Library? Or are you saying there's one in one of the Bonus Catalogs? Regardless, assuming there is one (which I don't have in my library), the chances that the casing, frame, sash, etc. are correct are between slim and none, and the chances that the size is correct is even lower.

Ya, you may never need a hexagon window again, but the same basics can be used to produce all sorts of other window shapes too. Its not too uncommon a need. In fact, it just came up earlier today in this thread... In that example though, you would use the Shape tab instead of the Arch settings. At any rate, I posted a link in that thread to a video I made a couple years back. Again, the window is a slightly different shape but the basics remain. P.S. I showed the Wall Cutout Polyline thing in that video as well.

You can actually make a hexagon window using a Tudor Arch. It will be sideways though... ....so you have to convert to symbol, rotate it, set to Inserts Into Wall, and then adjust the Wall Cutout Polyline...

Sounds like you must have used Rotate Plan View. That tool essentially just rotates the entire drawing board. You probably wanted to rotate the building and as such, should set the Plan View rotation back to zero and then use Edit Area to rotate the building and any other desired drawing elements.

This isn't exactly like your situation but may give you some ideas...

I think I would use a different approach. I'll attach a quick example plan, but the main points are: Set Foundation Walls to Hang Floor Platform Above On Walls (Structure panel) Adjust Footing Width and Footing Offset (Foundation panel) Draw the little framed walls separately just inside your foundation walls using a wall type that contains only framing and that is set to No Room Definition Example plan.plan

I don't know all your project details, but it can almost certainly be done automatically. The key is to do the following for all your As-Built components before turning auto framing on, and t's most easily done before drawing your addition although it can be done afterward as well (just takes a little more effort)... Group select all your rooms and check Retain Floor/Ceiling Framing. Depending on the situation, you may also want to put these rooms on a separate Slab Pour Number / Framing Group while you're there. Group select all your walls and check Retain Wall Framing. Group select all you Roof Planes and check Retain Roof Framing. Taking the above steps will ensure that none of the existing components get auto framed. There are more little details you'll need to work through to perfect the framing of your addition, but hopefully that should get you started on how to do it with auto framing turned on.

Yup. Lots and lots of ways. A few more... 1. Use Copy/Paste Hold Position and concentric edit mode to move the copy (use the Concentric Jump distance). 2. Use Multiple Copy to drag out a new copy (use the Primary Offset distance). 3. Draw a line that simply snaps to the end point of your desired lot line and then move orthogonally (use the Tab key and then enter the desired distance). Many many more methods but those are just a few ideas to get the ball rolling.

I think basement levels are always a little weird, both with regard to the Living Area label and with regard to the Plan Check tool. At any rate, you can trick Chief into giving you back your Living Area Label on Floor 0 by enclosing a little room off to the side that is completely separate from the rest of the structure. Now connect that room to the existing structure with a connecting wall. Now simply delete all those new walls. What's really happening is that you're tricking Chief into recognizing a new Living Area and therefore generating a new Living Area Label. When you draw the connecting wall, Chief considers them both part of the same structure and includes both areas in the total. Deleting the extra walls just deletes that one room and the new label stays. Also, you should be able to simply place the %living.area% macro into a text box to create your own living area label manually. This will alleviate the need to manually update any values.

Post the plan and you’ll probably get a more definitive answer, but it looks to me like Chief is just unsure as to which of those three or four walls to join to which of the other two or 3 walls and in which way to join them and their various layers. There seriously might be 100 or more different combinations of ways that those walls and their various layers might be interconnected and Chief is just picking one that you don’t want. When those unique scenarios arise, we typically have to use either the Edit Wall Layer Intersections tool, edit the wall definition(s), and/or use additional walls to help control the way they all intersect. in addition to the above, it’s also possible you simply have something set up wrong. It’s all guesses without a plan.