Alaskan_Son

Its the Inset that Chief doesn't like. Change the Inset to zero and it works. I would recommend you report this to Chief as unexpected and undesirable behavior. In the meantime you may end up needing to do that with multiple walls or a custom window symbol to get the inset look you're after.

You have me curious, especially after reading your suggestion... 1. If you’re using AutoCAD and it’s super easy in AutoCAD for you, can you possibly just export from Chief to AutoCAD and then export point data from AutoCAD. There’s nothing wrong with using supplemental software if it gets the job done quicker and easier. 2. How are you placing your elevation points in Chief? One of the main challenges is actually that Chief doesn’t supply us with a tool intended to measure point data in the first place. There are workarounds using available methods, but nothing specifically designed for the purpose. We can DEFINE elevation with points, but that’s really a different thing. If you’re defining points, my suggestion would be to just copy and paste your defining data into a table as you’re defining it instead of trying to compile and export it after the fact.

That was a $#!++¥ thing to say Alan.

By the way, one thing I commonly do is GROUP select the object if it's not behaving as desired during a Move or Rotate operation.

I was only able to take a quick look, but for now I think your best bet might just be to Display Wall Widths and then either Suppress those dimensions, mask them, or drag them out of the view.

There isn't one. Are you certain you need it for what you're doing anyway? Its not always necessary that the Z data be imported into your Total Station. I guess it depends on what you're doing with it though. P.S. I do have a method for automating the Z data output as well.

I don't personally think this is a downside at all. I can't speak to Joe's system specifically, but I recommend a polyline based system to most users as well. I've developed and utilized various hash, array, note, and schedule based methods over the years to compile and parse data for various purposes and although they work for some things just fine, they always seem to fall notably short when it comes to robust and customizable area analysis. Polylines obviously have to be managed manually, but they have some major benefits that can't really be replicated with any other method I've seen: They're exceedingly easy to customize in order to measure areas using whatever calculation method a person wishes (center of wall, exterior surface, exterior main layer, interior main layer, interior surface, etc.) They're exceedingly easy to customize in order to combine areas, exclude areas, or measure areas that otherwise have no usable model data (part of a stairwell, both a dining room and kitchen combined, a portion of the driveway, a bathroom combined with its shower, a birdseye footprint of the home, overhang areas, under roof area of a specific deck, area encroaching a ROW, etc.) They can easily and very naturally be used in combination with model objects that are already polyline based objects (roof planes, driveways, terrains, slabs, countertops, etc.) They lend themselves to very easy tabulation customization. Users can very easily break out, combine, re-order, and cross reference anything using standard or rich text boxes with each and every line formatted as desired...new decks, old decks, wood framed decks, covered deck areas, uncovered deck areas, demoed areas, carpeted areas, tiled areas, common areas, living areas, MIL suite area, combined closet areas, existing vs. new vs. addition vs. remodel, permeable areas, lot coverage, buildable area, sloped areas, shaded areas, etc. And any given line can be indented, underlined, bold, differing fonts and text sizes, etc. Its all fluid. They also require very little in the way of macro know how. Starting in X12, a person doesn't even need to open up Text Macro Management to use a simple polyline based area analysis system. Using polylines seems to be looked down on because they're not fully automatic and tied to the model, but the benefits FAR outweigh the minor downside of having to manually adjust IMO.

Bug. Please send in a report.

For larger projects, I typically use Arch D (24x36) for the exact same reason...so I can print half scale on Arch B (12x18). Depending on the project though, sometimes I can even get away with 8-1/2x11 layouts. It totally depends on the project around here. It's less about the size of the paper and more about making sure the text is the required height and that all the required information is on there.

Not sure exactly what Chop is doing, but I developed a very simple to use, tried and true method for this a while back very specifically for use with Total Stations. ImThe required 2D point data can literally be placed, compiled, and exported in about the same time it took me to type up this response. It just requires a small starter kit and some basic instructions. https://chieftalk.chiefarchitect.com/topic/25158-importing-points-into-a-ascii-format-for-total-station/?do=findComment&comment=202515

Looks like you just entered that information into your Default Interior Wall. Draw an interior wall now and the information should automatically populate the schedule.

I suggest everyone get in the habit of reading through (at least) and quickly testing out (preferred) the release note items one at a time at each new release. This particular item was a pretty big change Chief made. These settings are all controlled at the SAVED/ACTIVE Default level now opening up all sorts of new capabilities.

Oh, I see. I must have misread the first time around. I didn’t realize that it was only Joe’s macro. That would obviously depend on how the macro was written. I would try connecting it to another object in the neighboring room through. Another blank text box might even do the trick.

By the way, there are other things you can do as well such as connecting the leader to another object IN that room but it should actually work without doing that. If I simply copy and paste the text from your original post into one of my plans and then connect that text box to a room with an arrow, I get the information for the neighboring room, not the room that the text box is sitting in. Dermot showed the same thing in his example.

Okay. Your statement was just a little confusing.... Are you sure your arrow is set to Attach to Other Objects?

Walls>General Wall>Connect Island Rooms. This setting should really be left on. Its the island chases behind your kitchen causing the problem.

Is it a text box or a CAD Block? If its a CAD Block, unblock it.

Are you sure the arrow is actually connected to your text box?

It looks to me like you are assigning the settings to the wrong walls. The upper pitch stuff needs to be assigns to the hip walls not the gable walls.

Post the plan for a better answer, but if you select those lines, what layer are they on?

If the label layer is locked you lose the handle.

Post the plan for a more educated answer, but I'm guessing your fixtures are attaching to a ceiling plane above.

Unless you're a relatively advanced user with some pretty specific reasons for doing otherwise, I'd say you should only ever need the one "Default Set" Layer Set and that your Current CAD Layer should be set to "CAD, Default".

Sounds to me like you either inadvertently changed your Current CAD Layer (CAD>Current CAD Layer) so that those items were being imported onto that layer, or that you inadvertently moved your objects to that layer after the fact. Check what your Current CAD Layer is. You can also move the items to another layer after the fact by clicking on their Line Style tab and changing the Layer there.

This is the correct answer^^^^ You can however export as a 3D symbol or as a 2D DWG that can be imported and used as a reference.