johnny

Members
  • Posts

    2803
  • Joined

  • Last visited

Everything posted by johnny

  1. I personally think the line has a "z" coordinate if drawn in elevation or section. In other apps I use a line is a line in 3D space no matter what view. Overall this alone isnt a huge deal though as others mentioned.
  2. I agree - it should be Z, but regardless Chief should have it consistent. This is my point Larry -
  3. ...it should be odd that Chief isn't consistent with itself, and that should be an obvious problem. To move that same line with the move tool one uses the "Z" coordinate, and yet its the "Y" coordinate in the line specification Dbx - all in the same view. AND we are talking about all known apps i've used that keep X/Y/Z movement standard. Live sections are not 2d. If it was as simple as this one feature (or even a handful of features) then it wouldn't be a big deal. Unfortunately this app is plagued by oddities in which the sum of those oddities do become a big deal. I see similar posts all the time by you about these issues.
  4. Yeah I am realizing that with Chief...which is kinda odd since other apps you move items in 3D space no matter your view orientation (like Sketchup you have global X/Y/Z in all views represented by colors). In Chief if you set a 2D view of your 3d model its as if the X/Y for 2d only. However, there is an inconsistency with Chief in this regard. If you have the same line you are using the "Y" to get your "Z" value, but then you go to do a "move" operation, you must insert a "Z" value and NOT a "Y" value to move along that axis. So in one window the line is set by the "Y" value and the other you move it via the "Z" value.
  5. Psolids and other objects that have options to relative or absolute elevation settings.
  6. More than one way to skin a cat (odd expression). There are several ways to mitigate placing a notch in a stringer - Simpson strong tie etc to reinforce the notched section. It will require a letter from an engineer most likely for you to do something like that. You might even get away with sistering dimensional lumber to fix- but depends what your conditions are. ...but as Michael and Alan said its just notching the stringer is a bad idea.
  7. If you want the more detailed version you can simply copy and past on top of the wall section and extend or retract the area you need to fit. However, if you are printing that section 1/2" scale or below its probably not worth it.
  8. You may be seeking Chief to "frame" that detail, but there is no way I know to frame it correctly in Chief unless you manually place framing members. A pony wall method would only give you a different wall thickness in that area, when in fact that framing is typically added once the wall is framed. Personally, id use a material region. I love that tool, and it breaks the siding layer of the main wall.
  9. Is there a way to set my default plan so that certain things are absolute?
  10. Interesting. Yes, it shows the Psolid @ 121 3/4" - which seems correct. This led me to see that there is a floor elevation ref, and changing to absolute works. However, that makes little sense since my floor is set to 2x10 joists etc etc...so that number is just all together wrong. Got it working though.
  11. Ill add the fact I realize I can move the line using the Y value, but why doesn't that value match the the poly solid value for "z"???? This makes no sense to me.
  12. I've seen scott use normal lines in section to get the Z height of the line. However, all it lists is the X/Y in any of the data options. I thought perhaps Y was the actual "Z" but that doesn't seem to be the case since I placed a poly solid next to the line at the exact same Y value and it comes up short. Is there some other value I should be using? In Vectorworks everything drawn with "Z" value actually simply lists the "Z" value, so I am stumped how Chief is displaying the values.
  13. ^^^^this. its crazy since it would probably take all of 2 min. to fix for them.
  14. What is on the other side of the glass? Lake, forest, city, suburbia, territorial big sky? Each one of those exteriors demands a different glass setting. If its water/lake then your glass starts too far up the wall, if its forest its too narrow, if its city or suburbia you may be ok depending on surrounding home locations, if its territorial then you want to capture the horizontal view with the sky (so high is good).
  15. I guess I don't understand the aversion to labeling this as a bug. Is Chief acting as the programmers intended? Great workaround by Glenn but I'd say it's a workaround for a bug that needs to be fixed.
  16. Interesting that even if you place a material region over that wall section the problem remains.
  17. Isn't this a bug? The visual dosn't match the model info - as those gaps are not showing on the isolated wall segments. Its a connection issue...Chief's #1 problem.
  18. To correct I: 1. Made sure all the property walls were "no locate" (yard walls). 2. Turned off "full gable wall" from the wall with the fireplace. Worked. Here is a vid.
  19. I'd agree with you if Annosets weren't king...but since they are I find I have to use those primarily for other purposes unless I want to have a million different sets. My problem is that I work with several draftsman and so I try and keep the files as basic as possible. perhaps I am not dong something right then...since the wouldn't I then have to have a duplicate annoset for each dimension setting I wanted?
  20. Thanks everyone - I guess in plot plan view the size of those markers exploded. I use point-2-point often...im not a fan of having to go back and forth on settings inside my dimension tools on what I want to dimension, and to what point. I can't leave everything on and changing that setting all the time is more effort than pt-2-pt i've found.
  21. Can someone help me locate the settings that govern the tail length for dimensions? I've tried everything in the areas I would imagine...