Alaskan_Son

Members
  • Posts

    12236
  • Joined

Everything posted by Alaskan_Son

  1. Yes. That is what happens if you bring objects over from imperial plans into metric plans. Feels like it shouldn’t be necessary.
  2. ...or just open up the camera and uncheck Clip to Room. If you set up the camera as a Wall Elevation, it will automatically clip the sides, bottom, top for you (Clip Plane) and it will Clip to Room which cuts off the view of anything beyond the defined room. You can take advantage of the automatic Clip Plane behavior and just forgo the one Room clipping behavior though by unchecking the aforementioned setting.
  3. Not sure man. I think you might just have to turn on all your layers in a 3D view and start group selecting anything that didn't move with the room.
  4. I guess maybe I've never personally had to import settings between plans with different units. I just assumed it would work like any other plan. You're right though, Default Settings don't seem to carry over. Now that I think about though, I guess it makes sense that Importing Defaults from a plan with different Units may be problematic (although I feel like Chief should be able to make conversions internally so that this type of thing is possible). That being said, you can still Import: Saved Plan Views Layer Sets Default Sets (at least anything not store with Imperial Units) Wall Types Note Types I tested in X17 and it appears to let you Import EVERYTHING but in doing some quick additional tests just now it does look like the Default settings (at least any that I noticed) don't actually carry over. There's no message to say that they don't, but they don't. I guess maybe just Import what you can, and adjust the rest.
  5. Do you not care that Chat GPT completely changed your house?
  6. Rich Text has a number of benefits over Standard or Simple Text including but not limited to: The ability to have multiple colors, formatting options, alignment options, and text sizes in a single text box. The ability to have some sections of the text be all UPPERCASE and other sections in the same box be Standard Case. The ability mix and match Line Spacing and Margin settings in a single text box The ability to use various Bullet styles along with optional Number Prefixes and Suffixes The ability to insert one or more clickable hyperlinks Standard or Simple Text on the other hand has several benefits of its own including: The ability to create adjustable tab stops or rows The ability to display gridlines The ability to create a single link that can be accessed through the edit tools Perhaps most importantly, the ability to dynamically control your text by either layer or by text style My suggestion is to use the one that makes the most sense for the situation, but but BUT, if you're not sure and don't specifically need a Rich Text feature, use standard Text. Standard Text will give you more options that you're likely to want in the future (namely the ones mentioned in the last bullet point) plus you can always convert Text to Rich Text. You cannot simply do the inverse and convert Rich Text to Text.
  7. Ya, it's definitely best to start with a metric plan if possible. I think the best approach is to just open an empty metric template and Import all your various settings as desired. Chief made this a lot easier in X17 but could still be done in X16. That being said, the problem you're seeing is actually due to a limitation Chief has with cabinets in Imperial plans. I've never been 100% sure why, but cabinets (and by extension shelves) are one of a very small handful of items that Chief limits to specific increments (in this case 1/16"). Most items can be set to a much more exact dimension without issue. Try this quick experiment in an Imperial plan to see what I mean: Draw a couple otherwise identical shelves using both the Shelf tool and a 3D Solid and enter "50mm" as the thickness for both. Dimension each of the 2 "shelves". You should see that the Solid will show 50mm and that the Shelf will show 49.21mm Now open the dialogs for your 2 objects one at a time. If your change your Number Style to Decimal Inches, you should see that although they both displayed 1 5/16", that they do in fact store more accurate values when Chief allows it (which they do for almost everything). In the case of Cabinets though, Chief just happens to limit them to 1/16" increments. Again, I'm not 100% sure why but I wish they didn't.
  8. I've designed and otherwise helped set up a few different alternatives to the Project Information system that allow for the addition of as many project info. line items as you'd like. Some are macro based, and some are not. I'd be happy to help set you up with something as well if you'd like. Just email me at alaskansons@gmail.com if you'd like to discuss further. That being said, one of the easiest OOB solutions is to simply add your Assessor Parcel Number as a custom, non-evaluated, user-defined Text Macro via Text Macro Management. See example below where I have created an %APN% macro... P.S. This should be in the General Q&A section.
  9. And the Match Properties tool is yet another good option.
  10. Looks like a faulty font. Exactly which font is that and where did you get it? I know you said sans seriff, but that's just a generic term for fonts without fancy tails coming off the ends of the strokes There are a few that have leading issues like that, but that is one of the worst I've seen. I would definitely just fine a different font.
  11. I agree with almost all of what you said. All except that last sentence. Believe me, Chief is fully aware of the need for collaboration between multiple machines. I'm about 99.99% certain that one of main reasons (if not the main reason) for implementing Project Management in the first place was so that they could address some of these collaboration issues, more specifically with the goal of a managed cloud store so you eventually wouldn't have to import/export anything at all.
  12. That all sounds reasonable. What seems odd to me though is that it sounds like you're essentially attempting to display the North Arrow angle in Quadrant Bearings, but that will only ever be N0°W (or N0°E). It would seem that the text alone would suffice and that placing any extra lines or macros would be totally unnecessary. Am I missing something?
  13. There's not simple one line method to do this, but can definitely be done with a custom macro and I can help set that up for you if you'd like. That being said, I would definitely need more information about what you're trying to accomplish though because quadrant bearings are defined according to North and so that angle you're trying to display should always simply be N0°W no matter what angle the line is at.
  14. 3D>Camera View Options>Cross Section Slider
  15. Ben is correct. It seems that you are trying to accomplish something that is a mathematical impossibility. The only way to have the same fascia height, the same overhang, and the same plate height (ALL 3) while at the same time have different pitches would be to use trusses and make the heel height taller on one section or the other. With rafters its simply impossible.
  16. Next time, just draw the object right in elevation view where it goes.
  17. I don't believe there is any way to set a default for this. I've actually meant to send in this request myself. I think about it almost every time I change that setting but naturally, I'm always in the middle of something and forget to write it down. I'm gonna send it in right now actually. You should as well.
  18. I have macros that do this. Away from my computer but shoot me over an email if you want to discuss furtter and I’ll see what I can do for you when I get back to the office.
  19. FWIW, you can also optionally set the callout size in your schedule to zero but this will keep all the schedule number text upright instead of rotating it along with your window.
  20. It took me a while to understand your problem. I think I finally get it. What you want is for Chief to read your mind. Okay, kinda joking, but not really. There are essentially 2 things you could be doing with the Priority settings right now: Prioritizing pre-cut studs in which case Chief will cut your trimmers AND cripples from studs Prioritizing plate material in which case Chief will cut your trimmers AND cripples from plate I think what you probably want is a Structural Member Reporting Priority list for each and every framing member type. Cut cripples from this, cut trimmers from this, cut sills from this, and so on.
  21. Ya, I guess we should have clarified whether we were talking about a camera or a manually placed callout because the 2 are definitely different. I had been assuming we were talking about a camera, particularly because the callout arrow solution is relatively self evident. My assumption could have been wrong though.
  22. As Rene suggested, I do indeed have some custom systems I've set up to do exactly this. That being said, Chief also has some built in non-macro based tools to do what you want as well. For example, you can navigate to the Labels tab for your schedule, set to Use Both Callout and Label, and then simply toggle the callout layer off for most layer sets, but in your schedule layer set, toggle the callout layer on and toggle the normal label layer off.
  23. It’s still not clear to me what you are trying to accomplish. Are you wanting those arrows pointing in the opposite direction from what the camera is facing, or do you simply want them pointing left. There is a big difference. Currently the arrows point in the direction that the camera is facing, which makes perfect sense. I’m not sure why you would want them pointing in the opposite direction but if you wanted to do that, I imagine you could just change all cameras to use a custom arrow block pointing in the wrong direction. If your goal though is to actually face the camera in the opposite direction, then you have to set up a new camera facing that way. if however, your goal is to have ALL arrows pointing to the left regardless of which direction the camera is facing then you will have to individually change the arrow for each and every right facing camera on a case by case basis.
  24. Are you saying that you want the arrow pointed in the opposite direction to what the camera is facing?