Joe_Carrick

6 minutes ago, JKEdmo said:

 

For your consideration --

 

If the framed wall stands proud of the stair, one option would be to leave the full-height doors like shown with the door leaves concealing the sheet-rocked stair underside.

Assuming the doors swing outward.

Otherwise it will be a problem because the one on the right will not open no matter what the shape.

1 hour ago, basketballman said:

Always been minimum of 4" height difference between garage and main living area.

Code cites Fire and also flood prevention ..

Can you reference the Code Sections for this?

The CRC (California version of the IRC) only specifies a slope for drainage.  I can't find anything about a height difference.  The 4" height difference was a requirement at one time in the old "Uniform Building Code" but I'm not sure if it was even required in the last UBC.  I don't think it's ever been required in the IRC or any version thereof.

Fire protection is another issue entirely covered by Doors and Walls.

When will the X15.3 update be available?  I sure hope it will be this month.  

--- and of course that it includes all the NVPs I've asked for. 

Just use "Text" or "Rich Test" and drag the diamond icon to create the line with arrow.

Search for Roll Up

I posted one in a thread that comes up.

14 minutes ago, Hautetxinteriors said:

Yes, it has the show open off. 

Have you "Updated" the view?

Make sure the "Show Open in 3D" is off.  

It could be done with a custom macro in a text box with an arrow connected to the cabinet.

For a more comprehensive automatic method a custom macro would have to be created that would rely on the name of the layerset so that the label would only display that in an elevation view.

OTOH, the "Comments" field can be shown as a column in a Cabinet Schedule.  That's probably the best way to deal with it.

37 minutes ago, KenL-sdd said:

@DBCooper I only want to remove a portion of the fascia, not the entire roof. I think we need a menu to turn off on selected edge like gutters.

Thanks for your input.

Ken,  That setting can be for an individual roof plane.  If necessary you can break a roof plane to get just a portion of the edge.

My preference - if possible - is to have about a 5-6 ft level area and then a step-down that acts as a wheel stop.  I usually have the door between the garage and the interior at a location so that's possible.

Rene,

$Global variables can be assigned values from an object - but they are not attached to the object.

OTOH, you can assign any value (including a $Global) to any field in an object's OIP.  Just be aware that if the $Global"s value is change then that OIP field will also change.

I have some macros that rely on the current view Layerset name.  Unfortunately that is assigned to the object when it's created so it's not going to be available for the object.  My solution is to place an invisible text in each view with a macro to assign the Layerset name to a $Global.  That $Global will always be the name of the current view Layerset as long as the Layerset of the view isn't changed.

I had requested years ago that Chief add a $Global for the current Layerset but they simply added the NVP for each objects layerset. 

To store a value in an object use an OIP field.  

To assign a value to a $Global use an objects NVP or any other value you want.

BTW, a $Global can be an array if you want to store a lot of different values.  $p[n] where n is specific to the object.

A Hash could also be used, depending on how you want to be able to identify the values for retrieval.

For an asymetric door you will need 2 versions.  This is not a matter of "Change Hinge Side" - rather it's a matter of the actual swing.

3 hours ago, Renerabbitt said:

I fixed it, and it is a bug. If you added something to a style palette that contained a macro in its label, that macro will always remain. You have to make an entirely new style palette. You cannot overwrite the existing style palette because the label macro remains. Interesting because there is no reported value for label in Style Palettes

I think I understand.  It's kind of the same as the previous problems (prior to current X15 version) with symbols stored in the Library.  What object did you include in the style palette?  I assume there wasn't any way to replace that object with a current X15 version object.

no idea - post the plan 

Larry,

Is this a Client Logo & Title Block?  

If so, for different Clients - just relink the PDF on page 0 (default template page)

Also note you can have different templates specified for different pages in the Layout so the PDF could be different for those pages.

5 minutes ago, HumbleChief said:

I'd like to avoid having to do this on each page and have the page 0 masks overlay front/top each PDF on each page in the layout

I don't think there's any way to do that automatically. 

I'm assuming you would have different PDFs on different pages at different locations on the pages.  A mask on a default page would always be at a specific location, not relative to the PDFs.

Larry,

I'm assuming you want to have some text over-writing an area of the PDF. 

If that's the case, just use a text block with a white fill.  That's how I do it.

Search in "3D Warehouse" for Models "Clothes Line".

There are a lot of them.   

btw, I haven't seen those used here in California, USA for about 50 years.  We had them when I was still living in my parent's house before I went to college.  Now almost everyone has an electric or gas clothes dryer.

This would be IMO a very difficult programming task.  Chief's walls are very special objects which define the vertical limits of rooms.

If a sloped window wall is what's wanted I would simply create a symbol using a post to ceiling glass panel railing, defined as a geometric shape.  I would set a z stretch plane at + 12".

Then I would place it in the plan and rotate about the y axis to the angle desired.  I would make the wall where I place this as a single layer transparent wall. 

Perhaps if Chief were to create a "Window Wall" tool with the ability to specify a slope it could work - but it would need to also define the room as other than contained simply in a vertical wall.

if you use Wall Types set as "Partition Walls" they won't cut the finish flooring, intersecting walls or ceilings.  I'm using X15 so I'm not sure if that's the same in X10 - but it should be.

8 hours ago, Renerabbitt said:

yes but not with style palettes

Where was the macro assigned in the Style Pallet?  If it was in the Components you can:

• Open the Library Object 
• Select Open Object
• Components

and make your change there.

I don't know of any other way to get a macro into a Style Pallet.

1 minute ago, Renerabbitt said:

BTW i think we have space available in Idaho, did you already find a place?

My wife is coming with me and we have booked a suite at the Hampton Suites next to LePeeps.  We have other friends that live about 30 miles north which we will also be visiting.

So in X15 you can select the object in the library and edit its macros by right clicking on the library object and selecting "Text Macro Management".  My methodology is to copy/paste the X15 macro content into the existing macro and rename it as needed.

Just now, Renerabbitt said:

Joe are you refering to my template plans or in general?
All of my updated plan macros were written in X15...also I do not believe any of the macros I provided were problematic in X15..not that I know of anyway

I'm not referring to your template plans.  There shouldn't be any problems with plans created using X15 templates that are using X15 macros.  The problems would only occur when a Library Object created in X14 (or before) with embedded macros is added to an X15 plan.  Those macros wouldn't be the same as the ones in the plan and so might be incompatible.

2 hours ago, vikiw_bend said:

Hey Joe - what went wrong with the X14 plans you brought in to X15? I brought a couple plans in but haven't checked them out thoroughly. Were the problems obvious?

It was almost all related to NVPs in macros for openings (doors & windows).  Also since I rewrote almost all of my user macros for X15 and renamed some of them to X15 conventions (no spaces in macro names) there were a lot of macros that were no longer valid in those plans.

If you don't use many macros in your plans you shouldn't have too much problem.  That's not my way of working.

For example, I have macros for openings (doors and windows), walls and roof planes which provide different labels in plan views than in elevations & sections.  Almost everything in my plans and layouts are annotated my these very comprehensive macros.