Alaskan_Son

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.

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:

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.

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.

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...

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.

Its in the General Plan Defaults now

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.

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.

I agree. This functionality would be awesome.

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.

Control+Tab followed by Enter is a good alternative.

honestly, the best method is to avoid using this forum unless absolutely necessary, and just stick to the Home Designer forum.

Use the HomeTalk forum instead… https://hometalk.chiefarchitect.com

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.