Alaskan_Son

This^^^^ except that you can speed it up by group selecting and addressing them all in one go.

Actually, we still have Export to Res Check. That's a different tool and I don't believe anything was changed in that regard. The newly listed feature is a simple CSV export option to replace the thermal envelope data that we used to get in the Materials List.

There are quite a few methods that can be used. A few things to remember though that will hopefully help you... Under normal circumstances and unless they're manually manipulated, walls will automatically build through until they hit a roof or ceiling plane. This means you can either drag walls up/down in 3D (not the most ideal) or keep your roof planes inside your walls. Under normal circumstances, unless they're manually manipulated, and unless they're under a roof or ceiling plane, walls will continue up until they reach the height of your defined ceiling. This means you could set the height of your parapet walls using the room ceiling height or by building roof planes directly over the walls. You can create a room's ceiling using a manual ceiling plane and/or by using the room's ceiling definition. This means your room definition ceiling height could set the parapet wall heights and a manually placed ceiling plane could be used for your actual ceiling. As Ryan already mentioned, you can use multiple floors to further add to your possible options.

I agree. Not sure if this is the thread you're talking about or not, but here are my thoughts on the subject...

This should really be posted in the General Q&A section. Delete this thread, post a new one over there, and you'll likely get a few more answers pretty quickly.

The defining macro needs to be executed somewhere onscreen or else the global will never be defined. It doesn't necessarily need to be visible, but Chief needs to render it somehow. If you want to use the Text Field for example, then you would need to have the Note Schedule placed somewhere in your view (even off to the side) and the Text Column would need to be displayed. Because the Text Column is displayed, the defining code will be executed, and then global variable will be set. The problem with the Text Field is that the Note Schedule is the only place that text can be rendered onscreen aside from the actual data entry field. If you want to use a Custom Object Field, you could still use the schedule method, but there are other more complex methods you can use as well. For example, you could just include the defining text in your actual callout label in such a way that it is not displayed, like this maybe... %simple_schedule_number%%($test = custom_fields["Test Field"]); ""%

Just in case you aren't aware of this, you can actually just enter that code directly into the label as well like this if you prefer... %automatic_label% %width% x %height% (Glass Area %((height-4.in)*(width-4.in)).round(1)%)

The %automatic_label% macro will report values according the Automatic Label settings even if those settings are greyed out...

Objects set to be included in schedules can automatically either use their standard Label or they can use a Callout label but not both. Whether a Callout is used for the label or not is controlled by the schedule(s) that object is included in (Labels>Use Callout For Label). The Callout label is limited to the schedule prefix and the schedule number. If you want to include more information than that, you will need to uncheck Use Callout For Label. If you're using the Automatic Label then you can choose to Include Schedule Number. If you're using a Custom Label though you'll have to manually include %schedule_number% in your label. You can also optionally have both the standard label and a callout label by placing a callout manually and connecting it to the window using a line with an arrow, but that's typically more work than its worth IMO.

Never assume its being worked on and always report things that you really care to see fixed or changed. Like every other company out there, Chief has limited resources, and they're going to work on higher priority items first. If there is some obscure tool that only 3 people use that's just completely broken and all 3 people report it, its still likely to take a back seat to the 20 complaints they see for some other tool that is just not working as expected. I personally don't think its very productive for users to even share when a problem has been acknowledged by technical support because it really means next to nothing and gives a false sense of assurance that the problem is being addressed. Just because its on their radar doesn't mean its getting worked on. It only means that they know about it and that they plan to work on it when it makes its way to the top of the list. One of the best ways (if not the best way) to help ensure that it reaches the top of the list is to report the problem yourself so that your name gets added to the list of people who care to see it fixed. I also think its worth noting that the problem you're experiencing may not even be the same problem another user is experiencing even though they seem similar on the surface. Sometimes its simply impossible to know for sure until you submit all the required information. Again, if you're experiencing a problem and you care enough to see the issue fixed, report it yourself.

I agree. Seems like a bug in this regard.

This is an extremely powerful and robust approach and what I recommend doing as well. If you're not aware, you can also group select those polylines and generate a combined material list. You can then even further filter your results afterward by editing the Layer Set being used for that Materials List.

You should send in a report as well if you care enough to see it fixed.

Perhaps not. The problems you're seeing are the type of thing pretty commonly caused by using that sort of methodology though so I thought it was worth mentioning just in case.

Your various room definitions from past changes keep carrying forward. You'll need to clear out those room definitions to get the expected behavior. Try this... Switch to a Wall tool Hold down the Shift key and group select all the room defining walls on the first floor using a Marquis (if you get extra walls in there, that's fine). Cut those walls to your clipboard Save the plan and close it. This will clear out the old room definitions from that plan. Open the plan right back up. Paste Hold Position Build Foundation You'll have to go back and redefine your various rooms as necessary, but this should return the foundation behavior to what you would normally expect. In my opinion this looks like yet another example of why Chief has always discouraged the Save As Method. It keeps carrying problems and file bloat forward from one plan to the next. In this case you had room definitions from prior plans or from prior plan iterations causing all sorts of problems. They would have automatically been cleared out from memory had the rooms (defining walls) been deleted from past plans, but it seems that never happened and so you were left chasing your tail because no matter what you did, those old room definitions kept taking over.

Again, changing that setting isn’t what’s doing it. Simply opening the dialog and making any change whatsoever will do the same thing...even just clicking Okay will do it.

You are correct. That capability is gone. It was replaced by some much more robust capabilities though IMO. And you can't configure “Dimensions, Overall” specifically for Automatic Dimensions. It is the system default so that if you open an automatic dimension and place a check in the Default checkbox, it will be moved to the "Dimensions, Overall" layer. Again though, clicking Okay will also simultaneously modify the string which will change its system default layer to "Dimensions, Manual" (legacy plans) or "Dimensions, Plan" (X13 templates). And sorry if my statements were confusing. I wasn't really suggesting using the Default checkbox or using the "clicking Okay" method. Just meant to describe how it works. By the way, I did make a mistake in my last post. I should have said.... I went back and corrected it. Hope that helps clarify things.

That layer appears to be the System layer that replaced the Dimensions, Automatic layer. It’s the top level system default layer (as opposed to the Saved Default layer) for Auto Story Pole Dimensions and the top level system default layer for automatic dimensions. As I pointed out in my post above though, that default is extremely temporary though and I’m guessing it was only left in there for legacy plans. Bottom line is that there are a couple top level default layers. For all intents and purposes though, they should hardly ever come into play. We can now control BOTH manual and automatic dimension strings at the Saved Default level which was a huge improvement. If you prefer to place manual and automatic dimensions on different layers, you still can, but I think for 95% of situations it’s still faster to do so using the new capabilities. Either change your active dimension default or just move to a different layer later. Like I said, you can even do so by simply opening the Auto Dimension string and checking Default.

Didn’t mean to jump to any conclusions. I chopped off the last part of the quote because it was irrelevant to my comment. And if you weren’t talking about the layer behaviors with then first part of your statement, the what were you talking about? Nobody ever said anything about Locate settings. I’ve read it through about 10 times and I can’t for the life of me figure out what you were getting at now if it had nothing to do with the layer. Anyway, even if you weren’t talking about the layer, my comment still stands. That setting is nothing more than a toggle for the locate settings. Not sure what that had to do with anything being discussed. It just seemed to be confusing matters.

Don't forget that we can also simply Import>Import Terrain Data without having to jump through quite as many hoops. The data can simply be imported from the aforementioned sources as simple csv/text file data.

A few ways to fix your problem, but I'll give you a couple hints. First off, both your roof and your ceiling are set to Use Room Ceiling Finish (Structure tab). The Room Ceiling Finish is only applied to the first roof or ceiling with that setting checked that Chief finds on its way up. Either uncheck the setting(s) or edit the roof/ceiling plane so that the ceiling plane is lower than the roof plane.

The setting your changing in the screenshots actually has nothing to do with the layer. That setting is specifically to specify which locate settings are to be used for that string if you should decide to use the Add Segments edit handle. It only appears as if its affecting the default layer because you're modifying the string. You could make any change though and get the same effect. In fact, you can even simply open the dialog and click okay to change the strings default layer. This behavior was actually the same in prior versions as well. Any modification to an Automatic Dimension string changes it to a manual dimension string and therefore changes the default layer. As far as the default layer for Automatic Dimensions in X13 still being "Dimensions, Automatic", I'm betting that is simply a legacy plan behavior to help ensure things carry over properly. It is a little odd though. Checking Default in X13 for an Automatic Dimension string will move it to the "Dimensions, Automatic" Layer, but, doing so will also modify the string, so as soon as you click okay, the default layer changes to "Dimensions, Manual". I have no problem with any of the new behaviors and appreciate the changes. The default layer thing is a little funky though.

You sure you don’t have this backward? Plot lines take far longer to update than live views do. I feel like I must be missing something.

Sorry, that wasn’t very clear was it. I was referring to the settings I mentioned in the post I referenced (they were mentioned in the graphic as well)... Floor Supplied By Foundation Room Below and Supplies Floor for the Room Above. Those along with the Floor To SWT setting.

You could have just adjusted those 2 settings. No need to rebuild the foundation.