AW@WAdesign

I am also experiencing this problem. Will be retreating to my stable version of VectorWorks 2016 SP6 until the next 2018 service pack.

Raymond, thank you! Incredibly helpful. And thanks to your very helpful explanation, I was able to modify slightly to turn off the "project screen objects." Seems to work well in my files. Thank you and take care, Andy PROCEDURE VPProjScreenOFF; { Set "Project 2D" OFF for each ViewPort in the drawing. } CONST Proj2D = FALSE; { True = ON, False = OFF } procedure SetProj2D(H :Handle); Begin SetObjectVariableBoolean(H, 1005, Proj2D); { VP Project 2D } SetObjectVariableBoolean(H, 1035, True); { VP Display Planar } SetDSelect(H); End; { SetProj2D } BEGIN DSelectAll; ForEachObject(SetProj2D, T=VIEWPORT); { do this to each VP in the drawing } END; Run(VPProjScreenOFF);

If it's possible, it would be preferable to toggle these options on all viewports on all sheet layers within the file at the same time. (Global file operation as opposed to sheet based operation). Again, any help would be greatly appreciated. Thanks, Andy

Hi All-- I've discovered that I can navigate sheet layers with multiple viewports if I turn off "Project Screen Objects" however, I need to turn on "Project Screen Objects" when I print. I'm looking to create two simple scripts that will do the following: Fast View Mode: 1) Select all viewports on the sheet 2) Toggle ON "Display Planar Objects" 3) Toggle OFF "Project Screen Objects" 4) Deselect all Failed attempt: DSelectAll; SelectObj(INSYMBOL & INVIEWPORT & (T=VIEWPORT)); SetObjectVariableBoolean(122, 1005, False); SetObjectVariableBoolean(122, 1035, True); DSelectAll; Print Mode: 1) Select all viewports on the sheet 2) Toggle ON "Display Planar Objects" 3) Toggle ON "Project Screen Objects" 4) Deselect all Failed attempt: DSelectAll; SelectObj(INSYMBOL & INVIEWPORT & (T=VIEWPORT)); SetObjectVariableBoolean(122, 1005, True); SetObjectVariableBoolean(122, 1035, True); DSelectAll; Any help would be greatly appreciated! Thanks, Andy

I wish VW offered a simple, 2D drafting program as part of their suite of software products. Super simple, no BIM, no 3D. I use classes, design layers, and sheet layers to organize architectural drawing sets composed mostly of (gasp) lines and polygons with (gasp gasp) no 3D elements at all... Over the years I've watched my computing power get exponentially faster while my drawings have bogged down and performed poorly. I presume this is because they are enhanced with a significant amount of robust 3D power--that I never use. I've worked at four architecture firms in the SF Bay Area that have used various MiniCAD and VectorWorks versions over the course of 10 years. Not one has used 3D or BIM as a significant part of their workflow. I think there's a market for a lean, fast, efficient 2D drafting program for Mac based firms. If VW decides to offer it, please sign me up. Thanks, Andy

Alan, thanks. We do have "Save Viewport Cache" ticked. No improvement. We don't export from sheet views, but thank you for the suggestion. Kevin, yes, all viewports are in top/plan view. Agreed, the delays are not fun. At all. My employer just dropped $5k on a brand new "bear canister" mac pro in hopes that dual graphics processors would make this manageable. No luck. JimW, I have a feeling we're overrunning Enhanced Navigation Graphics. We've found that turning off this feature is the only way we can move around in the sheet layer. Turning it off at least allows us to pan, zoom, then redraw, as opposed to a slow, stuttering pan and zoom. I really hope that the VGM updates fix this issue. Tangentially related, is it possible to turn off all 3D features of VectorWorks? Is there a version that drops the 3D and optimizes the 2D? I'd welcome a simple, lean, fast 2D drafting program. Thanks! Andy www.wadesign.com VW Fundamentals 2016 SP3 (Build 301288) (64-Bit) iMac 3.2 GHz Intel Core i5 running OSX El Capitan (v10.11.3) 8 GB 1867 MHz DDR3, AMD Radeon R9 M390 2048MB

Hi All-- For some time now, our architecture firm has struggled with extremely slow detail sheets. On the surface, the detail sheets seem relatively simple--a standard sheet layer with about 16 viewport boxes showing a number of different details at 3"=1'-0". We could not figure out why they took so long to redraw, and we were losing time with every zoom and pan. We draw details entirely on a single class. They're all lines and polygons, and all drawing work is on the NONE class. All of the details are scaled at 3”=1’-0”. We use a limited palette of 7 or 8 hatches to indicate materials like concrete, gyp board, and the like. All of the line weights, line colors, hatches, etc are ‘forced’ (assigned individually using the Attributes palette). Pretty basic. Over the years, we've slowly built up a library of useful details from previous projects that we carry over to the next project. There is a lot of information visible on the NONE class in the design layer—perhaps a decade worth of details. This allows us to grab a window trim detail from here, a roof eave from there, etc. We’ve found that it’s efficient to build on and modify the library of details we’ve developed. We had assumed leaving the old detail info on the NONE class in the design layer wasn’t a problem, since we crop out the extra info in the viewport on the sheet layer. But here’s what seems to be happening: When you zoom out, Vectorworks renders ALL of the information present in the viewports on the sheet layer (even if that info is beyond the crop boundary). Only after VW has rendered everything, does it apply the crop box. This means that each detail visible on the sheet (16 viewports) re-renders everything on the NONE class every time we zoom out. We’re asking the computer to redraw a decade worth of details 16 times every time we zoom out, every time we pan, and every time we zoom back in. It’s frustrating to watch the fastest computers in the office hang as we attempt to lay out our detail sheets. Once we realized the problem, the solution was obvious. We’ve created a class called “OLD DETAILS” and a class called “CURRENT DETAILS.” Only the CURRENT DETAILS class is visible in the viewports. VectorWorks seems to recognize—and ignore—invisible classes when re-rendering the viewports. Why it can’t ignore items outside of a crop object is a mystery to me, but I’m glad to have finally happened on a work around. This forum has solved many odd issues for me over the years and I hope this post helps someone out there. Thanks, Andy www.wadesign.com VW Fundamentals 2016 SP3 (Build 301288) (64-Bit) iMac 3.2 GHz Intel Core i5 running OSX El Capitan (v10.11.3) 8 GB 1867 MHz DDR3, AMD Radeon R9 M390 2048MB