Joe_Carrick

You can do it. My Framing Labels macro handles almost every possible condition for me - but sometimes it's just as easy to do a simple one using some of the built in object specific macros. There are not that many things that are able to be automatically labeled in a section view.

Yep.

Here's a simple example. I didn't fully annotate this but everything you see is automatic. Framing Labels are reference macros where cut in cross section, the dimensions are of course Auto Story Pole and the Title and Scale are a CAD Block with %view.name%, a scale (text) based on a macro that sees 1/2" in the "Layer Set Name", and a Graphic Scale. Additional annotation can be done manually for wall materials, floor surfaces, insulation, etc.

To create a LIVE Wall Section: Use an Orthographic Back Clipped Cross Section Adjust the Position of the Camera Callout (Right, Left or Both) Set to "Clip to Sides" and adjust the extents. Reset the Drawing Scale to 1/2" = 1' Select an Annoset/LayerSet combination that is designed for this view and scale Add a Story Pole Dimension Add Object Specific Annotation User Custom Text Macros (referenced macros with Leader Lines Labels for some Objects Auto Detail as needed Add Rich Text Title %view.name% as named in the Project Browser Add a "Graphic Scale" Now, as changes are made to the Plan, the Wall Detail will change accordingly.

In X9 a layer_set attribute was added to each object. In most cases that matches the "Current Layer Set" but sometimes it only matches the Layer Set in use when the object was created. This seems to be true for all Architectural Objects. OTOH, Text Objects always match the "Current Layer Set". So, in User Text Macros I use a global variable $LayerSet when I want to know the "Current Layer Set" in order to get a different result based on what that is. In order to set that global variable, I've added the attached macro to all my Defaults for Callouts, Markers, Text and Rich Text. Then it's just a matter of placing at least one of those items in all Plan Views, Sections, Elevations, CAD Details, etc. Whenever the Layer Set is changed, the value of $LayerSet is updated. LayerSet,Global.json

Eric, I do that so the it's easy to add (concatenate) the result. example: result = area.round(2).to_s + " sq.ft." result = "Area = " + result or, if you want to perform some other calculations: x = area.round(2) result = "Area = " + x.to_s + " sq.ft." There are other ways of coding to get the same result.

Select the Room and then "Create Room Molding Polyline". Click any segment that doesn't have the Molding and check "Molding on Selected Edge.

Create a new macro named "Area.rounded" Check "Evaluated" Select Context "Owner" enter the following in the macro result = area.round(2).to_s insert that macro in the Polyline Label.

The reason I do this is so that I know which Layout goes with the Project. They not only don't have to have the same name but they don't even have to be in the same Folder. But having them the same makes it easier to keep track. btw, I have several "Detail Plan Files" that are linked to the Layout in addition to the "Project Plan File". My "Detail Plan Files" are in a Folder that never changes location so they never need to be relinked.

Open the Layout Select Tools, Layout, Relink Files Then just Browse to the Current Project Folder and select the Plan File.

My guess is that "Seeking Services" gets you to ChiefTalk is because CA intended that it be a resource for people looking for a professional Designer or Architect. I don't think "Seeking Services" was ever intended as a Q&A or Help system for learning how to use the software. CA actually has training courses if that's what you are looking for. It's a good idea to read the purpose of each Forum to determine where to post.

The Exterior Wall Layer could be turned off - still not ideal but it will work. Another option is to just use the Glass House Render Mode.

You would need a pic of a (1) full tile and (2) half tiles below (running bond). The best way to do that would be to take a pic of 3 tiles and then crop it. That then becomes the Texture that is repeated.

The only way I know of doing that is to make the Exterior Walls a Transparent Material (Glass for Example) but they wouldn't really be "Wire Frame".

You would need to just delete those views from the Layout. Once the Layout Box is gone, the link will disappear.

Try 6 and see what happens.

Larry, You can also go into Preferences and change the Undo Folder to a Folder on your SSD which should help a lot. I have it set there and I limit my undo stack to 12.

It may be that the new "Undo/Redo" settings in X9 are having an effect. The higher the settings, the more disk I/O and swapping might be required. I believe Chief is making a copy of the model in memory for each change to the model and saving it to disk. Depending on the location and size of the swap file, this could result in a very large "Undo Stack" and result in memory being written to disk (probably an HHD. If I'm correct then reducing the number of "Undo's" could result in much better performance. It might also be possible to increase the size of the "Cache".

Just re-link to the Plan File(s) you want your Template to use. If you set the Template to be the Default Layout Template then it can automatically be used when sending from a new Plan that doesn't already have a Layout.

It's in the Symbol dbx (the little chair icon on the Edit Toolbar)

Curt, You can access the individual labels of a mulled unit by tabbing.

I agree. If anyone at CA is monitoring this thread, it's something that should be investigated.

Yes, Blocking simply adds another level of complexity. Blocking sets all the sub-items location as relative to the Block's origin There is no reduction in Face Count. Rebuild has to use a transformation matrix to adjust each object's location vs the Block location. Create Symbol OTOH only saves the visible external faces of what's visible This results in many fewer faces No transformation matrix is needed since everything is located relative to the 0,0,0 coordinates The moral of the story is to create symbols (rather than blocks) unless you absolutely need to have access to the original objects. That is sometimes true but usually it isn't. Maybe CA could come up with a way of knowing what needs to be rebuilt but it might not be that easy and it could cause other problems.

You can also use a "Panel Railing Wall" with the Horizontal Mullions built into the Panel (Glass for the main part of the panel) and use the Newels as the Vertical Mullions. Set the Newels at full ceiling height. I did a video some time ago with this method but I don't know where it is - probably in the old Forums someplace. You can insert a doorway into this "Railing Wall" and change it to a "Hinged Door".

Yep, I personally decided to just keep those Ctrl_ keys. It's just too hard to give up the defaults for all the standards. We've been using Ctrl_C, Ctrl_X, Ctrl_V, Ctrl_S, Ctrl_O, Ctrl_P & Ctrl_Z for as long as I can remember in almost every App. That's just one of the nice things about Gaming Keyboards - you can assign any regular key (including Del, Home, End, etc) to any of the Gaming Keys. Even the Alt_ keystrokes (such as <Alt_248> °) can be assigned to a Gaming Key.