Joe_Carrick

So, go back and look at post #6.

I have a Border, Title Block, Grids, etc. set up on their own layers on sheet 0 for each sheet size.  When I select the Annoset for Arch-D, it selects the Layerset for Arch-D which has only thos layers visible.  Then I simply go to Print>Drawing Sheet Setup and select the Arch-D sheet size and then select Print>Center Sheet.  I can do the same for Arch_A, Arch_B, Arch_C and Arch_E.

This way I have only one Layout Template to maintain and it works for any sheet size.

It is possible to copy the door from the Chief library to the user/doors library and change it's Y origin.  this will make it correct in 3D views, but will not alter the position of  the 2D block in plan.

I requested that the 2D block be offset to match the 3D offset - but who knows if Chief will make that adjustment.

It could be a problem with displayed layers and what layer the text box is assigned to.

I don't have a problem with it the way it is.  I can set the defaults so that both sides of interior doors are the same.  OTOH, there are some who want the doors to match the room finish so IMO it's best not to change the current way it works.

Post the Plan - please!

You need to check the height.  It may be sitting on the floor.

Here's an example:

I have Annosets for each sheet size and a corresponding Layerset that displays only the backgoroung graphics for that sheet size.  When I select a different Annoset for the sheet size I then need to change the sheet size in Drawing Sheet Setup and also Center Sheet.

There is. (See material editing DBX.) However, this will do it universally for that particular material. I suppose you could create a new material for each unique surface by copying it and editing the pattern origin individually.

I guess I should have specified - per instance.  IOW, offset the fill pattern in this particular object (xoffset, yoffset)

Jared,

I would just popup the Windows Calculator ( I have it on my Taskbar) and enter the 2 values (glazing sqft / house sqft) and the copy/paste the result into a text box.

It's so much less hassle.

The Total Roof Area is more work than it's worth.  You would need to have a reference macro with an arrow pointing to each roof plane.  It could pick up and store that area in a global variable but to calculate the total it would have to then add each one up and store it in another variable to display.  Each time chief redisplays the plan, each of these macros would be evaluated and since roof planes do not have unique id's like room names it's almost impossible to make sure each value is zeroed out and the total is calculated properly. 

I've done a similar thing with decks, bedrooms, etc but with roof planes it would be almost impossible the way is currently configured.

The only values from a Polyline that might be useable would be perimeter and area.  Writing a macro to access those would be possible but it would need to be a reference macro and I'm not sure Chief has included the capability of entering user values in Ruby. 

The version 10 hardware lock will not work on X5.

If you upgrade to X6, you can deactivate your license via the internet when you want to use the Desktop system.  If you're going to be out in the field with the Laptop without an internet connection then you need to be sure to deactivate on the Desktop and activate on the Laptop before going out in the field.  The only other option that I know od is to have two licenses or purchase a hardware lock to use on both systems.

That's a pretty neat trick.  The question is how to get the XHatch to align with the boundary exactly where you want it.  When you block the item with the hatch, it centers in both directions but it doesn't appear to center the same in the X as in the Y direction. 

It would still be better if there was a setting in the dbx to offset both x & y independently.

Also, once blocked the hatch will expand or shrink as the object is resized.  If it's been resized such that the original x/y ratio is not the same then you can't unblock it.

There is another option by using a 3D molding but it would not show in 2D.

Cross Hatch Patterns are based on the [0,0] origin of the Plan.  There is no "offset" for these patterns.  To do what you want, you would need to create a separate pattern for each area.

It would be nice if each filled area had a possible offset in both x & y but as of this time, Chief doesn' have that capability.

I would place a "Room Divider" at each break and make it a Porch without a ceiling or a roof.  Then I would use one of the Wood Plank Materials for the Floor Surface.  You will need to make copies of that material and edit the angle for each different direction.  Using a "Deck Room" in this case is not very easy and the framing can be done manually better than the Auto Deck Framing.

BTW, you will need to specify the Porch Room Structure to be framing instead of concrete.

Do a search in the Legacy Forum.  There are some threads there that deal with this, without needing Polyline Solids or Soffits.

Can you post a picture of what you want? It would be fun to make a symbol for that.

But you might find this one sufficient:

https://3dwarehouse.sketchup.com/model.html?id=aa11b4cc60972d396412bca789fa2916

I'm still using X4 so therefore I'm getting a message telling me this is for a later version. Is there any way for me to use these symbols without having to purchase a later version? 

It would require exporting them (each symbol) from X6 to the 3DS format and then importing them into X4.  It can be done, but it's pretty time consuming.  I have X4, X5 & X6 all installed on my system but I rarely do any work in prior versions just because the latest version is IMO better.

I know this will sound foolish but try this:

1.  Undock the Library Browser and place it on a secondary monitor.

2.  Close the Library Browser

3.  Save the Plan

4.  Close the Plan and open any Plan

The Library Browser will be missing.

5.  Chief did exactly what it was told to do - but the user might not realize that they told it to do this.

Of course, when you add it back using the View Menu, it will be where you had it previously.  I would guess that someting similar is happening with those who are having troubles and say that the Library Browser is disappearing.  If that's true then it's operator error, not a problem with Chief Architect.

Maybe I'm wrong - if so, I apologize to anyone that's having a problem that isn't a result of the above scenario.

There are a couple of Brother Multi-function printers that will do 12"x18". 

Perry,

I just checked and it's not working for me.

Try this:

1.  New Plan

2. Create a 1st Floor

3. Create a 2nd Floor - slightly different plan

4. Create a Roof Plan

5. Send each of the above to Layout Pages 1,2,3,4

6. Display Layout Page-1 with the aerial view displayed.  It should show Floor 1.

7. Switch to Page 2,3,4 - in each case the aerial view still shows Page-1

8. Move or resize the aerial view - it should show the current page

They aren't doing something the way we are.  Maybe they're just testing to see if selecting a region on the Aerial View causes a zoom to the corresponding location on the Layout Page.  The problem for me is that the Aerial View doesn't update when the Page is changed.  I suspect that they are not checking that condition.

Also, if all their layout pages are identical then they wouldn't notice that the aerial view wasn't being updated.

Maybe we need to get them on a GoToMeeting so we can show them.  If not that then I can just call and try to explain what's happening.

Lew,

I only use such details for those things that need to be revised and should be revised based on the latest practices.  I always keep a set of as built plans for reference (prints) but any time I'm doing a new project based on an older set of plans - then I want the latest details according to current codes and practice.

This sort of thing is something that I as a user am resposible for.

The difference between a Layout and a Plan is basically just that the Views in the Plan are named Floor 1, Floor 2, etc. and in the Layout they are named Page 1, Page 2, etc.

My guess is that the software is checking for Floor to force the Aerial View update.  Should be an easy fix to add or Page to the code.