Joe_Carrick

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.)

Select the area between them and make it a "Deck Room"

Try 3D Warehouse and search for "Patio Heater"

I don't think that's the point. Default Sets and Layer Sets are the basics giving you a set of Defaults and Layers to choose from. Reference Layer Sets are now more important than ever. Saved Plan Views simply allow you to save a view so that it retains: zoom factor layer settings (Primary Layer Set for the type of drawing - Architectural, Structural, Electrical, etc.) default settings (How various things will be created and diaplayed) floor level reference floor displays (floor numbers and layer set) etc Then whenever you reopen that view all of the above will be as they were when you last saved that Plan View.

If you have a straight on photo of the material you can use that to create a texture.

My solution is a little different: 2 standard framed (or unframed) cabinets 1 center unframed cabinet (sides are normal) select all three and convert to interior furnishings symbol (hangs on wall with appropriate height) add to schedule as "Wall Cabinet"c Make sure you edit the label and description to show what you want in the Schedule.

San Diego County still accepts 2016. San Diego City doesn't. PITA

I just had a set of plans rejected because my Code Reference was to the 2016 CRC. I didn't even know the 2019 had been adopted. Does anyone know if there have been changes from the 2016 CRC? If so, what are the changes?

I have a lot of different wall types stored in my user library. The variations are numerous, including lots of different material layers, and even if there's a pony wall. When I want a particular wall type I just select that from the library and start drawing. It's much more comprehensive, allowing for wall thickness, new/demo/existing, etc.

If you have an X10 license, why not download it from your digital locker to the computer with X9 and install? If they are both yours then you can use X10 on both - just not at the same time.

That's one I posted several years ago. I'm pretty sure it was X8 or earlier. IAE, it still works and CA hasn't come up with anything better.