Joe_Carrick

OIP fields are text automatically. If you want to get their numerical value you need to do that in your macros.

That's as bad as watchin a Tennis Match sitting on the sideline.

By making the leader line connect to an object within the room it will work

No, but I have determined that you are correct that the leader needs to connect to an object rather than the room. Even a very small solid will work but a fixture, cabinet or piece of furniture would be easier. Material Regions don't work. IMO, connecting to the room should work

Michael, Can you post a macro that works under those conditions?

1. Place a RTB outside of the exterior wall and add a leader line to a room. 2. Insert a user macro in the RTB that references a room attribute such as: room.schedule_number I don't get any result. When I put the RTB inside the room it works.

Note that it won't work with a referenced (leader line) condition. I need to report that.

I just discovered that the room attributes are not available with Rich Text when a Leader is being used. IOW, referenced macros don't get the room data.

Yep, In fact it's now possible to have a macro that creates a vertical schedule for an individual room. ie: one column and multiple rows. This is something I asked for several years ago. CA still hasn't provided that directly but with this new functionality we can essentially do it ourselves. The key is that we now have access to all the room attributes in user macros vs the limited set CA provided in the object macros.

Attached is a macro that when placed in a Rich Text Box creates a Room Label consisting of the Floor, Room Number & Room Name. Example: 101 - ENTRY 102 - LIVING 103 - DINING 201 - MASTER BEDROOM ETC. Enjoy room_num_name.json

None that you are using - at least not at this point. I did find a problem with my X10 Wall Legend macro which I've re-written for X11. The X10 macro basically locked Chief requiring an "End Task". If you see this type of behavior anyplace let me know.

Don't hold your breath. It's not on my priority list.

I'm not sure yet but I think I'll be able to put together a Note Schedule that contains the results of macros referencing Room Attributes in the custom fields of the Notes. It may or may not be worth the effort.

I'm not saying a lot about X11 - but I'm grinning a lot because so many of the new features are things I've been asking for. The one thing I really wanted was an OIP for ROOMS and FRAMING OBJECTS. Maybe they'll still be able to get those in for the final release. If not then I really hope they get them in X12. I've had to do some revisions to some macros for X11 but the results are superior. I had one macro that worked nicely in X10 but brings X11 to a virtual standstill. I still haven't been able to identify exactly why, The new Notes have the room attribute and also the OIP so there's actually a way to get part of what I wanted.

Yep, those custom_fields make a world of difference since we can now access them and perform calculations, etc.

HI Mark, Did you notice the new attributes for panels and inserts? At least I think they are new.

That's the correct way to do it.

That's correct but it's what I assumed would be in that data. Apparently they only provide it for material take-off. There are times when I provide an insulated wall even though the space is not going to be conditioned initially. The attribute should be a part of the Wall Type regardless of where it's located in the plan. BTW, R-value is much more important than the thickness. You could have a very different R-values depending on the material so thickness without the R-value is worthless.

Here's what's reported when the wall is part of a conditioned room: > owner.upper_insulation => #<NVPublisherOwner:0x0001f445f1e678 @names=["area", "width", "depth", "length", "formatted_size", "num_batts", "owner"]> > owner.upper_insulation.formatted_size => "6x16x93\" batts" But the actual cavity R-value is 21.0 In any event, why shouldn't the data be a part of the wall even if it is just a short segment in a wall legend?

Hi Larry, Just trying to give you a simple way to accomplish what you are asking for.

I found 2 attributes that are not getting any data. lower_insulation upper_insulation I reported this and asked that the oversight be fixed. The data is available in the Wall Type dbx but it just isn't being picked up in the wall attributes.

I like the new Wall Schedule in X11 - but I usually want more than just the simple description that provides. So, I created a custom macro that utilizes the wall layers attributes that are new in X11. In addition, I used the Wall display Layer Name to show the Type (Exterior/Interior) and the insulation value. There's a lot of new information available this way.

Larry, Just utilize the "Saved Plan Views". Each "Saved Plan View" will have it's own Reference Set.

I know - but I was referring to the fact that a Framing Member specified as a Steel I Beam (I would probably be using W Shapes and sizes) could be reported correctly. Unfortunately they appear in different areas of the Materials List than Lumber Framing.

This is another reason for having the OIP for Framing Objects. Then we could use OIP fields for annotation and the Material List.