Alaskan_Son

Members
  • Posts

    12268
  • Joined

Everything posted by Alaskan_Son

  1. Create 5 side by side windows that are all the same height (height of the center unit). Group select the windows and block them. Give the Mulled unit an Arch (Broken Arch) Adjust as necessary.
  2. Yeah, on that note, unfortunately 3D view columns are the one area where Chief doesn't recognize unique attributes. There has to be something different in the text. I would recommend sending in a complaint/suggestion on this if you want to see this behavior changed.
  3. In addition to the option @robdyck gave you, you can also leave Group Similar Objects checked and force the items onto individual rows by making something unique about them. The thing to understand is that schedules group items that are identical based on what is being displayed in the schedule. Here's a simple example: Standard schedule with items grouped: ...and here's what happens if I remove the width column: So, if you want to force certain items from not grouping together, make sure to include a column that is reporting some unique attribute for the desired object(s). This may be a Room column, a Label column, a Description column, or, it can even be as simple as using the Comments column and adding a unique column. In this example, all I did was add a single space to the Comment field for one of my 12" wide cabinets:
  4. This should be moved to General Q&A, but all you need to do is toggle your "Patterns, 3D Views" layer in that specific layer set.
  5. 3 Things: You need to have both the object layer and the label layer turned on in your new layer set. Turning the object off also turns off the label. The label you're currently seeing is probably the label from the layer set below. While we're on that subject... I failed to mention this in my first post, but you should probably turn off the cabinet labels in the layer set below. Uncheck XOR in your new referenced floor.
  6. There's another option that can work quite well but that can be tedious to initially set up. That is, use your Reference Display. Here are the basic: Decide which objects need their labels moved forward. Create a new Layer Set that has only those objects and their labels turned on, and set the line style for all those objects to the Invisible line style. Use the Reference Display settings for your current Plan View to add a new Reference Display to the TOP of the stack using that new Layer Set. Set it to use the same floor you are already trying to display, and make sure both Details and XOR are toggled OFF. This will place all your desired labels in the top drawing group without displaying any additional lines or fills for the related objects. Here's a quick example where I have a header label obscured by joists above. In this case, I couldn't relocate the label because I want to leave automatic framing turned on, and even if I could have, the direction of the joists above would still be obscuring it...
  7. Never seen anything like what you're describing. The only thing that comes to mind is that it sounds like you may be inadvertently working with multiple plan files.
  8. If you're using a closed polyline, then %length% will not be an option. As @DBCooperalready stated though, you can use %perimeter%. The problem though is that you're going to get the entire perimeter of the polyline and not necessarily the length of the pipe that the polyline is supposed to be representing. Assuming though that your "pipe" is a specific width and that and that its a pretty consistent width closed on both ends, then you should be able to use something like the following: %((perimeter.round-8.in)/2).to_s("\'-\"")% ...where the number 8 is just double the width of the "pipe"... NOTE: I rounded the perimeter value just to avoid a more complex fractional inch value macro but this should work for a basic length. Just make sure to replace the number to reflect the actual width of your pipe. If you need anything more complex or need things tweaked further, please feel feel to reach out. I do offer consultation services for this exact type of thing.
  9. That behavior is controlled by the Text Style being used for your North Pointer's Layer. Edit the Text Style so that it is set to Rotate with Plan. If you need that setting unchecked for something else, then create a NEW Text Style and set it to Rotate with Plan.
  10. I have my own systems for creating custom project information "fields". Information is all entered in a single location in the plan or layout file, custom fields can be created on the fly, and I don't use globals anymore. That being said, I'm a little curious why more people don't just use plain old non-evaluated text macros. Its a very very easy way to create custom fields that can be exported/imported as well.
  11. Control+Tab followed by Enter is a good alternative.
  12. honestly, the best method is to avoid using this forum unless absolutely necessary, and just stick to the Home Designer forum.
  13. Use the HomeTalk forum instead… https://hometalk.chiefarchitect.com
  14. Me! Joking Okay, Not joking ... Its tricky because you have to use both Ruby (programming language) and Chief which are 2 entirely different and separate constructs. You can use any number of online resources to learn how to program in Ruby including the actual Ruby documentation, the StackOverflow forum, and even ChatGPT... ...But then you also have to learn how to use the various tools that Chief has given us to work with. This is where it gets tricky. There is a lot of nuance and interplay between the 2. We have certain information in Chief that we can access and parse, various ways to access and parse that information, and some (but not all) of those ways can optionally use Ruby. Chief has quite a bit in its documentation about built in name:value pairs, special built in Classes and Methods, and other text macro stuff, but has very little about actual Ruby programming (and rightfully so). If you're serious about custom macros and otherwise using Ruby to access and parse information in Chief, it is well worth the effort to pay for an hour or 3 of consultation/training time. You'll save yourself many hours...days..even weeks of otherwise unnecessary experimentation.
  15. Use a simple Ternary Operator: %height > width ? height : width% ...or put into an Array and use the max method: %[height, width].max%
  16. Yeah, I don't get it. It seems like it would be an easy thing for Chief to just make the calculation conversion internally, but clearly its not that simple or I know they would have done it already.
  17. It was a totally serious question and you seemed to acknowledge its legitimacy in your last post where you seemingly admit that its a problem. Just like me, I'm sure you have seen countless examples of AI changing crucial details (not only in renderings but also in simple text). People gush about how great the results are and many times don't even realize the extent to which the end result has been changed. And when you mentioned "(altered architecture)" it was proceeding "heavy demand time" so I assumed it was a catchall phrase for the level of service you were using and could include material changes, landscape changes, trim details, and so on. Again, I really and truly was just curious if you care that AI changes things because you stated... It's a hard pass for me though. It's 90% cool, but that remaining 10% is a deal breaker. It's not a useful rendering in my opinion unless its accurate and in just about every single example I've seen to date AI does something either structurally or with lighting that I think would be a disservice to my clients no matter how pretty it looks.
  18. Yes. That is what happens if you bring objects over from imperial plans into metric plans. Feels like it shouldn’t be necessary.
  19. ...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.
  20. 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.
  21. 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.
  22. Do you not care that Chat GPT completely changed your house?
  23. 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.