HumbleChief

Members
  • Posts

    6103
  • Joined

  • Last visited

Everything posted by HumbleChief

  1. I thought I posted something else in this thread but it got lost. Mark, I could not get this technique to work. I only got wider front filler pieces but nothing that filled all the way back like a panel.
  2. Of course one could always place a couple of slabs (or cabinets that behave like slabs) next to a cabinet and always appreciate any input but I was looking for a way to create a waterfall counter using just a single entity, much more flexible and adjustable IMO.
  3. Thanks Mark With your plan how would you get 2" sides?
  4. Mark how do you get the bottom piece to go away?
  5. Thanks Kevin, I've always used p-solids as well but hate chasing 3 parts around, size resize etc. Found a way to do it with cabinets, is there a better way?
  6. Would like to create one using a cabinet, can it be done? Slabs is easy but would like to use a cabinet if possible? Or best method perhaps?
  7. Can you create a room where the stoop is and have the floor of that room stop the foundation wall from extending up? Post the plan for better help.
  8. This is good advice though within that search hopefully you will discover why Xeons are not necessarily good for running Chief and in some cases down right bad. I have a dual Xeon system and would not go that route again.
  9. In my opinion those 3 systems represent exactly what you get for your money these days, which each increase in cost you get that much more power. Do you need a fast computer for Chief? Do you build large models? If so and you can afford the last one it has the best components and should run Chief really well and is also a good price for what you get. I wouldn't worry about 'name brands' or whether or not someone else has heard of them as they are probably using the same components anyway.
  10. I shut Chief down and re-booted my computer and everything is back to normal. Just one of those weirds I guess. Thanks for the replies
  11. Thanks Eric, but what happened? And why should one have to do that? I can always just replace the slab which is essentially what you suggesting but why? There's a couple of buggy things I've encountered with this new release but that doesn't lessen my appreciation for your help and time. thanks again.
  12. Not sure what's happening here but I can't delete certain items and now I can't select a hole in a slab in order to delete it. If I insert a new hole I can select and delete it but not the other hole. I can replace the slab easily enough but am just wondering what I'm missing? Anyone else experiencing this? Attached plan. hole_in_slab.plan
  13. Seems like I can turn off the display of the elevation and section cameras then delete items, turn the display back on then use the elevation camera I need to create my symbol. Did Chief always work this way? Could have sworn I could simply delete every thing, including cameras with a simple warning that could be ignored.
  14. When creating a new symbol I open my template plan, create an elevation to build the symbol, then delete all the other items to save my new symbol. This morning I created my symbol went to delete all other items and I can't delete the elevation/section cameras and can't group select anything if the cameras are included. Something simple? Weird, seems as though I've done this a thousand times. Something with my Layer Sets? Nothing is locked. Weird. As long as I group select items WITHOUT including the elevation/section cameras they will delete but instead of a previous warning about deleting the camera views they simply will not delete. Gotta be something simple. Any help GREATLY appreciated. My template plan is below. TEMPLATE_4_26_17_AS_BUILT.plan
  15. Thanks again for some clarification Glenn. It's a great help.
  16. I'm sure this has been suggested before but I found this tip from Glenn Woodward to somehow make sense to me suddenly. I hope it helps others and any tips regarding same MUCH appreciated.
  17. Yeah I'm seeing some great possibilities with this technique. I tried it on a test plan and was amazed to see how Chief actually works - graphically - nice tip. Maybe post that in the tips and techniques section? I think it is worthy and thanks again. I'm posting a vid in the Tips and Techniques section. If anyone wants to elaborate or correct my interpretation - more than welcome.
  18. That's a great tip Glenn. BTW it doesn't work with a back clipped cross section but the visual is very helpful.
  19. Yusuf, your posts and your attitude on this forum are very refreshing and I appreciate them and your great energy very much. Having said that the fact that you just posted 3 or 4 paragraphs on how to think of Chief and the way it works 'logically' more than makes my point. There's a logic to Chief no doubt, but one that does not come to hand immediately - it has to be learned which may make it 'logical' to some and crazy making to others. I am firmly in the latter camp. I always built from the bottom up and took that 'logic' to Chief and was thoroughly trounced by Chief's alternative 'logic'. I thought the 'logic' that the ceiling structure of floor 1 would have an effect on the ceiling framing of floor one on a 2 story building and was once again trounced by Chief's 'logic'. So is Chief's version of creating structures 'logical'? Of course it is - to the designers of the software. But that may or may not translate to the user or the user interface and in Chief's case I think they missed the UI boat in many cases. Remember these are the same folks who gave us a new feature of poly line area labels that resolved to 7 decimal places - making it completely useless - as a new feature no less (remains the same to this day BTW). Perhaps that same 'logic' is placed in too many places in Chief's UI or I just don't get Chief's version of logic. Had another thought. If the way you've explained Chief's paradigm is indeed 'correct', knowing 'correct' is quite a subjective term, then where is this clear explanation of how Chief's structure dialog box should be viewed in Chief's literature and or training videos? Or even the structure dbx itself? There are many users who don't understand it and many that do but the 'logic' you present is not part of Chief's training or instruction - and should be IMO.