Alaskan_Son

Default Settings>Schedules>Custom Object Fields

Import into Plan and then Copy/Paste into layout.

Usually shutting down Chief completely and then re-opening fixes this type of problem. If not, open Task Manager and make force the shut down of any other Chief Architect related processes and then re-start Chief. If that doesn't work, then I would re-start my computer.

Hey Kristine, just sent you a PM

I believe it was changed to more closely resemble how files and cells are selected in other processes. I suspect a lot of people were expecting a certain behavior, getting confused by how Shift and Control work, and then costing Technical support a lot of time. I can sympathize to a certain extent, but I maintain that better documentation/education is the answer, not taking away functionality for the sake of so called continuity. We’re not selecting from cells and lists here. We’re selecting from a virtual 3D environment where there is commonly a jumbled mess of objects stacked on top of each other. The more refined and intuitive control we have over what we are selecting and de-selecting the better. I feel like our options in this regard were already pretty limited and that we only lost some of the little we had. To be fair, MOST of the functionality is still there...it’s just far more complicated and a whole lot less efficient now.

I detest this particular change more than any other Chief has ever made. Shift used to simply be restrictive based on the active tool and Control was non-restrictive. Either could be used to add or subtract from the selection with either a marquee or by single clicking. Now it’s a goat rope trying to remember which combination of keys (Control or Shift) and actions (single click, marquee, or right click) to use and when to use them (before or after an object has already been selected), etc. Very messy and hard to describe. I could easily teach a person to use the tools to efficiently select groups of objects in busy areas in X10 and prior. Now? Not so much.

I could set one up for you. Sent you a PM.

It is. Here's a quick video I made on the subject 2 or 3 years ago. A few of the settings might look different (not sure) but the basics remain the same...

Materials can only be made invisible in vector when used in the structural layers of roofs, ceilings, walls, etc. Even glass is not invisible in Vector Views unless its part of a door or a window. And as Eric pointed out, it has been requested many times. Maybe add your support to one or more of these threads...

Pretty sure I would just use a ceiling plane. That's really what it is anyway right?

A lot of various ways to go about this, but the key thing here is that you need to set your garage floor to have a negative elevation (this is how you tell the floor to drop down).

This is the "edge" of the roof baseline polyline that is controlling that pitch... It's just a little tricky to access. What you have to do is first drag the roof on the right either up or down (doesn't really matter which)... ...then select that edge and change it to 10/12... ...and then drag the polyline edge back where it was...

2 key things: 1. Chris and I are using Pattern Line Defaults. This is a setting at the bottom of the Send To Layout dialog and it must be set when initially sending the view to layout. When this setting is selected, the patterns no longer get their definitions from the material definition; rather, they use a single generic pattern line definition that you can set right in the layout box dialog. 2. In Preferences, you need to go to Appearance>Display and make sure your Color Off is setting is set to Grayscale.

Break and reshape wall and/or footing polylines in a 3D or elevation view.

I have a custom macro tool that I created a while back that makes pretty quick work of this. It needs to be tweaked a little to work more efficiently with X11 but it wouldn't take me long. Shoot me over an email if you're interested and we can take it from there.

Here's that one I was thinking of. I'm not sure where I got it or whether or not I tweaked an existing material or what, but I can't seem to find it in the library anymore. It worked really well for the last walnut job we did, but do be fair, that job was walnut stained with a walnut stain so it didn't need a lot of grain variation. HighRes Walnut Sheet.calibz

Looks nice Chris. I do very similar except that: I don't typically add any plants myself...Might look better, but it's just not something I do. It's extra work and I tend to be super picky so I would end up spending an inordinate amount of time trying to get them all positioned just so. Just not worth it to me personally. I don't use Edge Line Defaults. I prefer to have a little more control over the lines being produced for the various objects. I don't necessarily want them all to use the same line weight or color. Pattern Lines? Yes, usually...but not the edge lines. I've taken to just covering everything underground with a semi-transparent filled polyline. Nothing fancy, but it does what I want it to...

I am away from my computer right now but as I recall there is a Hi-Res Walnut Sheet in the core catalog that actually looks pretty good... Or maybe I had to tweak it. I guess it don’t remember for sure. I’ll check when I get back to the computer if I remember.

Absolutely. ...and a much smaller hammer will breach a window. Heck, We were working for a client years ago--changing out windows and doing a handful of other things--and she was really paranoi...er...concerned about the security of her daylight basement windows and wanted us to ad bars on them. I had a conversation with her explaining that there were various code issues to contend with and that if someone really wanted to get in it was still easy enough to get in. For example, yes, you might add bars to that little window, but what about the sliding glass door 15ft. to the right of that? Anyway, fast-forward in the project...We had a lock box on the house and she took the key out one day and forgot to put it back in for us. We showed up in the morning to get to work as scheduled after she had already left for the day and no key. No problem, it just took us a few minutes to completely remove one of the windows we were planning on changing out anyway. I think it was pretty disconcerting to her to see firsthand how easy it was to break into her little fortress. I still feel a little bad about that one because she was obviously already a little paranoi...er...concerned, but it went toward further proving my point. Its really not very hard to get into the house if a person really wants to and knows how. We do what we can, but stressing about this access point or that isn't really worth all the fuss if there's another easier way in.

Ya, I've thought many many times over the years that it would be really nice if we had a quicker way to specify that any given extension line should be marked as a center line. I use center line markers a lot myself and its definitely a pain to have to go in and out of dialog boxes to get one. The Centerline Dimension tool works okay, but what if we want the functionality of one of the other dimension tools? What if we only want the automated centerline behavior for one or 2 specific objects? Or what if we've already dimensioned something and need to add a center line marker later? It could certainly be made easier than it is.

There are many reasons, but the main 2 that come to mind: 1. As a safety feature as has already been mentioned. It's easy to adjust a bunch of things and then accidentally break the room definition and lose all your changes. This is one of the main reasons. 2. The tool can be used to produce a vast array of different framing configurations without our having to be tied down by room definitions. We can use this functionality to create; -decks stacked on top of decks (multiple tiers placed however you want them all created with deck framing) -decks with pergolas/trellis/lattice work above (all objects being created independently with deck framing) -decks with surface mounted posts/newels (frame deck with deck room and then drop floor and don't frame deck at all) -etc. Just think of it as a different tool entirely when you use that setting. Its a deck framing tool that just happens to use a room definition temporarily. The key though is that if you're using it as a deck framing tool then you also need to remember to turn off Automatically Regenerate deck framing when appropriate.

Nerp.

Definitely reference display IMO.

As long as your computer is set to display at the correct resolution for the connected monitor then the scale macro should report quite accurately.

This highlights one of the most fundamental pieces of the puzzle... Chief Architect and Ruby are 2 entirely separate constructs. The sooner a person realizes this, the better. A .json text macro is NOT a Ruby script. It’s a Chief file. That simple text file contains several key pieces of information that only Chief can make any use of...one of which (evaluated vs. non-evaluated) is whether the appropriate section of that text file should even be sent over to Ruby in the first place or not. An .rb file on the other hand is typically ONLY Ruby script and not something Chief can actually make any use of. It only becomes useful if it’s accessed directly by Ruby. And do what you guys want, this is obviously just one persons opinion, but I wouldn’t recommend switching over to Notepad++ till you actually learn the fundamentals. Based on some of the posts above, it’s clear to me that some of you are lacking some important understanding of some key basics. In order to address those shortcomings you should really stick with writing your macros in Chief, using the selected object to get accurate feedback, and using the Evaluation Error messages to see where you’re going wrong. Once you actually understand the code you’re manipulating, how that code is being used in conjunction with the Chief model information, and how that code is being run through Ruby and subsequently displayed onscreen by Chief, then I think you can better make use of an external text editor. Until then, I feel like you’ll be trying to run and jump before you can actually walk.