Joe_Carrick

Members
  • Posts

    11704
  • Joined

  • Last visited

Posts posted by Joe_Carrick

  1. Barton,

     

    I generally find that the "Light Bleed" is due to fixtures where the Light Source isn't positioned quite right within the Fixture - or it's the wrong type of Light Source.  Getting the position, direction and type of light correct takes some experience - and usually a bit of trial and error - but it seems to always fix the problem.

  2. I'm having some interesting experiences with the remodel/repair of our home after the kitchen fire last December.

     

    1.  Plans submitted for restoration/repair to the County of San Diego - over the counter approval (1 hour)

    2.  Exempt from the following code requirements which would have been required if there hadn't been a fire and we were just remodeling:

         a.  Title 24 compliance - all 14 Sliding Glass Doors are Single Pane Aluminum Frame

         b.  Fire Sprinkler System (house is 5150 sq.ft.)

         c.  Guardrails don't have to be brought up to current code - Horizontal rails are 7" o.c. and rails are only 36" tall

    3.  However, the inspector is requiring code upgrades for "Fire Blocking and Draft Stops" which were not required when the house was built in 1990.

    4.  The Inspector said that an existing bath that had mechanical exhaust also had to have heat added - but I've not been able to find such a requirement in the code.

    5.  Drywall attached to an interior plywood shear panel needs to be attached with 1-5/8" screws into the studs, not just with 1-1/4" screws.

     

    IOW, we have Selective Code Enforcement for a reconstruction which has a total cost of more than $450,000.  Some things are "Grand-Fathered" and some are not. 

  3. Geir,

     

    It appears you are in Norway - Oslo to be precise - so maybe they have your plans on file.  OTOH, perhaps you can talk a 15 year old Chief user to have some Lutafisk.  LOL

     

    Seriously, if you don't need it done in Chief - why not go to a local Architect and them do it for you?  I'm sure they wouldn't charge more than the job is worth.

  4. Lew,

     

    Yes - any user can unlock or lock layers as they wish.  But if one of my consultants did that they won't be my consultant for long.  The bottom line is that when I incorporate their work into my Plan, I only copy their layers.  Any changes that they make to layers that they aren't supposed to will simply be discarded.

  5. This is always going to be a problem unless Chief is made to be a Network Application with File Check-out and Locking capabilities.

     

    For purposes of collaboration with different engineering & building disciplines I simply give them a copy with all layers locked except the layers that they will be working on.  From time to time, I copy their Layers into my current Plan and give them a new copy to work on.

     

    You have to be careful to copy just the correct layers, but it does provide a way of having multiple users working on the "same" project.

     

    During this process, you will have several different Plans, but they will all basically be the same - and in the end they are all merged into a single Plan.  You should never give 2 users access to the same Plan - unless you enjoy seeing one of them overwrite the other user's work.  ;)

  6. FWIW,

     

    I've previously and repeatedly asked CA to make much more available to Ruby and also to make it so Interior & Exterior Elevations as well as Sections would allow Ruby macros for annotating Walls, Roofs, etc.  IOW, a Reference Macro placed on a Wall should be able to extract data (wall layer thicknesses and materials) so that notation could be almost automatic.

     

    Just Dreaming and Hoping ;) :rolleyes: B)

  7. Thanks Perry!  

    One question: I understand the use of macros that evaluate or display information pulled from an object. In your example, why would one prefer this type of macro over just a CAD block with the same, non-changing information. I'm still learning so the answer may be obvious, please excuse my ignorance if it is. Thanks.

    Barton,

     

    One advantage to using a macro for a simple Text String is that it's going to use the current Text Defaults so the text will be the right size.  A CAD Block will not be scale dependent, so you might have to resize if you use it on a different scale drawing

     

    Example:  A CAD Block created for a 1/4" Scale Elevation would be twice as large if placed on a 1/2" Scale Interior Elevation.  This is of course the same problem that you can get when taking Details from the Library.  They may be larger or smaller than you want.

     

    The other advantage as Perry indicates is that it"s "LIVE" and will update if you change what's in the macro itself.

  8. Barry,

     

    The Annoset is a set of Defaults.  When you select an Annoset, the Defaults for the Plan are actually changed.

     

    It's actually possible to completely ignore using Annosets and define everything in the Plan defaults and in the Layersets.  Annosets simply makes it easier to change several Defaults in a single step.  The main reason for having Annosets is to adjust the sizes depending on  the scale of the drawing.  This is due to the fact that Chief defines annotation in Model sizes as opposed to print sizes. 

     

    Assume that you use just one scale for Plan Views (1/4" = 1'-0") and your standard font is 1/8" Chief Blueprint then you could use a single Annoset for all Plan Views and control everything else within the Layer Set.  iw: Use custom Text Styles for individual Layers such as Room Labels, etc.