Bill Carter

Katie, Thanks for your reply. Based upon what you've said, it doesn't make sense to annotate viewports because text, dimensions, etc. would be "left behind" when referencing only the design layer - hence, the annotation feature of viewports is not so useful. Also, if source material on a design layer to be displayed in a viewport is at a different scale than the intended scale set for the viewport, this is not of much use for workgroup referencing purposes either. Please let me know if I am wrong in these conclusions. As usual, thanks very much for your help and insight into all our questions. Bill Carter HKTA/architects

It appears that we cannot workgroup-reference viewports from one file to another. Would Katie (or anyone) please address this? If there is a method for doing this, that would be great. Thanks.

It would be very useful to have the option to batch print to PDF's or postscript files rather than directly printing all, or a selected number of sheets to the plotter. Quite often we will finish a job and create PDF's to give to our print service. We have always done them one at a time, and while still faster than plotting to the office HP, a batch postscript or PDF command would speed things up even more.

I wonder if anyone else who uses Artlantis with Vectorworks 11 has found that in order to export a 3d model to Artlantis, the model has to be displayed in a layer link rather than a viewport. If a 3d view is displayed in a viewport, the Artlantis Export command can't find an object to export. A 3d layerlink on screen exports as it has in previous versions just fine.

I haven't yet figured out how to get a ceiling grid to center in a space. Is there a trick to it?

Robert, Thanks for your reply. Good to hear that it will be fixed.

On 2/25, Chris T wrote about the unfortunate results that occur when sheets are added (or removed) from a file. Interestingly, no one answered this. I would like to bring it up again, because it really is a problem that I would like to see NA respond to. The fact that class settings are reset to their defaults is significant, especially toward the end of a project's schedule when there isn't the time to fiddle with changing things back. I think that in VWA several versions back, several other unwanted results occurred also, such as extra sheets being added out of the blue. Having the capability of adding or removing sheets is a very useful feature, but it doesn't seem like it is yet ready for prime time. Robert, can you help out here? Thanks.

Robert, Kristen got it right - your explanation needs to be in the manual. You've been a tremendous help. Thanks again. Bill

Often we need to work on large buildings with many spaces. This generates many window, door and room symbols or objects. Unfortunately all these objects are attached to the single window, door or room record that is created to link these objects to their respective schedules. When the schedules are set down on their respective sheets for plotting, they run well off the bottom of the sheet because they are so long. I have taken to creating additional records and schedules (Door Record2, Door Schecule2, etc.), along with additional objects attached to these new records, and this works up to a point. Unfortunately I can't use the Room Name tool and the Assign Room Finish tool to operate on the objects attached to the new records. In order to assign room name and room finish info I have to manually enter all information in the OIP's Data pane for each secondary window, door or room name object. Obviously, all objects in the drawing attached to the first or default records can take advantage of using the Room Name and Assign Room Finish tools, but once the number of these legitimate objects is such that the schedules they are on reach the bottom of the drawing sheets, all other objects have to be assigned to the alternate records and manually fleshed out - a tremendous waste of time. To make matters even more complex, occasionally some drawing action will inadvertently reassign the default record to objects assigned to the secondary record, and then the objects start showing up on several schedules. I've spoken to a tech representative about all this, but there is no help forthcoming apparently. I would like to know if anyone else has developed a clever way to handle long schedules. Thanks.