Alaskan_Son

Members
  • Posts

    12005
  • Joined

Everything posted by Alaskan_Son

  1. Click on the Layer tab and adjust the Drawing Group or use the View Draw Order Edit Tools in your Edit toolbar.
  2. No problem. Depending on your processor speed and on what macro recording software you use, you might need to adjust the delay between keystrokes.
  3. There isn't one. You need to use multiple commands (via hotkeys or mouse clicks). You can either manually do these in sequence or record a macro and assign it to a hotkey. There are multiple routes you could take, but I would probably suggest just assigning hotkeys and using those in the following sequence: Layer Display Options hotkey Shift+Tab (should put you into the Name Filter field) Type out the words "roof planes" (should filter the list) Tab (should move to the selected layer) Spacebar (should highlight the layer if it isn't already) Tab, tab, tab, tab (should activate the Display checkbox) Spacebar (should toggle the Display setting) Enter (should close out the dialog)
  4. Select the Cabinet and then click on the Open Symbol tool. You can adjust the height using the Z Position offset. I would make sure that you haven't done something weird with your cabinet or countertop settings first though.
  5. I have this happen all the time when sending as Plot Lines. I keep forgetting to report it. I always just delete them. I'll report it right now. You should as well.
  6. I haven't actually seen your plan file and it may or may not make any difference in there depending on your various settings, but ceilings planes can and often do cause walls to frame entirely differently.
  7. I think you're trying to repurpose the X/Y offsets for something they really shouldn't be used for. What we really need is some more refined bounding box control if anything. In the meantime, I suggest you reset your offsets and maybe try one of these options instead: Add a super small object to your symbol. This can be a very very tiny Face even that gets placed on the floor and that will be essentially invisible in all views. Add something to the symbol that may actually serve for increasing accuracy (Range ----> anti-tip bracket, Toilet ----> waterline, Dryer ----> Ducting, etc.) Place your symbol in an Architectural Block and just add a molding polyline to the back of the block that doesn't have a molding assigned. You could alternatively continue to use the offset along with a Custom CAD Block that creates the offset using a text box so it doesn't show up anywhere like I've done with this dryer example: Dryer with offset.calibz
  8. Think about it like this: Chief normally build walls till they hit a ceiling or roof plane above right? So what happens when you uncheck Flat Ceiling Over This Room? Chief will build the wall up till it finds either a ceiling or roof plane. This is the reason that I believe Chief states that "The Baseline of a ceiling plane should be drawn along the outer surface of the bearing wall’s Main Layer." Admittedly, I draw ceiling planes inside the wall all the time, but if you want the behavior you desire, just model as Chief suggests and I think you'll be happier with the results.
  9. From the looks of your screenshot, I would say that the source of your problem is those double walls. You have created a scenario where you have one large exterior room enveloping the entire plan because, although it might be very very narrow, it continues between those double walls. Try setting ONE of the walls at each of those double wall instances to a furred wall and see if that fixes your problem. Or, you could optionally set one of those walls to no room definition. There are other solutions as well but try those three on for size.
  10. Your conditional statements are what causes one thing to supersede another. In this example, you're using what's called a ternary operator which consists of 3 parts separated by a question mark and a colon (condition ? value if truthy : value if falsey), and you're testing to see if referenced has any truthy value. If it does, your obj variable is defined as referenced throughout the rest of your code. That's it. You've created a fork in the road and have decided to head down the referenced path.
  11. I know it might sound like a pain, but at this point, just consider producing you prints in 3 steps: 1. Print your set minus the page or pages that need rotated elevations. 2. Rotate everything on your Template Page or Page 0 (including the Drawing Sheet) to accommodate the rotated elevation page(s) and print just those pages. 3. Combine pages in PDF editor.
  12. Can you just rotate EVERYTHING else and print portrait instead of landscape?
  13. You get a lot more than just upgrades with SSA, plus, no one says you need SSA to upgrade. There's no reason you can't just wait till they release new versions and then pay the upgrade fee at that time.
  14. Here's one I threw together for you on the house. The material definitions could probably use some work though. Rustic Wine Barrel Sink (block).calibz NOTE: I made a couple very minor improvements to the materials and edited this post to replace the one piece library symbol with a block that includes the separated countertop and sink so you can easily adjust those as desired.
  15. Yes and no. Can be done in layout by sending multiple cropped views of a single column text box. Or in plan by using multiple text boxes and custom macros. There’s no built in function that will do this automatically in Chief though.
  16. I'm not so sure I understand what you're talking about. Can you show an example? Is it the columns you're having trouble with, the bullets, or both?
  17. I'm not so sure this would address the issue being discussed. We can already control which pages get printed in the Print dialog and as has already been mentioned we can also exclude pages by setting to Use as Page Template. What I think we really need is a Make Page Inactive checkbox that essentially just causes Chief to ignore the page entirely without breaking its link to the proper Template. Ideally this would be available on Right Click from the Project Browser as well.
  18. I can confirm that there is a problem with the sand pattern. That pattern seems to be comprised of nothing more than single points (no lines) and Chief seems to be unable to properly process that point data in Live Views. Use a different pattern or use Plot Lines.
  19. I could probably write you a custom macros for this purpose, but there are a couple easier options. @Michael_Gia already mentioned one of them when he said... Another much easier option is to simply place the desired numbers of pages manually. Yes, its an extra step, but its pretty easy to just enter the number you want instead of jumping through all the hoops required for other methods.
  20. You seem to have very little appreciation for anyone's time other than your own and for some reason you found it appropriate to highlight that fact right off the bat. That's not a good look for someone asking for help. It would take you all of a few seconds to update your signature so we know what version you're using, but you choose not to because your time is apparently too valuable? I suggest you dial the attitude back a little bit and consider that our time is valuable as well. Commonly the best answer depends on which program version a person is using. You're actually doing everyone (yourself included) a disservice by not taking a few seconds to update your signature with the appropriate Chief version.
  21. for a 6" solid line just put 3 dashes that are 2" long with a Spacing of zero.
  22. You should only get the number of printed pages as long as your remaining pages are empty. Do you have objects placed onto your extra pages?
  23. What you just described is making a mess of your hotkeys. The Delete Objects tool is an entirely different tool than Delete or Backspace and the 2 shouldn't be confused. The hotkey assignments you showed in your first post were correct and you really shouldn't have changed them. I really recommend you call tech support and try to get to the bottom of what was causing your original problem because I don't think it had anything to do with your hotkeys.