rlackore

Pretty much like Jonathan laid out. I import the whole mess and either map all the ACAD layers to a single CA layer (for simplicity), or if I need independent control of the ACAD layers then I map them to custom CA layers that have a prefix, eg the CONTOURS layer becomes A-CONTOURS - this way I can easily find/distinguish the imported ACAD data. Then determine the rotation angle to align the site plan with your building model; select all the ACAD data and rotate it in one fell swoop; then Point-to-Point Move to stick it in the proper place (or you can do an Edit Area(All Floors) Point-to-Point move of your CA data and move it into place on top of the site plan - you're choice).

The offending contour data was a fire hydrant that was drawn on the CONTOURS layer. Lesson learned to scrub the data before you import - or to isolate the data layer after import and take a really close look.

Yep, the points are useless. You'll have to use the contour lines. Create a Terrain Perimeter, join the contour polylines together at the breaks, then convert them to elevation lines. To refine things you can drop Elevation Points on top of the datum points. That's the best you can do with the data you've been given.

The elevation points in the ACAD file have a z-value of zero, so Chief is interpreting them correctly. However, the contours appear to have a z-value, so they may hold some promise.

Zip the dwg, or just change the file extension to txt and we'll change it back to dwg once we download it (I think that might work).

Not uncommon for me. Can't really predict why or when. Sometimes the wall clean-up tool fixes it, sometimes not, even with walls of the same type. Usually worse in areas where more than three or more walls intersect in close proximity.

No file attached.

Nice work Dermot - I never would have figured that out.

Easy fix - open the Door Schedule dialog box and remove the Hardware Group Column:

On an unrelated topic, your ADA Restroom is not ANSI compliant. Some of the issues are: 1. Not enough clear floor space at the door for a forward or parallel approach (when exiting the restroom). 2. The clearance at the water closet is insufficient - the lavatory intrudes into the space. 3. The sixty inch diameter turning space can include knee and toe clearance, but the toilet clearly intrudes on this space. 3. Be sure to show the vertical grab bar.

When I insert a new Door Schedule there is no Hardware Group column. There are no subcategories defined as Hardware Group. So, I don't have an explanation of how the Hardware Group column got added to your door schedule, but it's an easy fix - just open the Door Schedule dbx and remove the column. Ghost in the machine, perhaps.

The plan file is 0 bytes. Be sure to close the file before zipping.

I agree with Larry. Even when I find something on 3D Warehouse it invariably has little errors or doesn't quite fit the need.

The default door schedule doesn't have a "hardware group" category, so maybe you added this as a component sub-category? Could you post the plan so we can look at the doors and the schedule you've created?

I work in a small design office. We use Chief in a networked environment with all our job files stored on a local server. The only time we transfer a file to one of our work stations is if the server is down for maintenance. Chief has it's own file locking capability (Preferences>General>File Management>File Locking>Use File Locking), so you can easily prevent more than one user opening up the same file. There is no automatic method for tracking modifications, though Chief has a backup feature that allows you to revert to prior versions by loading an automatically archived version of the file. Chief has so many tricks, techniques, and work-arounds that it can be very problematic to share the development of a model between multiple users. We try to keep each project with one user, though this isn't always possible; when we do hand off a project to someone else we save the prior user's file in an archive folder for reference. If the project is deep into development there is more time lost in the transition between uses than there was when we were AutoCAD/Revit based; this alone is a strong incentive not to pass the project around the office. I also believe this makes it much more difficult to "enforce" office and drafting standards. Our printed output is much more varied than it was with AutoCAD. There is no reason you can't succeed with Chief in a small office networked environment, though If your office paradigm is to frequently shuffle projects between users, then you may find it doesn't fit your needs.

Okay, I see the problem with the upper-left area on the line drawing. I suspect it's a problem with Chief not handling the curvature of the wall/windows very well. Probably not a video card issue.

I don't see any obvious "missing line" issues in either plan or your saved elevations. BTW, did you mean to include a plan or image in your post #8?

I agree with Rob: review the truss drawings to make sure they conform to your architectural intent. If they don't, mark them up and send them back. If there are still issues (like whether a truss can be built to accomplish what you want), then get on the phone with the truss designer and hammer out a solution. Then you can update your model. So, ideally, the trusses should conform to your model, not the other way around. That's the simplest method.

I assume the second pic is from the CAD viewer; if so the text color is white - so is the background color in Chief.

It took 2 minutes for me this morning.

You attached a layout file but no plan file.

The attachment didn't stick.

Please post the plan and screenshots showing what you are describing, then we may be able to help.

Oh, library items. I was hoping it was a text dbx that I hadn't found.

Chief has 3D text? Please tell me where I find that tool. Thanks.