rlackore

That cursor indicates that you have angle snaps turned off. Turn angle snaps on, and the icon will disappear.

That is a really interesting capability, that initially seems filled with so much promise, only to fall short in so many ways. Sometimes I feel Chief doesn't follow through on their ideas and implementations. Nonetheless, thanks for pointing this out - I was completely unaware of this feature.

You can combine plan files in Chief, but they won't "auto-update" like an AutoCAD Xref, because they are now part of the plan into which they've been inserted. I've been using TwinMotion, which may do what you want, sort of. You can export your Chief models as .dae files, then import them into TwinMotion - they can be "refreshed" within TwinMotion easily after you've made changes. There are quirks, of course, but TwinMotion is fairly easy to learn and is very fast and responsive. It does crash too often, which I think has something to do with Chief's .dae exports. This screen shot shows two Chief .dae exports, imported into TwinMotion; notice in the Import tab that they are two separate DAE files:

I don't know what controls which Floor Level a Polyline Solid is placed on, but moving it is easy: find it, select it, cut it, move to the desired Floor Level, and Paste>Hold Position.

I can't share the file - I'm on X12, and you won't be able to open an X12 file on X11. Refer to the Reference Manual, I think it can get you headed in the right direction:

For more help, download the Reference Manual for your version of Chief - there is a lot of good info that will help you with manipulating roofs.

Turn off Auto Rebuild Roofs and edit the roof planes manually:

To your points: 1. In my jurisdiction, the original, stamped and approved plan set must remain on site. Revisions do not have to go through plan review but must be available for the building inspector. The inspector can make any call on whether a change is permitted or must be resubmitted. 2. Expecting zero revisions to the construction documents (plans, specifications, etc.) would be ideal, but is unrealistic. Errors and ommissions account for some needed revisions. Other revisions are required by changes in the scope of work, discovery, etc. Also, fast-tracked projects are, by definition, fluid and require continuous updating of the contract documents. 3. As the project manager for the architect, I distribute revisions to the relevant parties: the general contractor, the owner, and occasionally to consultants or specialty contractors. I do not interfere with the GC's obligation to keep his subcontractors in the loop. Of course, I answer questions from subs all the time, but ideally, the flow of information to most subs should go through the GC - not the architect. 4. Design-build is a different animal. As architects, we may be hired by the building owner, by a general contractor, or a developer. We are always intermediaries between different parties who often have competing interests. We do our best. Good for you for figuring it all out.

I can't tell you how many job sites I've visited and found the only physical drawing set available is tattered, unbound, dirty, and out-of-date. As a project manager and the architect's (and client's) representative, my best recourse is to always take a copy of the most recent drawing set with me, leave it on-site, and throw out the old set. When we run across a GC who can't get their act together, we don't refer or recommend them for future work. Perhaps you could do something similar: if a sub can't make the effort to ensure they are using the most current drawing set, don't use them on your next job, and tell them why. Of course, ultimately, as the GC, it's your job to distribute and enforce the use of the most current plans.

If you want a single room, you can remove the ceiling, then manually place a flat ceiling plane in the "flat" room, and sloped ceiling planes in the "vault" room.

I know this is a hack, but I use two double-hungs, stacked and mulled, to simulate the typical Eze-breeze four-stack unit: It's not perfect, but it's relatively quick and easy and doesn't require a lot of messing around. It's not perfect in close-ups, but for most situations, it works reasonably well.

Some custom garage doors I had to make for a project. Chief X12 library file: Custom Garage Doors.calibz They use default Chief materials, so should import fine. Two sizes: 9'x8' and 18'x8', three sections high. Four flavors: panel lights; panel lights with grilles; panel lights with braced frames; panel lights with grilles and braced frames.

Like Eric says. Here's a project where I created a CMU areaway off the stone foundation (old farmhouse) and defined everything through the Room Specification dbx. Notice most of the settings are changed from the default. Placing the Bilco unit on top is simply a matter of finding/creating a Symbol. Areaway Doors.calibz

Thanks.

It isn't?

To a certain extent, but the %schedule_number% macro doesn't work in Rich Text boxes, at least not for Rooms. I will make a Suggestion.

For a few versions I've been using Rich Text boxes and macros to create custom room labels. However, I'm trying to leverage the power of schedules, and have figured out how to add the %schedule_number% macro to the default Room Label; however, any text (or macro) entered into the default Room Label appears after the room name, and I can't determine if there is a method to display the schedule number before the room name, e.g. 005 bdrm instead of bdrm 005. Has anyone else solved this problem?

Didn't know it was in that menu. Thanks Eric.

This is in X12, but maybe it was there in X9:

It's not obvious, but it's easy. With the camera view open, use the toolbar icon: or, in plan view, right-click on the camera and use the context menu:

Select the Exterior Room (it's a narrow band just outside the exterior walls) and check if the material was changed from the default:

Download a copy of the X12 Reference Manual. Robert was referring to this: Lots of good info in the Reference Manual. I'm not saying this will solve your issue, but may be helpful.

Chief Premier installs the Chief_Blueprint.ttf Truetype font.

Glen, I completely missed that part of your post - and it was right at the top! I apologize. Thanks for the help.

I agree. I know this topic has been raised as a Suggestion. Chief is still way behind in basic CAD functionality.