Scott Dobbie

I believe I've found what the issue is. When saving 3d views the Unified View button on the menu bar must be on. I usually work with it off. If it is off, even if you have your settings in the Tools/Options/Vectorworks Preferences/3D tab/Projection when changing from a Top/Plan to a 3D perspective: any of the three perspective views selected, using the numeric keypad will only show orthogonal views with no transition. I've searched through VW2015 help; no mention of this required state of the Unified Views button for the "View transition animation" to work. Even the on-line videos trumpeting the new VW2015 feature mention nothing about it. However, the video does show the button to be in the on position. Who knew? SD

Just tried it again on new fresh file. Saved three 3d perspective views of simple object rendered in OpenGL using cameras to create views. Used saved view drop down list at top of interface window to switch between views. Still just jump cuts between views. "View transition animation" setting under Tools/Options/Vectorworks Preferences/Interactive tab is checked on. SD

I have VW 2015 Architect/Renderworks with SP2 installed. I can't seem to get the new 2015 feature "View Transition Animation" to work. When I select various saved 3d or 2d views it just jump cuts to the selected view, no 'tweening smooth transitions between views. The “View transition animation" switch is checked on under the Interactive tab in the Vectorworks Preferences control panel. I’ve looked in Vectorworks Help & online but I can’t seem to find any reference to any other switches I may have incorrectly applied or not to facilitate this feature. Is it hardware dependant? Anybody else out there having this problem? Scott Dobbie North Vancouver, British Columbia Canada Mac Pro 2013 3 Ghz 8 core Xeon E5 32GB 1867 Mhz DDR3 RAM Dual AMD FirePro 2048 MB graphics cards OS X 10.9.5 (13F34)

Having problems with a section viewport. Section viewport is derived from an front view elevation viewport. When I access section viewport to annotate, the machine becomes extremely sluggish trying to draw additional 2d lines, dimensions & notes in it. It's frozen a couple of times & intermittent flashing, ghosted, dotted lines appear from model points at a 45 deg. angle. This in VW 2014 Architect, all up to date, on my spanking new 2014 Mac Pro. The source model for the viewport is not overly complex. Anybody else experiencing this? Scott Dobbie North Vancouver, British Columbia Canada Mac Pro 2014 3 Ghz 8 core 32GB 1867 Mhz DDR3 RAM Dual AMD FirePro 2048 graphics cards OS X 10.9.3 (13D65)

..sounds like I have a corrupted file. So this is the project file that I've spent 2 months working on? What do I do now? The file is stored on local drives. I do incremental backups so I have copies of the file in it's chronological stages going back about 5 days. Should I apply for a research grant to troubleshoot this? This is so frustrating. I just want to get this job done.

Thanks for your reply. I re-created the sheet using your advice & it worked for the most part for about 12hrs. The same routine started happening with another sheet view, (at almost the exact time of day too... go figure), only now along with the warning, VW crashes when I edit symbols (symbols that shipped with VW). It also crashes now when I select a particular type of wall(created with the wall plug-in) & try to change the line weight. This program behavior reminds me of CorelDraw 7 under Windows '95. This shouldn't be happening. This is simple stuff. Is this a memory thing?

No, it's just in top/plan view & seems to be only on one particular saved sheet view. This sheet view was created by VW during the setup process in VW Architect. Could I recreate a new saved sheet view of the same thing? This warning box keeps returning in that sheet view, even if one zooms in or out, pan around, etc., no matter how many times one hits the OK button. I'm using VW Architect 10.5.1

I'm getting an error mesage coming up in a project file. It states: "One or more operations aborted due to lack of memory" This annoying box comes to the foreground, weirdly enough only in certain views? Is it relatd to saved sheet views? If I go to other views & work it's okay. What is this?. I'm running a PC 2.6 Ghz. SCSI U160 drives & controller. 512 MB RAM. File size is up there... 30MB. Using VW 10.5 Architect. Never seen this before... Anybody out there seen this?

Who knew? Looks like it was the KVM switch or one of it's cables. I've used the SmartView unit for over a year without a problem until I upgraded from VW/RW 9.5 foundation to VW/RW Architect 10.5. Then the "troubles" really started. I switched over to another unit that I have, a Mini-View CS-142 & voila' VW runs as smooth as kitten... go figure. Guess I won't have to apply for that research grant after all....

I'm using a Microsoft Internet Keyboard Pro & Logitech Optic Wheel mouse & the latest drivers have been installed for them. I'm also using a KVM switch between this & another machine. Might this be the issue with VectorWorks? It's a Smartview Intelligent IC-712-I model. It's a high quality unit I believe......

I did a defrag, un-installed the program, re-installed & it still does it. The only constant I can see so far is it seems to occur when I zoom in to something to edit or move an object. This is unfortunate as, of course, I'm working on a project for a client & this is wrecking my schedule big time. Should I apply for a research grant to figure this out? Computers are such time savers.....

I'm using VertorWorks Architect 10.5.1 on a Windows XP Pro machine. I can't establish a pattern yet, & this happens on any file, not just any particular one. While working on a drawing I lose the mouse & keyboard use. The keyboard won't type the characters I've input & the mouse behaves erratically. It only happens when I'm using VectorWorks. No other program I use does this. Even shutting down VW doesn't correct the problem. I have to reboot the machine. It can happen after as little as 30 sec. of use or as long a 2 hours. All drivers & Win updates are current.... Anybody else out there ever see this behavior? It also occurs on another machine of mine under Windows 2000 as well. Kinda' Mystified....