Alaskan_Son

Hey All! I'm starting up a sort of old school style subscription based mailing list here where I'll be sending out weekly emails filled with a variety of goodies. They'll be aimed more specifically at intermediate to advanced users but I'll be trying to include tidbits for beginners as well. Those emails may include: Answers to common questions Answers to specific questions I see posted here on the forum that I think would benefit a lot of people Solutions to various needs emailed over by subscribers Power tips Misc. tricks and hacks Tutorials Custom macros Custom symbols Example plans In-depth insights into various Chief tools and settings Advice/guidance on various supporting software Workflow guidance Links to other valuable content Etc. ....just whatever I think would be of service to the group but in manageable chunks I've been using Chief since version X3, have 25 years or so of experience in the industry, and have a lot to share. I've long wanted to find a suitable outlet to do so and decided a basic subscription based mailing list is where I would like to start. If the mailing list gets to be large enough, I'll consider converting it over to another format and possibly expand on my offerings but for now, let's see how this goes. Emails will be sent out at least once a week but may be published more frequently if I choose to do so at my own discretion. If the scheduled publish date lands on a holiday or time when I'll be away from the office then I'll make up for that week on either the previous week or the following week. PRICING: Individual subscriptions*: Single email address only - $15 monthly or $150 yearly *Please Note: Individual subscriptions are intended for single user offices only. If you have multiple seats of Chief Architect, please see Multi-user office rates below Multi-user subscriptions**: 2 email addresses - $25 monthly or $250 yearly 3 email addresses - $30 monthly or $300 yearly 4-9 email addresses - Add $5 monthly or $50 yearly for each additional 10 or more email addresses - Email me at alaskansons@gmail.com for pricing **Please Note: Multi-user subscriptions are intended only for offices with multiple employees/multiple Chief Architect licenses Content Creator subscriptions***: Single email address - $60 monthly or $600 yearly 2 or more email addresses - Add $15 monthly or $150 yearly for each additional ***Please Note: Content Creator subscriptions are intended for any and all users creating Chief Architect related content or acting as Chief Architect trainers. All monthly subscriptions will get a minimum of 4 emails TO GET ON THE MAILING LIST: Just send payment either using Venmo® (@MABASC) or PayPal® (@AlaskanSons). Please make sure to include a message with the phrase "Chief Mailer" along with your email address(es). Please place administrator email at the top of the list. Your subscription will be linked to the email address(es) in your message. You can also email the requested information to me and I can send out a payment request link. Email any questions over to alaskansons@gmail.com. A mailing list may be a bit off the beaten path and it may not be the most glamorous or cutting edge approach, but I think you'll be happy you signed up Issue #7 is set to go out Friday, July 12th!! P.S. For those of you who already know me, know what I have to offer, or who have used my services or insights successfully in the past, your feedback would be greatly appreciated. Please feel free to share your experiences below. Thanks so much and look forward to talking to you again soon!

If you change the settings I described, this would not be the case. What I'm saying is that you have 2 ways of controlling all those elevation lines and you're boxing yourself in by not using the Layer Set instead of Edge Line Defaults. I would really encourage you to learn to use the Layer Set instead of Edge Line Defaults. It will save you a lot of time and give you more possibilities.

You have to stop using Edge Line Defaults. If you check Use Edge Line Defaults, the line style, weight, and color are all being overridden with a solid line using the color and weight you have selected for your Edge Line Defaults. if however you uncheck Use Edge Line Defaults, your Edge Lines are all controlled by the Camera’s Layer Set. If you open that Camera, go to Active Layer Display options, Select All, and then change all line styles to match your Edge Line Defaults, you should get the same results you had before except that your below grade lines will now behave the Override settings.

Those controls have actually been there since X15 and they are mentioned in the Help files as well:

Ya, I guess it depends on whether you want 2 instances or whether you just want access to the same instance.

Actually, all you have to do is hold down the Control key while Chief opens in the second desktop. Its the same way we open a second instance on the current desktop as well. I was thinking the goal was multiple instances.

Just change all the line styles for all the layers in the required cameras' layerset(s) to use whatever linestyle you're using for your Edge Line Defaults. It should essentially have the same effect.

My guess? You have Use Edge Line Defaults selected for that Layout Box. This would override any other line style settings being used for that view (except possibly Pattern Lines).

Default Settings>Materials>Terrain/Property Line

This is exactly right, however the OP was attempting to rotate the North Arrow to precisely the right angle, and although its been over 8 years since my post, I assume I was trying to point him toward adjusting the Number Style so he could view it and then adjust that angle right there in the dialog using the same format. Anyway, in order to enter precise degress, minutes, and seconds. Enter in the following format: Example Angle 1: 21° 45' 34" What to enter in Angle field: 21 45 34 Example Angle 2: 21° 45' 00" What to enter in Angle field: 21 45 Example Angle 3: 0° 0' 34" What to enter in Angle field: 0 0 34 The trailing zeros are optional as are the minute(') and second(") notations.

As Joe said, Chief doesn't provide the name:value pairs that you need. The macros you're using are special "Global macros" or intraChief string substitution macros that I don't believe are even run through the Ruby interpreter. Regarding your syntax: You're not getting the expected results because although you've defined your method, you've never actually called on that method. Getting wall heights into a wall schedule can be done by the way. It just requires a more complex system that is slightly less automatic. If you want to st up a private consult, I can set you up with the basics.

I don't think you're getting any responses here because most people who understand the issue are wondering why you don't just try it. Draw a single wall, follow Rob's advice from that other thread, generate a materials list, and take a look at a 3D view. You'll have your answers faster than the time it took to type of this response : )

Quite a few ways, but here's a pretty simple one: Drop a Room Finish Schedule into your plan, delete all the columns, add Area Interior and Area Standard. Set the schedule to Include Objects from All Floors and to Display Totals Row. This should give you 2 totals. Just manually subtract the one from the other.

CAD Detail is typically the way to go, BUT if you really want to put schedules in specific views (and there definitely are valid reasons to do so), all you have to do is put the schedule on a different layer and turn that layer off in other views... Also, just as a side-note, you should familiarize yourself with the Project Browser for quickly accessing your various views (specifically CAD Details in this example). I typically have my Project Browser tabbed along with Active Layer Display Options and the Library Browser...

A few solutions come to mind: 1. Create a special Layout Template specifically for these smaller schedules. It can even be nothing but a blank page with no borders or title block. Maybe only page numbers. 2. Just print directly from the Plan using the Print dialog. When doing this, I will typically zoom in so the desired area is centered onscreen, use "Chief Architect Save As PDF", and then adjust the Fit to Paper scale so that the preview shows it filling the page like I want. See response posted by@DBCooper below for a good way to set it up so you can more efficiently set the positioning, zoom, and scale by just printing from a CAD Detail (again this is still printing directly from the Plan). 3. Copy/Paste the Schedule to another program and print from there. This can be tricky though and may not be desirable since you'll lose any callout symbols or 3D views that may have been in your schedule. 4. Select the Schedule and click the Export Text tool to Export to another program. This has the same issues as Copy/Paste but also has a few benefits over the latter in the various export options.

A Plan Footprint is a special object type on Chief. If you're not familiar with it, search the Help files for Plan Footprint.

The Plan Footprint is controlled by the Layer Set being used in your CAD Detail, not the layer set used back in your Plan View.

We have handles for Leaders and for Callout Arrows but not for Section Arrows. A suggestion for the Callout Arrow to be used along with the Alt Key to pull a Section Arrow might be a good one.

I don't typically donate time to troubleshoot or advise on scripting issues on here anymore, but I decided to make a one time exception this morning: There are all sorts of little problems: source_information = %room.area.internal% numeric_part = source_information.match(/\d+/)[0] numeric_value = numeric_part.to_i result = numeric_value / 20 puts result 1. %room.area.internal% isn't a Ruby accessible object attribute (name:value pair). It's just a Chief Architect string substitution macro. If you want to use this macro in a text box placed in the room, the name:value pair you should be using is simply room.internal_area without the percentage signs. 2. The match method is a Ruby method used to parse a string. The internal area attribute however is not a string. Its a Measurement. If you want to use the match method, you first need to convert the source_information to a string using the .to_s method. 3. Just an observation, but you may not be getting the results you think. The .to_i method is converting your results to an integer which is the whole number rounded down. 0.999 would become zero, 559.9 becomes 559, etc. What's worse though is that because you're diving by another integer (20) the results of your calculation would also become another integer. So, instead of 559.9/20 = 27.995 you would get an even 27. This one can be solved by just converting to a float (which contains decimal values) and then rounding the result. This can be done a number of ways, but one of the easiest would simply be to replace .to_i with .to_f. 4. puts isn't used in Chief's text macro environment. It's simply not needed. If you try to use it, your results will by nil (empty). So, the corrected macro becomes: source_information = room.internal_area numeric_part = source_information.to_s.match(/\d+/)[0] numeric_value = numeric_part.to_f result = numeric_value / 20 result.round Although the above macro would work, it still has a handful of totally unnecessary code and could be reduced all the way down to: (room.internal_area.to_f/20).round

Are you sure you used the Hole in Ceiling Platform tool and not the Roof Hole or Hole in Roof / Custom Ceiling tool?

Have you looked at the Hole in Ceiling Platform tool to see if that does what you want?

To get additional items into the Material List, you need to use the Components tab.

What happened to... ??