BlairDrafting

Members
  • Posts

    19
  • Joined

  • Last visited

Posts posted by BlairDrafting

  1. For anyone still curious about this issue: it appears CA is placing the sub fascia too high up on the roof plane. The soffit height is determined by the sub fascia in the roof plane structure. By increasing the roof plane's sub fascia from 5.5" to 16" (a ridiculous amount) I've found a workaround. I'm still not satisfied with this non-solution but at least it hides the problem.

     

    image.png

    image.png

  2. Thanks for looking into this Eric. I went through the same process and didn't get the result so I'm guessing I've made a mistake somewhere along the line. I'll review what you did and will try again.

    Do you know the reason the concrete layer in the wall assembly overlaps the wall above when it is on the main wall layer? I would prefer not to rebuild the foundation if I've got a basement and a bunch of work into it.

  3. I've recently noticed Chief Architect automatically will add numbering bullets to a text box when the first characters are a number followed by a period or parenthesis.

    For example: the text in my text box should be as follows

     

    ROOF LOADING:

    0.72 KPa (15 PSF) - D E A D L O A D

    1.89 KPa (39 PSF) - SPECIFIED SNOW LOAD

    2.70 KPa (56 PSF) - GROUND SNOW LOAD

     

    but it looks like this

     

    ROOF LOADING:

    0.72 KPa (15 PSF) - D E A D L O A D

    1. 89 KPa (39 PSF) - SPECIFIED SNOW LOAD
    2. 70 KPa (56 PSF) - GROUND SNOW LOAD

     

    Is there a way to have CA not automatically assume I want it to start numbering my lines?

  4. 11 hours ago, DeLayDesign said:

    Curious though.  The framing components you're using for the roof - are they 'actual' size 2x8s?  It's been a while since I've seen those.  I only ask because your roof structure is set to 8" even.

    You're correct. I must've confused the roof structure here with that of another job I'm working on. Thanks for pointing that out.

     

    11 hours ago, DeLayDesign said:

    If I replicate your original design (Because it appears the download file has been corrected), I see what you're talking about, but looking at how your original file is drawn, correcting it how you have in the download file would be the solution to this problem.  Plate height, window interaction, overhang etc. would all play a factor in buildability.

    I'm inclined to agree. Even in a situation where the roof requires a 14" (or bigger) joist I would still need to raise the roof to accommodate an appropriate heel height, which would likely also correct the soffit height. I would still like to know why Chief places the soffit above the bottom of the fascia in this situation.

  5. Please see attached plan file for reference. I've drawn a revision cloud around the soffit area I've been having difficulties with.

    Since my previous post I've adjusted the roof structure material to 9 1/4" (down from 14"), which has mitigated the problem, but not eliminated it.

    There is a railing wall which defines the roof bearing for that plane.

    I'm curious why this issue would affect one roof plane and not the rest of them in the same area.

    D-22-119 - BROLLY - FIELDCREST - DEC 2022 (AS-BUILT).plan

  6. I'm having an issue with soffits appearing above the roof planes. This mostly occurs with porch or deck roofs, but can also happen to a roof over dwelling. It is most noticeable on roofs sloped at 4/12 or less. I've been seeing this happen since I started working with Chief in X12 and thought I'd reach out to see if anyone else has thought of a solution.

    Renderings attached show above and below the roof plane.

    image.png

    image.png

    • Downvote 1
  7. On 10/31/2022 at 11:26 AM, rgardner said:

    There is one issue that is known and that is an issue when using dropbox and some other cloud services and working on the plan without downloading them to your computer.  It was an issue that dropbox had at some point but still comes up occasionally.

     

     

    My situation is similar in a broad sense. I've been working from an external drive with multiple plan files linked to one layout, some of which are linked from a different computer. The layouts I've been given to work with are often messy and are usually from previous versions of CA. I can see how X14 might have difficulty with reading from multiple sources and different CA versions.

  8. Hi all,

    I've been working on X14 for a few months, and I've noticed a bug I can't seem to fix or find a work-around. When working in a layout file the plan file will sometimes delink from all the layout's viewports when I use the undo button. It usually only takes a few minutes to relink all the viewports to the plan file, but recently this happened, and it corrupted the plan file to the point it was unusable.

    I've never seen this happen in X13 so I'm wondering if it has something to do with the way X14 manages linked viewports. Has anyone else had this issue, and do you know a way to fix it?

     

    Thanks,

  9. I'm having a minor difficulty with a plan file and am hoping someone in the community can answer this for me.

    Chief Architect defaults the drawing group order so dimensions show up over top of auto-generated framing labels (or any labels). Is there a way to change the drawing group order so I can have the labels show up above my dimension lines? Screenshots attached for reference.

     

     

     

    image.thumb.png.5ff1dd481a917504079831b8261703da.pngimage.thumb.png.e3d85ca0d6eb577de010b4c80434b6f0.png

  10. I've noticed a significant difference in menu text size from X13 to X14. I bring this up in this thread because I think it is related to the printing text. I work on a 15" screen so the larger text size feels much less comfortable. Additionally, many menu boxes now require a scroll bar, which adds an extra second to each time I have to navigate through object menus and whatnot. See the attached image showing the difference between the preferences menu in X14 (left) and X13 (right).

     

    image.thumb.png.a8204618f83b25ef1cd416ec261cdaa0.png