SHCanada2

i would make that upper window shorter you would have to go to 2:12 for a shed roof for some reason I cannot get the shed roof to auto build, but the above is what it would look like

91.5 + 1.5 +1,5+1.5= 96. So if one puts half inch drywall on the ceiling first aren't you short half inch when you go to put drywall on the wall?

there was a related suggestion earlier this year, which in my view, would solve all sorts of problems

rene, Joe looks to add things to a hash and then runs timers to add things up (presumably goes through the hash to add applicable fields) I add things to an array via a label, and then have a macro which runs through the array to add them up. The tricky part I have found is accounting for a removal of an object. I have a reset macro on the plan, which it looks like Joe has something similar. So i have two macros below, one in the window label, and one in the pline(elevation area) label then resize add a window:

interesting ...I think my macro in the label would give similar output, but I think if I remember correctly the label always has to be showing (even if it is teeny tiny) does your total update if you delete the wall, in say,a 3d view,.without going back to the view with the total or a plan view? that is always the limitation I have found ...unable to always trigger a refresh under all conditions...especially the removal.of an object as there is no "on_delete" event that I know of. The CA schedules are oh so close to being able to do this type of thing

or if you only need the dimension and not the coordinates, you can use a dimension and set the line type to none. then you can move the dimension label whereever you want either by moving the dimension, or the dimension label this is a dimension tied to the pline make the box bigger, the dimension changes with it and move the dimension line upwards:

I use, if available, a unique identifier and an array (could probably use a hash as well). For instance I add up all window areas on an elevation uisng a label in the window, but if the window changes size, one needs to not just add the new area, but replace/remove the old area in the summation. The unique identifier I use is the schedule number, and force the schedule to not duplicate. so if your custom object field is from an object that is "seen" (windows are seen on elevation and plan (asssuming the label is showing), I suppose you could use the same methodology

setting is here: I use different spacing for different font sizes/default sets

did you check the materials like I showed above?

and delete any embedded pdfs or images

I'm not sure what you are trying to do. Are you trying to use a result as the name of a global variable? If so I've tried that but don't remember being successful

if it is not supposed to be read only, you can click the properties of the file in windows explorer and change it to allow write privelges by user.

I bought a used XEROX 7800 DN phaser color printer for 11x17. ink is pricey, but I dont think I will ever need it, as the ink goes for 1000s of prints best $200 printer investment i ever made. it sits in my basement hooked to my network as it is not small

I use one layout, 24x36, and will sometimes print to pdf at 11x17 for speed( rtrt cameras are a lot slower at 24x36). The end user can print to letter or legal if they want to, that is my philosophy. I also put on each page that the scale is at 24x36.

they look to behave differetnly. below are both with the top right corner dragged. notice with the C key the extra buffer to the label c key: x key:

I think though, because you and I seem to be doing the same thing, if you send it to layout then crop the box, as long as CA does not reduce the camera width or height by more than the amount you crop, you would be okay/ Or put another way, if your camera was larger(width and or height) that what you really wanted, you then send that to layout and then resize using the X, then crop to what you wanted, you should be okay ...at least that is how I do it, I dont care that the camera is perfect width or height, as long as it is larger than what I want because I will enlarge and crop in layout

Keep them the same or change them in default sets i change the arrow size for different default sets: 1/4" 1/2"...should probably be 2.25

well, let me preface by saying what i am trying to do and so I am always on the lookout to see how people do it. I want to be able to send the cameras to layout and then not touch the cameras or do anything more with the layout. Because I want to change things in the plan, such as cabinets, fridge location etc, and just have the change show up in layout so i can pdf them to send to the client, or even for me to review. So i first tried sending the camera to layout but it showed up as a medium sized layout box (see the second image below), and when I went to pull the corner to make it larger, the layout box would not expand correctly(third image). So then I went to sending "screen as image" to layout and constantly resizing the image and constantly resending to layout whever something changed. Then someone told me the layout box will expand concentrically if I hold down the X key while dragging a corner, I then crop it to how I want...which results in the aspect ratio I want.Which is why when I saw your issue, I was wondering if you are doing the same as me, because I do not have the same issue, and I essentially choose the aspect ratio by cropping. I have these two on layout and I dont have to resend or export images. they update with the plan The only "remaining" problem I have is that to get the crispness of the image, I need to pdf the layout as ARCH D, if I pdf it as tabloid, is is not as sharp, presumably because CA is maxing the out the DPI at 300 (CA indicated such), and by having the larger sheet, i get more dots in my image. But that is just a guess. The only problem with this is that a full page ARCH D PBR RTRT camera takes minutes to pdf, while tabloid takes seconds. Send "screen" to layout: dragging the corner: uisng the X key while dragging: cropped: per first screnshot above Now other people have said they export the camera to image, and the layout is linked to that image. Its just a PITA in my opinion to constantly be exporting images. I asked CA to be abe to specify a DPI per camera. If they did that I think one could get as good an image as one wants through configuration, and pay whatever price one wants with relation to file size. And with the existing cropping ability one can get whatver aspect ratio one wants. which is why i was intrigued by your issue

in case i ever have this issue, from what to what did you change? thanks

thanks for the update, I did some checking on layouts, and do not see it change the apsect ratio for me. It keeps to the same size window filled that I sized using the 'X' key. is it only happening when you do this? : if so that would explain why i do not see it

most people use plot lines I believe for elevations plot lines live view live view with black and white camera plot lines:

download it from 3d warehouse and then import it into chief

This is normally what I want the behaviour to be. I might switch layersets to see other things (all on for instance) on a plan, but will go back to the one I sent to layout, and I might turn the odd layer on or off. To quickly go back, I actually just go select the saved plan view in the saved plan view drop down rather than trying to remmeber the one i was using If you use save plan views, I believe if you switch to a different layer set in the plan file, and then save that saved plan view, the layout will refelct the layerset, as the layout uses the saved plan view (if configured that way)

I had a post couple months back on this

to fo this, select the roof planes, then click the transform replicate button, and specify a positve number for Z. But really this should just build properly without having to do that. You might want to post the plan