AgChief

Well that was easy enough. And I had obviously done it before. But I've slept since then... Also, naming the png file the same as the custom toolbar button did the trick. Thanks!

Does anyone know 1) How to get my custom toolbar button icon to show? I was trying to edit the icon and pulled it off the toolbar and it disappeared. 2) How do I change the icon of that button? Is it a simple matter of creating a button icon and name the file the same as the custom toolbar? I noticed that's what the icons are named for the standard buttons.

How about this. Instead of a door facing the Dining Room, make it a cased opening going to a hallway and create a mechanical closet by enclosing the water heater and A/C with double doors. I try to avoid placing doors on "public" areas, or at least soften their presence with a cased opening. I also placed a cased opening at the entrance to the Hall to the bedrooms for the same reason.

Latency/unresponsiveness has always been a huge aggravation for me with CA. This simple test took my system about 6 seconds each to increase and decrease magnification. How can a simple single (albeit large) Psolid bog down the software like this? Is this typical with everyone's system? Edited to say that I just noticed the 1/16" scale concrete pattern. That's the reason it's so slow, I realize. How does CA generate that? CPU or GPU?

Not sure if this is what you're looking for, but it's a method I've done on lots of houses in Texas. I just lowered the roof pitch on the back half of the house to a 6:12 so I could have the main left-to-right ridge defined by 13:12 roof pitches, framed from an interior wall about halfway toward the back of the house. That frameline is really arbitrary until you want to determine how high you want the highest ridge. Pull that roof plane forward and it'll lower the ridge. Push it back and it'll raise it. I never use the automatic roof function so all of these planes were done manually. When I saved the chief file I saw that you're on a version older than x10. I went ahead and saved it to x10 but I've uploaded some screen shots too. Trying to Zip plan.zip

I haven't explored all the options for this and, really, I just had an idea and threw something on the wall to see if it would stick, but how about this: I had already created a wall type with 1x3 furring strips to create a rainscreen gap, so after I built the wall framing and the furring strips showed up, I thought the same could be applied to battens. What I did was to create a wall type with the outer-most layer being a framing layer of 1x3's spaced at 16" oc to represent the battens. Then you have to build wall framing for them to show in 3d and on the plan, and set auto-framing to "ON" to update the battens when editing the plan, etc. The problem is that if you have to delete battens that aren't spaced correctly, or there are just too many (like at corners) you have to turn off auto-framing and you're back to square one if you change anything. What you end up with are individual framing parts that are similar to psolids but are somewhat parametric, albeit very limited. Addionally if you're just looking at the model without the framing, that exterior layer of battens will show up as one plane of material and cover the "boards" which, in this case, I just used vertical siding. Board and Batten experiment.plan

Thanks, Joe!

Reviewing this thread, I just noticed that my "ObjectProperties" is different, and I have absolutely no idea why. Is your "ObjectProperties" the stock version or did you change it? See the attached pic.

Joe, I dropped your name when I contacted tech support, so that's probably what sped things up!

Thanks, Joe! I've reported it too so maybe we'll get a quick fix.

Nope. I'm not referring to "modelling" as I've been drafting on 2D Autocad for my entire professional career. I'm simply referring to placing a note on the plans telling the framer where to set the top of the window. When I've framed window openings and on every set of working drawings I've ever done where the top of the window is referenced, it is referred to as "Header Height", and as far as I've experienced it's been common nomenclature in this profession. I've been doing this for over 25 years and have never, ever had an issue with a framer in terms of window placement height so believe me, all of these years I've obviously been doing something right. This thread was intended to point out a potential bug and to see if anyone else had experienced it. I'm certainly not an expert in Ruby, but I've had success with this macro in the past, and when it doesn't work after an update it logically follows that there's a bug.

Exactly. It's not working after the x9 update, when it was working perfectly fine before. Before the last update %top_elevation% returned the top of the window in inches, which I then formatted to feet and inches in a format (ie., 6'-10" H.H.) that my working drawings have had for years. I never consider rough opening when I call out the header height so why would I go to the trouble of doing the math in an equation when that information is (or, has been and should be) provided by %top_elevation%?

I think the issue is that since top_elevation has the string formatting, the macro blows a fuse when it tries to evaluate a string in a real equation.

Thanks, Joe. It looks like Chief has added formatting to %top_elevation%. I can avoid the error by changing the original macro by substituting header_elevation for top_elevation in the macro. Adding "owner." to the macro doesn't seem to have an effect. The following macro does give a valid result but "header_elevation" isn't what I'm looking for, as it accounts for the 1/2" at the top of the window for the rough opening then rounds up to the next whole number. In this case it would result in 6'-11" instead of 6'-10" arr = header_elevation.round.divmod(12) "#{arr[0]}" "'-" "#{arr[1].round}\" H.H." Like I mentioned, I think Chief must've added the quotes to the formatting to denote inches, which screws up my macro. See the attached image to see the difference in the results.

Anyone else getting #EvaluationError# on macros since the x9 final release? Things were working fine until the update to the final, non-beta, x9 version. I have a set of working drawings to finish up..... Here's the offending macro, it's purpose is to show the header height on a window label: arr = top_elevation.round.divmod(12) "#{arr[0]}" "'-" "#{arr[1].round}\" H.H." evalerror.plan