-
Posts
6103 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Everything posted by HumbleChief
-
Lumber size restrictions and ridge board/beam
HumbleChief replied to RyanDe's topic in General Q & A
+1 -
Lumber size restrictions and ridge board/beam
HumbleChief replied to RyanDe's topic in General Q & A
I don't think there's any absolute formula one needs to follow. You don't have to go to a professional designer on day one, or ever, if you are pleased with your ideas and they fit your life style and family needs. Any design almost always needs an engineer's expertise to size lumber/footings etc. but if you like the design you've come up with then build it. Chief gives even the DIY designer some great tools to visualize the finished product and there's really only one test of whether or not you've created a 'good' design and that's if it pleases you. If you rush it then you will run into trouble but if you consider many different aspects of design (they are not really all that secret) there's no reason you can't come with something more than livable. I say jump in with both feet!! -
..nor is it shown in section if it's the only layer selected. What other layer behaves like that? Why? What are cross section lines?
-
I have a feeling 'Cross Section Lines' have a very unique purpose in Chief. If the 'All Off' layer set is used then just the 'Cross Section Lines' layer is selected, nothing shows. But if your Section Layer Set is chosen, 'Cross Section Lines' will turn on and off with the layer. So they are there but not really 'there' and behave like no other Layer I know of.
-
Lumber size restrictions and ridge board/beam
HumbleChief replied to RyanDe's topic in General Q & A
That's as good a strategy as any and I would focus on the design, and leave the structure alone for now, as that should free up your creative energy to design what you want free from structural restraints. Then when you get what you want design wise, see if it can be built and how much extra it might cost to stick with your design versus making some changes to save on the budget. This strategy allows for much more freedom in the design process and one I employ a lot. Others will surely disagree and think that the structure should be considered during the design phase but I find that it just gets in the way and almost any design can be built as long as you are willing to write large enough checks. -
Lumber size restrictions and ridge board/beam
HumbleChief replied to RyanDe's topic in General Q & A
I'm curious Ryan, are you building a house for yourself? What is your overall plan? Your knowledge seems to be very limited and your experience as well but I don't want assume such things without knowing what your overall plan is. To answer your question more directly, exposed beams will effect the overall structure and load/framing if they are engineered to do so but they don't have to. You can also install exposed beams that have very little to no effect on the load/structure as well but again it's an engineering question as much as a design question and very difficult to answer in any definitive manner on this forum. -
Lumber size restrictions and ridge board/beam
HumbleChief replied to RyanDe's topic in General Q & A
Both the rafter sizes and ridge board/beam size can be specified in Chief's roof framing dbx. Make sure auto roof framing is turned on and you can change sizes in the roof framing dbx. The rafter depth is hidden in the structure dbx and the width specified below. The ridge is spec'd separately. Sizing them is another question but once you know the sizes you can tell Chief (not the other way around) what size to make those members in that roof framing dbx. -
Need Help With Simple Floor Heights - Again....
HumbleChief replied to HumbleChief's topic in General Q & A
THANK YOU DAVID!!! Sadly the paradigm still eludes me... -
To continue my string of embarrassing posts I am still struggling to understand Chief's structure dbx and cannot figure out this latest behavior. I am trying to lower the floor of the garage to -12" but it seems to lower the floors on all the other rooms. I've never seen this before and am wondering what simple setting I am missing? Is Chief 'remembering' a setting somehow? How can changing the floor height in one room change all the other floor heights? Is that expected behavior? FLOOR HEIGHTS.plan
-
Yes Lew, good explanation and I think I've unwittingly benefited from the behavior you're describing but just never really understood it.
-
Here's another explanation of the (beneficial in my opinion) behavior from Tech support. The reason, simply put: the program remembers various room settings. As stated, these settings can be flushed, for example, by deleting the Foundation and starting over -- deleting the Foundation floor with Auto Rebuild on will not just clear the foundation floor, but delete the entire Floor 0, which is what is necessary to wipe all of this remembered information, saving and closing the plan is necessary to completely flush this type of information as well. This behavior can be seen anywhere a room is defined and is typically going to help you even though it's not apparent at the time. The intent is to remember and save data about how the rooms are defined in the event that the room definition is lost, the user won't have to waste time redefining a room because they accidentally disconnected a wall, etc. Knowing how and why it works, you can force it with expected results. For instance, if you start a brand new plan and draw a room, bisect it with an interior wall, set one room to Living and one to Family, drop the family room's Floor © value to -6", then delete the interior wall--the area will be defined by whichever room was larger, either Living or Family, and take on the settings of that room. Now, redraw the Interior wall and you will see the Living and Family rooms will be redefined as they previously were, the Living at 0" and the Family at -6". In this specific plan, the information that is being retained is actually the Floor 1 Room's "Monolithic Slab Foundation" setting, also forcing the Floor Supplied by Foundation Room Below to be set. On Floor 1, if you open the middle room, uncheck "Floor Supplied by the Foundation Room Below" and "Monolithic Slab Foundation", then delete and redraw the room, the foundation will regenerate with default stem walls. So, in this case it's not so much remembering the Foundation, but the room above's Floor settings.
-
Again a huge thanks for responding Dermot and I don't think there's anything inherently wrong with the way Chief is designed to work and it actually might be a GREAT feature - it's just not that clear to the user how that design is implemented. If I and all Chief users knew Chief was designed that way there would be no question nor any thread regarding same and I really can't think of a good way to even describe the behavior let alone define in such a way that a user manual definition would really make sense. Bottom line, I learned a little more about Chief and how it works and hope this thread helps spread some of that knowledge around. Again thanks for participating, it's not a small thing and it does not go unnoticed.
-
Yes I could do that (EDIT: did that and it works as it should) but still...shouldn't one expect new rooms, no matter where you draw them, be to drawn to floor/foundation defaults?
-
Yes that is how it works - but should it work that way? Shouldn't a user expect that if the defaults are changed that any new room would build to those defaults? And what is 'remembered'? And for how long? And in what areas? How can one know that some area of a plan will draw to defaults while others won't? That is very baffling behavior. And now that I know this I don't have to spend all the time I already spent re-building my template plan.
-
Tried it and I'm going to say yes it fixed it, even though I can't be sure I built over the exact same area, I tried a couple areas and the foundation built correctly after deleting the walls and closing/reopening the file. Still unexpected to my mind and has to drive a new user crazy when defaults simply stop working because Chief is 'remembering' something that no user could possibly be aware of.
-
Here's the phenomenon I was describing Dermot.
-
REALLY appreciate you taking the time to explain Dermot. I have noticed the behavior you are describing and usually find it to be not too confusing but I had a plan that would keep drawing new rooms to old room settings despite the default setting changes. If one moved off that old room area, which now had no walls, the rooms would draw to the defaults, but if new walls were drawn over that old room area the room would be drawn to the last known room spec and not the defaults. I'll spend a little time with that plan and see if I can confirm that behavior and maybe send it into tech to see if that's expected behavior - or not.
-
Yeah great question Glenn. If there are rules for such behavior I would also love to know what they are to add some consistency and alleviate some confusion. I was always under the impression that any time you added a new space that the new space would conform to the defaults and not 'remember' any other previous settings. If Chief does remember old settings why and in what circumstances?
-
I've never heard a story like SRC's and have no reason to not trust his/her version. I also haven't used a Mac in years so can't comment first hand. Both Macs and Windows machines seem to be fine for most users and I like the ability to customize a Windows machine, others do not. I rather value my hard earned cash and find there's no need to spend more on a Mac where, for me, there's no added value. Others like the culture and one company attitude and its perceived benefits, me I run from Apple for just that reason. Can you compare apples to apples with the 2 system approaches? Difficult, but generally you get more bang for your buck with a Windows machine and Chief does indeed require lots of bang.
-
.. same here but so hard to really document in a way that the Chief guys can fix and if the fall back is to just create a new plan each time that defeats a lot of the inherent power within Chief. I will also bet it's almost always 'user error' but a program should not be so complex that errors are the norm from a very experienced user such as myself, unless I really am as stupid as Chief can make me look/feel.
-
Yes and I always ignored it - till now.
-
Thanks Perry - that helped 'a little' but still unusable for any kind of accurate framing detail. I'll just take care of it manually.
-
I am working on a plan where the defaults are constantly changing in the room dbx. Numbers that seem to come out of nowhere and certainly not the defaults I have set. Take a LOT of work to get everything to play nicely. Match properties is the only solution many times.
-
Thanks Chop (love your avatar BTW) it's not that big a deal to manually do it all but was just wondering if there was something I was missing.
-
I don't use the wall framing details very often but have a condition I would like to show but Chief isn't framing that wall in a way that seems usable. As can seen in the attached pic there's all kinds of strange anomalies - header is weird; no trimmers; sill come up short etc. Is there a setting I should know about that will give a more accurate detail? Or does one just move stuff around manually? Here's the plan; WALL FRAMING 1.plan