DrawingABlank

My goal for posting was for ridge "vent" quantity. I did leave out that key point when commenting on the reported values. I edited the original to clarify that. Your question is curious though... it seems that ridge cap is not a value that is usable in macro or other? At least not from what is in basic object properties for each plane. Of course this qty still reports in to materials though. Thanks for inquiring and being willing to assist.

Thanks. In cases around here the vent is actually held back some from the end and a 'one for one' cap = vent is not as accurate for my needs. So I was looking more at situations when ridge vent is selected as the default though. In a way the schedule results and reporting in text was my goal. In order to get the correct result knowing how the vent qty is achieved was important. (instead of just cap) Thanks for confirming that. Good point to keep an eye on it in some cases.

How does chief get the ridge vent qty? I did not find anything in the manual or in forum search. Two planes meeting at a peak of 40' length gives component ridge vent length result of 20'. It would seem to be allotting half of the ridge vent length to each plane. Could anyone confirm that or clarify? Thank you edit: reiterated topic title in the body by adding vent in reported results. Sorry for the confusion

I appreciate all three ways suggested. Thank you all. Having multiple suggestions not only builds my understanding of the specific task and macro use overall.

Good day, After searching over countless Macro topics, going thru 2 Ruby tutorials and many macro versions its time to give up digging / 'learning' for the moment and just post the question. How can a "floor_finish_name" macro that returns "Concrete" when no flooring is present be written? (extra credit would be if it also returns "Sub-floor" in case of being on floor system) This macro IF argument is needed cases such as defaults like Mechanical room and in rooms with default floor removed. The biggest challenge for me seems to be the syntax when wanting to call on Chief's string values from the plan. Any help in this regard is appreciated.

Of course! Overriding the Current CAD layer would not make sense. I appreciate the tip on closing the file prior to uploading. Next time... Thank you Glenn.

I created a CAD Block, set my preferred layer (not CAD Default) and then added to library. When the item is subsequently pulled from the library it reverts to the CAD Default layer. After searching, the Help files did not yield an answer or indicate any limits for CAD Block layers. This was in x14. This was reproduced in x13 so it would seem to be intentional. Seems to be a strange limitation on very basic library item. I will admit, it is possible that I am using these tools differently than intended. So... what is at play here? Operator error? Is there a better solution to have a ready made CAD 'icon' that starts on my preferred correct layer? For what it is worth, the CAD Block in question consists of a CAD circle and 4 lines. I tried changing the layers individually to the desired layer prior to creating the block and after with the same results. Thank you CAD Block Layer.zip

The chief save as pdf worked. Thanks Chopsaw. For what it is worth attached are the results. For science and prosperity I guess. One using Chief save as with no artifacts and the second showing artifacts using the cutepdf.

Thank you for the reply. Yes, the ghosting goes beyond the actual layout box/border for the image. I suppose saying the it is an artifact of the original size is probably better description than the term ghosting. I will try the chief pdf. Thanks for the tip. I guess at some point from x1 I had issues with Chiefs pdf printer and never bothered to try it with newer versions. What is also interesting is the construction lines on the adjacent elevation views are not being lightened while the cad lines are. (Same item sent to layout)

Any one have issue with this? I seem to have a an issue when sending Perspective camera to layout using 'current screen'. (I will call it the image) The the image is resized to fit properly on the layout page a 'ghosting' of the original size shows up after printing to pdf. (using cutepdf) It was apparent because the original image size ended up overlapping any other layout items. Creating lightened line color on the other layout items. Confirmed the source of the ghosting by moving the image on the layout and printing again. The ghosting of original size moved as well. It is not visible when previewing the pdf in print preview. Adjusting the images layer order does not correct it and may even ghost over the images actual visible area. I am unable to post the plan and layout sorry. Just wanted to put this out there while still fresh in mind. 2 attachments - one showing the layout box borders displayed and the other is showing the ghosting after it is printed to pdf.