Joe_Carrick

Select View > Toolbars That's a toggle.

Select the stair on the 1st floor and then click the icon on the Edit Toolbar to "Create Stairwell". That will automatically create the "Open Below" area on the 2nd floor.

You should make sure you have only one of the windows specified as "Include in Schedule" and "Show Label".

Larry, Shutdown and restart might fix it. But you should call SSA Support and see what they know.

%scale% is best used in the Plan. It's useless in the Layout.

David, What does your 1" Dimension Default and 1" Annoset look like? What does each detail look like before sending to Layout?

David, When you open the different details, remember to select the correct Annoset before sending to Layout.

BTW, Annosets are extremely powerful. It will be worth your while to learn to use them.

Each Layout Box has the "Layer Set" and "Active Defaults" when the view was sent to Layout. You must have something different.

Better to use a "Graphic Scale" in the Plan - that will always be correct.

David, Use 2 different Annosets with 2 different Dimension Defaults.

Dimension Defaults are per Plan/Annoset. If you use separate Plans for Details at different Scales you can have different dimensional accuracy. The other option would be to use a Secondary Format but then you would just have 2 dimension values. But of course the real answer is Annosets.

Small flat terrain regions in place of the points would work much better, assuming you don't want to use terrain lines.

Jared, Actually when you open the Layout the Plan is automatically opened - it just doesn't show in the Project Browser until you open a view. I'm not sure why CA doesn't display the Plan in the Project Browser immediately when you open a Layout. I've asked for that for a couple of releases but they haven't done it.

And that the Layout and the Plan are both open.

We've been over this before. Chief doesn't recognize any characters above Alt_0255. We need CA to add Unicode support.

Yes it's only in a RT - and I'm assuming you mean X9 (Version 19), But you also need to use a material with some degree of reflectivity.

Dermot, This has been a problem for some time. It has been suggested before that the Annosets should not only specify the Current Layer Set but optionally also the Current Reference Layer Set and the Referenced Floor Level Alternatively, the Layer Sets could be provided with those items. The options for Referenced Floor Level should be: Foundation <Floor Above> <Floor Below> <Previous Floor> This is the current behavior when changing Floors 1st Floor 2nd Floor 3rd Floor nth Floor Attic Currently I have my system set up to work with the <Previous Floor> scenario, but it would be nice to have the <Floor Above> or <Floor Below> optionally locked. IAE, I almost never want it to change, especially in the Layout. CA should really take a look at setting this up so we can rely on the Layout being consistent.

No, the Wall Details Labels are OOB simply showing the "Framing Layer(s)" of the Walls. If there is more than 1 framing layer in a wall there will be 2 Details. It would be nice if CA provided something like my macro OOB but it's easy enough to just modify the Templates and then you have it customized to your standards.

Johnny, You can use the %view.name% macro in that label. It will display whatever you have named the Wall Detail in the Project Browser. The attached macro can be used in the Default Wall Label and any new wall will be automatically named with the Floor Number and Wall Number and the Wall Type. Wall Labels.json

Import this macro in TMM (Text Macro Management). Then whenever you select an object you can open TMM and hi-lite _Object Properties to see all of it's attributes and their values. Any of these attributes can be used in a label by simply placing by enclosing the attribute with %.....%. The can also be used in a Text Box with Arrow. In most cases CA has already provided Object Properties to be used in the Label. Custom Macros can be written using the attributes as well. If the custom macro begins with: referenced ? obj= referenced : obj=owner then you can simply place obj. in front of the attribute and it will work either in a label or in a Text Box with Arrow. _Object Properties.json

You can open the Door or Window dbx and specify the number of trimmers, but there isn't any per width settings for the number of trimmers.

Attached are a couple of macros that can be inserted in one of the OIP fields to be used in Door and Window Schedules in lieu of Chief's "Header" column. There's no charge for these. Header Labels, OIP Fields.json

CJ, Use a Wall Niche and then move the Panel into that location.

You should ask your questions in the Q&A Forum. Tips and Techniques is for people to post Tips, not for questions. Some users will not answer questions posted in this Forum.