Joe_Carrick

Thanks Dermot, Since there usually are not that many sinks in a plan, I don't think there would be much "bloat".

Very nice !!!

OK, but that bypasses the automatic placement of the sink. Shouldn't there be a better coordination of the data when sinks are placed in cabinets? I guess I'll need to put in a feature request.

In that case, you will need a separate Molding Polyline for each molding. You would need to manually edit the Molding Polyline to set the distance from the doors.

Alan, There are 3 possible moldings for a room: Base Chair Rail Crown Each can use a different Molding Profile and locations (height and offset)

I suspect that you are not sending "Saved Plan Views" which would be specific to each floor. Another possibility is that you have the "Reference Floor" displayed.

When a Sink is added to a Cabinet, Chief just creates a 2D CAD Block. I can select the cabinet, tab to the sink and open the dbx. The sink can also be shown in a fixture schedule. However, if I try to get the name/value pairs (attributes) for the Sink I only get the attributes of the CAD Block. There doesn't appear to be any reference to the sink in the Cabinet attributes either - except for "has_appliance_or_sink" true/false. Does anyone know how to get to the Sink's attributes? I would like to include some of the Sink information in the Cabinet Schedule or in a "Note".

We have them. Defaults > Material Regions Floor Material Region Wall Material Region

Rooms don't have an "Object Information Panel (OIP)" so it's not possible to add "Custom Fields" to be used in the "Room Finish Schedule". Notes OTOH do have the OIP and a Note placed within a Room will pick up the "room" attributes, allowing all that data to be retrieved in user macros and displayed in a "Note Schedule" substituted as a "Finish Schedule". This makes it possible to use the Notes as "Room Labels" with both numbers and names as well as including Custom Columns in the Schedule. It may take a bit of work to define your new "Finish Schedule" with the appropriate "Custom Fields" and the "User Macros" but in the long run you will have a much more comprehensive Schedule.

I have no idea who the user is that goes by the name "Signatures" but the request isn't without merit. When we get questions it's often not possible to answer without knowing what version of the software is being used. Sometimes it's a Home Designer product and sometimes it's a Chief Architect product. In addition, the capabilities of newer versions are different than prior versions and it really helps to know what the version is in order to give the best answers. In addition, if a plan is posted it's much easier for us to see exactly what the problem might be rather than just guessing. It helps you get the right answer quicker and saves us making guesses that might not help at all.

IMO this is just a minor limitation of the "Style Pallets". It doesn't prevent you from selecting other doors and changing their type. It would be nice if it was a bit more comprehensive, but the "Style Pallets" is not a total replacement for "Defaults". Sometimes we just have to do some actual work rather than expecting Chief to do everything for us.

Rebuild 2D Block should fix that.

Yes, Ben's solution using the .convert_to() method works nicely but I'm not really up on the methods available with the Measurement Class. I really need a pdf document that is akin to the Ruby.org documentation. I think CA should provide that in their help files or a separate PDF for us.

In X12 all numeric attributes are Measurements that have "UNITS". Calculations return the same Units even though that isn't what you want. Change your macro to: a=(area*0.092903).round(2).to_f.sq_m.to_s

Go to the Terrain Specification dbx and set: Building Pad > Subfloor Height Above Terrain Note that it should be relative to Elevation 0.00 Example: Pad Elevation 4893' Subfloor Height Above Terrain = 58728"

So in California we seem to have a different set of dates. 2010, 2013, 2016, 2019, etc. The code adoption comes at the end of the year every 3 years. January 1, 2020 local building departments adopted the 2019 CRC (California Residential Code). I suspect this is just because to get the California Codes updated it takes about a year from when the International Codes are published.

Did you import the terrain into your X12 plan? Have you then created a Terrain Perimeter and set the elevation data to match the imported dwg? The other thing you have to do is set the offset so that your model elevation sits on the terrain at the correct height.

Yes, that's possible. However, I don't do that. One thing that I do is have a separate "Note Schedule" for each Floor. That way each Floor starts numbering at 101, 201, 301, etc. I could set it to start at 100, 200, 300, etc.

I use a couple of custom macros in a "Note" (rectangular with room_number in the top and room_label in the bottom) The Note (stored in the library) is placed in each room. The room data is picked up from the room the Note is placed in - all done with macros in Custom Fields within the Note. I also substitute a "Note Schedule" with custom fields instead of a "Room Finish Schedule". This provides a much greater amount of Schedule Detail than can be provided with a conventional Room Finish Schedule.

That's good to know, but it's pretty much irrelevant. There are not many changes from 2016 to 2019 and I only have one project that was submitted in 2016 and hasn't been permitted yet so I've just changed the reference to be the 2019 code. It's easier to make that change than to worry about it. Maybe I can program my macro to automatically update every 3 years.

Richard, San Diego is a much different place to work.

Yep. I've updated my Code List Text Block for all jurisdictions. This has been a rather annoying time. Submit for Plan Check - 2 months later get the plans back - make corrections - resubmit and the Code has changed - resubmit with new Code reference. Arrrgh !!!

When you create a Symbol just keep the original PSolid / Solid. You can save each modification as a Symbol with a version number. That way you'll build up a library of parts.

Just for your info: Convert it to a Symbol (Geometric Shape You can now copy, rotate, move and resize to your heart's content. I have no idea why the PSolid itself is not being more forgiving but at least this is a solution for you.

I almost always just select my "Saved Plan Views". The only time I would select a different Default Set or Layer Set is if I want to add a new Saved Plan View using different criteria. It's easy to start with one Saved Plan View ( Architectural for example) and then by changing the Default Set and Layer Set you could "Save As" (Framing, Electrical, Plumbing, etc.)