Joe_Carrick

We used Palomar Mountain and Julian as training rides. We started in Escondido.

Hey Scott, That looks kind of like a bike trip I did in 1990 - except that we started in Bangor and ended in Washington DC. It was all along the coast until we got thru Connecticut. Then we went thru Pennsylvania to Gettysburg and down to DC. It was really great because you see a lot more from a bike than from a car. We camped almost every night except for a couple of nights in motels.

I will figure out a price - but it will take a few days because I need to outline all the needed info and devise a way to make it all work with a minimum of user input. I need to think about using Wall Types (custom named) for the BWLs and Cabinet Partitions for the BWPs. I will also need to set up a table for the Code Table Requirements and Adjustments. Unfortunately Chief doesn't provide some of the Wall Properties needed to just rely on the plywood sheathing. However, the Wall Type Name can be used to ID Shear Walls. OTOH, it might be more logical to just use 2 separate Cabinet items (Shelves and/or Partitions) due to the ability to use OIP fields to store data.

That works and it can turn corners as well. More than one way to skin a cat.

Another option would be a 2" diameter cylinder (primitive solid) rotated 90 degrees to be flat and assigned a dashed line style. It can actually be set at a z height of -36" and stretched to whatever length you need. Yes, it's really 3D but you don't need to show it in 3D Views.

Yes, this is true. Exterior Door Frame & Exterior Door Sill & Exterior Casings are all specified by the "Exterior Trim" material. I've requested separate materials for each of these items. This is not consistent with real life conditions.

To get a Braced Wall Panel length & floor number you will need to use something that has a length or width attribute. A custom Wall Type or Railing Wall or Cabinet would work for this purpose. To automate a Schedule I would suggest Cabinets Partitions with specific OIP fields. IAE, It can be done using currently available tools but it will at least 2-3 custom macros. Depending on the number of calculated fields it might require more macros.

There is no way to make a stairway down to the basement from this location while maintaining the existing structure and foundation as you show it. Several things would need to be drastically changed.in order to get access to both the basement and to the main floor. Knowing the function of the various spaces as well as the exact foundation in that area will be critical to coming up with a solution. Even then, it might be extremely expensive.

Years ago - maybe X5 or X6 - we couldn't specify the Beam size. I lobbied for this for a long time and we got it. I've been using this capability for so long that I can't remember what version of Chief it appeared in.

Adam, Use Symbol Category "Hardware". That has the correct Option: "Treat as Handle"

For some reason CA left "Embedded Geometry" out of the Import Symbol Category.

Import the symbol as "Embedded Geometry" and click "Treat as Handle" in the Options Tab

Hi Scott, It doesn't work with doors because Chief doesn't handle Door Jambs correctly. Basically, we need control of the materials for Jambs & Sills separate from the Trim - and the Jambs need to work like Window Frames. ie: The wall opening (including stucco wrapping into opening) needs to be outside of the Jambs in 3D. Currently the Stucco wrap and the Jamb face are at the same location. Additionally in 3D the Wall Framing appears at the same location so there's a lot of z-fighting going on. All these problems are tied to Door Jamb / Casing problems I've reported in other threads.

There's a rumor that it will be in X11.

Small adjustment needed. I had an exterior casing (beveled profile) and a RO 1/2" clearance all around when I took that pic. By simply eliminating the casing it's almost perfect - even in vector view. The only problem is that the stucco layer shows as separate.

Quite some time ago there was a topic on "Bucked Windows". Here's an example using just the Window dbx in a 2x10 stud wall. It took a bit to get it just the way I wanted it but ......

Door DBX, Options Tab, Double Door Only

Use a 3D Molding Polyline. As Robert said, Wall Caps are only on the lower portion of Pony Walls.

Actually, you can do it in a text box with an arrow connected to the Polyline - but the macro would need to be "referenced" and maintaining the connection of the arrow can be difficult. Labels are best.

Alan, Create a new owner context evaluated macro named area_40 with the content (area.round(1)*40).to_s In the Polyline Label place %area_40% along with any other text you want. You can't just do this in a text box - it needs to be in the Label of the Polyline.

Alan, I would need to see all 3 of your macros to know what you are doing wrong. I suspect it's the way you are calling the macros but it might be the returned values of the 2 macros you reference.

Check your System File Settings for "File Types". That's what controls the App that Windows will try to open a file with. .calib .calibz .layout .plan This would be particularly important for any file that hadn't been previously saved in X10, such as existing templates from prior versions.

Alan, What you are trying to do is not possible with the current set of available properties of the Foundation Wall.

That's not all that needs to be answered. %AreaPline% ??? would need to return the area of a PolyLine as a floating point value, not a text string %Roof TL% ??? would also need to return a floating point value, not a text string. x would need to be changed to *. Ruby uses the following characters for calculations: +-/* In any event, the load on that column would not be the result of the proposed calculation anyway. Alan needs to consult an Engineer. The Hip Beam has a reaction that is much more complicated to determine.

Works fine for me as well. It appears that you have your system set to open this file with the wrong App - probably a text editor.