Richard_Morrison

Members
  • Posts

    1367
  • Joined

  • Last visited

Posts posted by Richard_Morrison

  1. 1 hour ago, Joe_Carrick said:

    Richard,

     

    San Diego is a much different place to work.  

    May be. But they still use the date the building permit application is complete -- i.e. the date they take it in as ready for review, not the date the permit is approved -- to set the governing Code cycle. This is on their website, and is pretty much the policy everywhere in California.

  2. 1 hour ago, Joe_Carrick said:

    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 !!!

    Generally, whichever Code you submit under (based on the date of the permit application) remains the governing Code for the project. For example, many people were racing to get plans submitted before the end of the year under the 2016 Energy Code because the 2019 requirements were far more draconian. Did the plan checker tell you that you had to submit under the new Code, or did you just assume that? 

  3. One idea is to read the Help menu on "Selecting Multiple Objects." There are a couple of recent features that will help you use a marquee to multiple select items without picking up extraneous types. For example, you can select a door and a cabinet, and then do a Shift-select marquee which will then only select doors and cabinets. There is also a Marquee Select Similar tool on the Edit toolbar which can be very helpful.

  4. On 2/12/2020 at 5:44 AM, Michael_Gia said:

    Just want to say everyone should subscribe to Steve’s YouTube channel. 
    The presentation and length hits the sweet spot for YouTube following for anyone learning.

    Even more advanced users can benefit because he always throws in a tip or two that you might not have known about or have forgotten about. 
    He makes for a great ambassador for promoting the program to people who are only trying out the program or are lurkers who are presently using other software.  More subscribers and more likes will give him more visibility. 
    I love a lot of the other videos from guys on this forum but they’re often not for newbies and they don’t have the flow, form and polish of Steve’s videos. 
    Keep up the good work Steve!

    I absolutely agree with everything Michael has said here.

    • Like 1
    • Upvote 1
  5. 37 minutes ago, Alaskan_Son said:

     

    We already have arrows in defaults.  The thing I assume you're wanting is the ability to set arrow style to be controlled by layer settings somehow...i.e. change layer set and arrows change to suit.  Is that correct?

    Yes, I really should have stated a by-layer arrow style.

  6. 4 hours ago, CARMELHILL said:

    Movie on how to create the detail with automatically resized text.

    https://youtu.be/VqK004LwYwY

    Ed,

    You might not be aware that you can set your text with leader to input standard text by going to Preferences>Text and unchecking Rich Text. Also, you can select all leader arrow lines at once by selecting "text line with arrow" and group selecting. I would love to see arrows added to defaults and have suggested this, but sometimes it takes a few years. :(

  7. On 1/3/2020 at 11:37 AM, Alaskan_Son said:

    Totally agree.  I’ve heard people argue to the contrary that it’s a regional thing, but it’s not.  It’s incorrect.  It’s just become normalized in some areas.  It’s the slow but certain degradation of the language.  It started as Tray, it turned into Trey, and now I’m even seeing Trace in some places.  

    Even worse is when people correct you when you are already correct, such as when you correctly pronounce the French word "forte" (meaning one's strength) as "FORT" and someone says, "don't you mean FOR-tay?" (Forte -- pronounced FOR-tay -- is an Italian word, used primarily in music to mean "loud") No, I don't, and neither do you. They are two separate and distinct words from different languages with different meanings. This is a no-win word. Pronounce it correctly, and some think you are incorrect. Try to be colloquial, and the people who know better think you are poorly educated. So usually I just avoid the word altogether.

     

    I'm still not happy with "ray-casted", but at least "casted" was used many centuries ago as a past participle. But it is (or should be) archaic now. Sic transit gloria mundi.

    • Upvote 1
  8. 13 hours ago, rgardner said:

    The reason I asked is I thought it was richard that mentioned in another post that he uses some cad details that have some pdf referenced cad details among his drawn cad details...

    Nope. Must have been someone else.:) However, the ability to store PDFs in the user library would be a good addition. 

  9. 15 minutes ago, Dermot said:

    Unless I have misunderstood, Brian and Richard are talking about copying a "Cad Detail".  Michael and others are talking about copying a "Layout Box".  These are not doing the same thing.

    I am talking about copying a layout box that has a CAD Detail in it. (i.e. Open a CAD Detail, send to Layout.) Copying a layout box which was sent from a CAD Detail produces inconsistent results. The copy is labeled correctly, has the correct scale, but is sometimes blank, sometimes just a very different origin from the original detail. Copying a layout box that has a floor plan seems to work fine.

  10. There is a huge difference between specifications and code notes. Specifications are for the contractor, and define contractual obligations. If you are working directly for a contractor, most will opt for as few specifications as possible. If you are working for an Owner, that is a different ball of wax. Over the past thirty-some years I have done it both ways, and found that if you put the spec's in a book, that book will stay in the contractor's truck, and worse, may not even be seen by a subcontractor during the bid. For a number of years, I was adamant about the electrical spec's being on the electrical sheet, for example, because contractors would tear apart the plans and give the electrician just the one electrical sheet. If the electrical spec's weren't included on that sheet, the electrician might not ever see them, and then you have a mess when the electrician claims he never saw the requirement for metal boxes and currently every installed box is plastic with a bunch of cracked nailing fins. When you can now distribute the whole set electronically as a single file, it doesn't matter as much, because there isn't an excuse that the sub never got the spec's. 

  11. Michael,

    I had problems with both. Here's the quote I received, "We do not currently support copying what we call CAD details in the program from plan to plan. My guess is you are either referring to a CAD Block containing a detail or a layout box containing a detail."

     

    I'll go back and try again. Maybe I misunderstood the response when I reported it.

  12. 1 minute ago, Alaskan_Son said:

     

    Huh?  It works perfectly fine for me.  Sounds like you must be trying to copy and paste from the Project Browser itself because copying a layout box and pasting into another layout box seems to work just fine. 

    Well, I'm only telling you what I was told by Brian Beck. It generally was problematic for me. Maybe it's because I was trying to copy CAD Details rather than plans. Not using the Project Browser. Copy/pasting text and annotation items from layout to layout worked fine, however.

  13. 2 hours ago, wjmdes said:

    Does anyone see any breakdowns in this process?

    Yes. You can't copy and paste details. (Occasionally it works, usually it doesn't. But I have been informed by Chief that it was not designed to work that way.) You need to double-click a detail on your Details.Layout and then send to your Project.Layout. When you go to send, there is a dropdown that lets you pick which open layout you want to send to. Otherwise, that is the way I would do it. However, I would put each detail in its own CAD Detail in the Details.Layout file.