Search the Community

After two days of trying VW 9, encountered many bugs - you will no doubt work through them. Sluggish performance is not a bug - it's a basic design issue. 3D solid operations, doors and windows, simply changing the width of a wall object, all take unacceptably long periods of time. If you have a strategy to get back at least to the user performance of v 8.5, let me know. Otherwise, can't use VectorWorks in the future.

An operational detail which has been changed in V9, is the way the screen automatically scrolls when creating objects. So, drawing a line off the edge of the window automatically brings new terrain into view. It used to be that dragging the cursor off the edge scrolled the screen. Now, dragging the curson off the edge does not scroll the screen. Instead one must place the cursor in a particular (small) region for the scrolling to occur. Quick bold movements used to work and no longer do. Now, I have to get the cursor in just the right spot, not too far one way or the other. Now I overshoot and undershoot. So I have to slow down the motion to make things work. I regret to report that this looks to me like another example of some change that must have been seen as an improvement but in fact slows down the workflow. The cummulative effect of all these improvements is, for me, reduced productivity. Don't get me wrong, this program is on balance a very good CAD program. But I would like it to be a great program (it's got the right DNA) and the difference is, I think, in the subtle details of operation. These difficulties are not enough to compell me to return to 8.5, but in some ways working with the old version was more fun because I could really fly with it. Another oddity about the scrolling I've noticed, is that if a save reminder comes up in the course of creating a polygon, dragging the cursor to the "magic zone" does not scroll the screen at all. It is necessary to abandon the object and start over. Regards, Donald

Since "upgrading" my MAC to Snow Leopard & installing VW2010 from VW12.5, I've had nothing but problems when attempting to render. First, the system crashed. After some sage advice from GRANT PD (thank you Grant) I discovered a corrupt piece of my drawing and replaced it. I was then able to FAST RENDER. BUT when trying to FINAL RENDER, it is SLOW SLOW SLOW. When I try to FORCE QUIT VW is "not responding". Anyone else working on MACOS6 with VW 2010? I'm even wondering if my VW program is faulty.

Sorry for my lack of response, I've been away from work The media is on autoselect, however i've tried plain paper and nothing changes, it is still slow. I'm still wondering why its not every single drawing, but only every third that prints slow. Are there any adjustments made to the drawings that can slow up printing?

Your not alone. I had slow redraws and slow navigating. I hadto increase my RAM to 4 gig and I also replaced my video card. Here is the tech link you should read about all of this. http://techboard.vectorworks.net/ubbthreads/ubbthreads.php?ubb=showflat&Number=116110&page=1 Read all the messages till the very end. You'll realize you need either a very powerful video card and lots of RAM to utilize all of 2009 new on screen hints and aquisition highlighters. I turned off all the Interactive Highlighters in Preferences and it tremendously speeds of the program. But if you still slow, you'll need to upgrade to more RAM, a better video card, or finally a newer computer.

In regards to the huge file size, there is an option not to save reference cache to disk. This will reduce your file size, however, you will be required to update the reference when you open the file. For the slow down, here are a few questions: 1. What version of VW are you running? A detailed signature will be helpful here. 2. What exactly is slow? Reference update speed, DLVP draw speed? Could you please provide details? 3. Does the slow down happen always, frequently, or sometimes? Best Regards, Tolu

Hi David, Thank you very much for the sample files. >Thank you for confirming our suspicion that there is no way to >prevent VW from wasting time trying to find information from >remote files that is turned off in the DLVP. As I stated in my previous post, because layers from file 1 made it into file 3 does not mean that VW is reading them from file 1. VW will read and use the layers of file 1 that are present in file 2 if it finds that those layers are up to date. Specifically, when you update the reference in ?Untitled 3.vwx?, NNA#1#1_Design Layer-1 is read from ?Untitled 2.vwx?, NOT ?Untitled 1.vwx?. Furthermore, NNA#1#1_Design Layer-1 is an empty in ?Untitled 3.vwx?; therefore it is not a contributing factor to your slow down. As such, if you purge "unused layers" and run the script, you will not see NNA#1#1_Design Layer-1 listed because it would have been deleted because it is empty. I currently unable to determine what is causing your slow downs. If you are still seeing slow downs, I had be glad to take a look at your files and your server configurations. You can also contact tech support. Best Regards, Tolu

quote: Originally posted by Katie: Lett, There is a slowness of OS 10 overall that I've noticed. We have reports of VW crashing in OS 10 for no apparent reason, at least not one that we've been able to track down. On the other hand, I've also noticed other native applications crashing in OS 10 for no apparent reason. None the less, VW 9.5 and 9.5.1 shouldn't be running slower than VW 9.0.1. Have you made sure that everything, including drivers are up to par to match the OS version that you are using ? Does VW 9.5 and 9.5.1 run slow in OS 9 for you as well, or do they run faster in OS 9 rather than OS 10 ? About how much slower is it running ? When you experience this slowness, do you have your email on or is there another application in the dock that is taking up the processor usage?I've seen VW slow down as far as snapping or redraw when the email program was checking mail or another application in the doc was doing some behind the scenes work. Is the dock bouncing when you notice these slow downs? Katie, I have tried it without any other app running and it is still slow. I have noticed that it is really slow when I run it with iTunes playing. I've also been working on a large document lately. If the document is corrupted, then how do I copy it into a new document so that the file size is smaller. I have tried purging eveything and it is still a 10mb doc.

The slow OIP happens when you make an edit and then move the mouse. If you you wait to move the mouse until after the OIP has updated it will take far less time. NNA is aware of the details of the slow OIP problem and I expect a fix soon. As for the other issues of slow screen redraws. Here's the scoop. OS9 uses the processor to calculate the position of pixels on the screen. This rasterization of the file is not a simple task. Plotter software is slow for the same reasons, it is not a simple task. OSX asks the video card to perform this task. Most video cards processors are not as fast as the main CPU so the switch will affect the performance. What it boils down to is if you are running large files with new software on an old video card then you will have issues. I recommend using class or layer visibility to filter down the number of objects your trying to display and get a fast video card. As for the G5 not performing: the 1.8Mhz G5 is only 28% faster than my 1.4Ghz G4. That is not a perceivable difference. VW is not a 64 bit app or written for DP. So I am not sure why you would expect to be blown away. Once VW is compiled specifically for the G5, becomes multi-threaded and then you test it on a fast G5 like the 2.5Ghz you will notice an improvement. HTH Patrick

WOW, settle down, If it would slow down considerably the program, then it isn't worth it. The program that I learned to do this in, it wasn't a problem, it didn't slow it down. There isn't a huge amount of complexity involved. Simply applying the detail to the object. One plane/layer. It is projected through so that wherever you cut, you can see it. Not that difficult, not that complex, nothing to get worked up over. Like I said, not every nail, just a bit further than Petri showed. There are still more details that need to be added after cutting the 'simple' section. Degrees of complexity. This brings me to another point. I downloaded the 'BIM Best Practices' file from the NNA website. It ran incredibly slow. And there wasn't even any structural info in it. Is this file intended to be broken down and referenced multiple times (WGR), or is that it, a large clunky file? Am I missing something? Here are my cpu specs using VW 12.5.2 Machine Name: Power Mac G5 Machine Model: PowerMac7,3 CPU Type: PowerPC G5 (2.2) Number Of CPUs: 2 CPU Speed: 2 GHz L2 Cache (per CPU): 512 KB Memory: 1.5 GB Bus Speed: 1 GHz

If I try to open any more than 3 drawing at the same time VectorWorks becomes unusable, it took a few minutes just to try open the "window menu" to switch to another drawing and to try shut it down. Impossible to even draw a line or a rectangle. Memory usage in the task manager puts VectorWorks at 400,000k - 500,000k , when I manage to close the third drawing, the memory drops just below 400, and when second drawing drops to low 300s, things speed up a bit but still slow and unusable. VectorWorks just by itself (no drawings open) uses up 134,000k. I have to close down Vectorworks to make things fast again. This has only happened today (twice though), and different files each time, files in question are not to large, range from 5mb to 20mb each. Slow down only happens in Vectorworks, I can still use other programs and they run as normal. Using the computer in the sig on the left.

It is slow also when relaunched. When VW is minimized, the mouse is slow also on the desktop. It seems to affect other programs when minimized, but it is ok when I close VW. The mouse is slow in the sense that all acceleration seems turned off. I have a Logitech Marble FX ball mouse, and have to do a lot of turning to move from one end of the drawing to another. The mouse is not slow as it would be if the machine was hanging, or was running low on memory. And again, the stair tool does not work at all, but the spiral and ramp tools work just fine(!)

I did some investigating -- the application is larger on macs and when going from 12 0 1 to 12.5 due to the universal binary version of the application. However, the larger file size shouldn't slow down operations in VW. The only place you will see a slow down is when launching the application. Other factors that slow down the launch of the application are extensive libraries in the RB - each file has to load, the size of the file that is opening first (default blank file is small, however project files that are larger in size will require more time)

Hello forum. I wanted to gain your opinion. I am based in the UK and have used ACAD LT for 15 years. For several years I have been considering changing software and VW is at the top of my list as clients often want 3D views. i discounted Revit and ACAD Architecture on the grounds of cost and licensing. My work is mostly domestic extensions, some new build and a little commercial work - all fairly small scale but it earns me a living. I don't have loads of money or time to go on courses and do most of my learning from books whilst I work. I have spent some time mastering Sketchup this last year and have produced some good models which gives me a 3D model but it is limited in presentation as Layout is awful to use - very slow and very time consuming for detailed drawings. I don't think that you can produce construction drawings in Sketchup efficiently. I'm not saying it cant be done but I think it takes longer than it should. So I think that you need to combine Sketchup with another program to produce construction drawings but it seems wrong to me to be working in two programmes and switching between the two. The appeal of 3D for me is that the sections are automatically generated which can be a big time saver but I don't want it to take longer to build a 3D model than it would to draw the plans elevations and sections separately. I also like that when you move a window for example, the plans and elevations automatically update by default so you don't get inconsistencies between drawings. I have VW11 (Fundamentals) which I have never used. I was thinking of upgrading to VW Architect 2011 which will cost around ?1000. I am concerned that it will take me a long time to learn VW, it will slow my work rate down so that earning becomes difficult during the learning process and that it will not give me the end result that I am hoping to achieve. I would like an attractive 3D colour model with material renderings (not necessarily photo real). Being in the UK we do a lot of work with brick buildings, rough cut stone, roof tiles etc. Most examples of what I have seen in VW are shiny glass buildings with smooth cladding and render or siding. Will it produce attractive images for traditional English materials? In 2D I can produce a decent set of drawings in quite a short time period. I assume that building the 3D model will be more time consuming? I am hoping that you are going to tell me that it is easy to learn and as quick or quicker to use than LT.......and that what you tell me is true. I was also unsure whether VW2011 is more geared towards commercial projects than domestic or whether this is not an issue at all. Loads of questions, sorry about that, but I would welcome any comments that will help me decide to make the jump or stay as I am. Thanks.

I have the same painfully slow OpenGL performance in 2011. This is on a file that was created fresh in 2011 so nothing from 2010 to slow it down, and it has barely anything in it - just a few roof faces. Navigation in OpenGL skips and jumps around with all kinds of visual artifacts. After I changed the image of a RW texture, the old texture would randomly pop up on the screen while panning around. As if that old texture were stuck in some OpenGL buffer. I guess we need to post some videos on youtube demonstrating this terrible OpenGL performance so that NV can understand what we are complaining about. What makes this so frustrating is that other 3D software packages work perfectly fine on my computer with none of the OpenGL performance problems that Vw2011 exhibits. So I cannot accept that it is only because my computer is 2-1/2 years old: the problem lies with Vw's OpenGL implementation. Regards, Tim

Hello Katy: By slow I refer to the response of the menu as any of the main heading check boxes are clicked, such as "General Settings". The redraw of the menu is hesitant, unlike the standard Info Palatte display which pretty much responds to the click of the mouse. It appears that the hard drive is being accessed for each click, both for opening and closing a selection, thus causing the delay. If I recall, thereb was a similar Info Palette speed issue with VW9 and fixed in VW9.5. My Mac is running a 500 mhz G4 Sonnet card, VM off , 412 MB RAM and 225 MB dedictaed to VW. Thanks. ----- When you say slow, how much slower? Is it slow in loading, in making changes to the objkect, or how is it slow? What speed computer and OS are you using? Katie

This is very much a work in progress project. I was developing it last year, but I've since not had the time to finish it off. We regularily use it for creating new classes in accordance with AEC(uk)/Uniclass (Agent-Element-Presentation-Description-View) but it was intended for more general management of the classes. It works through copying and pasting to and from the excel file and VW Class & Layer Mapping Tool. I set it up to convert between variations of the AEC(uk) format, for easier selection during drawing or just simplified naming. Formats supported: AEC(UK): A-G25:JF1-G-WallBlck-Sec AEC(UK)SIMPLE: A-G25:JF1-G-Blck-Sec DESCRIPTION-AEC(UK)SIMPLE: A-G25:JF1-G-Sec (Blockwork walls) AEC(UK)SIMPLE-DESCRIPTION: Blockwork walls (A-G25:JF1-G-Sec) SA1-CODE/TEXT/AECUK: G_Bldg/2_FabCm-G25_Wall-:JF1_Blck/A-G25:JF1-G-WallBlck-Sec SA2-TEXT/AECUK: BuildElem/FabCm-Wall-Blck/A-G25:JF1-G-WallBlck-Sec SA3-CODE/AECUK: G2-G25-G25:JF1/A-G25:JF1-G-WallBlck-Sec If anyone is interested in developing this or if possible converting it to VectorScript please go ahead. I wish I had more time to get into it, but I'd rather put it out there than let it collect dust here. I have attached 2 versions. One with search enabled (very slow) and one without (not as slow). Any thoughts welcome. rename file from .pdf to .zip

Perhaps this is related to my earlier post about my demo 2011 RW not working, but having got it now working I'm finding Final Quality on Identical Models/Files with identical settings for lights etc... to be 3x longer in 2011 then 2010. I've tried with a very simple model; Four walls, One Roof, One Door and Four Windows, One Floor to represent the ground plane and one simple background, two textures, no lights- this will render in about 1.5 seconds in 2010 and six seconds in 2011 Then with a more complicated model, a Craftsman house project I'm working on with it will take about 2.5 seconds in 2010 and about seven seconds in 2011. Are we to compare 2011 Final Quality with 2010 radiosity? It certainly doesn't appear too different in quality with these simple settings. Playing with other files with higher quality parameters inputted seems to slow things down even more. I did increase my RAM recently but it is of the same specs, just another chip- and my video card is not among those mentioned as having issues. No crashing or anything, just slow renders. What gives?

We currently use AutoDesk TrueView on 'The Old Beige PC' we keep for non-Mac software, for checking DWG exports. It would be nice to have TrueView installed across the Macs in the office but we're hoping we can get a network licence for AutoCAD itself now it's coming back to Mac, as it would allow us to re-save our DWG exports natively. Not sure the iPad app will be of much use. I find that A1 size PDFs are rather slow to load on the iPad and a DWG would likely be just as slow. Nice to see them exploring this area though, for when the future hardware can live up to the concept...

we are running a 3 station network with the slowest PC running 3.0Ghz, winxp sp2 with 1 gb RAM and there is not slow down as you mention we have been using it for 6 months you may need to check out the Vectorworks preferences on the slow computers. things like vectorcaching and 2d accelaration there was no mention of the specs of the slow computers and settings of VW and WinXP virtual memory settings

I am still having problems with PAINFULLY SLOW keynote editing. I had always relied on them, but have had too abandon them on many documents because editing was so slow. I have to wait along time for spinning beachballs; even when creating the callouts from scratch- instead of copying and pasting. Dan Kocieniewski Vectorworks 2010 SP4 Mac Book Pro 2.5 Ghz Core Duo 4 Gb RAM Mac OSX Version 10.5.8

Hello Board, I'm a VectorWorks Landmark user since 9.5. Just got my upgrade not too long ago to 12. For some reason, I can't get tile to work anymore. I've installed my copy of landmark to my laptop and home computer just to test the tile function, and it does not work on any of the three. Vectorworks says it works as it processes the command, but... no tile. Does anyone have a workaround? Also, I enjoy tracing bitmap scans of preliminary design concepts and have done this with almost every design I do since I purchsed VW four years ago. With each release I hold my breath hoping working with large image files would get faster. Often, tracing a bitmap is painfully slow waiting for redraws with every pan, zoom, and drawing command. I now am the proud owner of a very fast dual-core opteron based system with raid, 2gigs of ram, high-end graphics card, etc - I can't hardly notice a difference dealing with bitmaps than my "old" 2.0 ghz machine with 512 megs of ram. In fact, I almost think V12 is slower than 11.5. Anyone have any ideas on how to speed the snail up? As a side note AutoCAD is smoking fast on my new machine... but I just love VW more... (frown). And lastly... I just got done "translating" an AutoCAD 2005 file. I can't believe how slow VW re-draws the file with every command - just as slow as working with a bitmap. I re-imported it no less than five times trying to work with different settings to speed it up. No dice. The file is not "huge" but did have over 30 layers and several blocks of trees, shrubs, and hatchs. But nothing major. Again, I swear 11.5 is faster at that as well. Any help there?

I have been using an HP455CA printer for over seven years. Originally it operated using the supplied HP RIP under OS9. I now use it under OS10.4 with the built-in system print driver utilizing GimpPrint. The printer has always printed slow under OSX. I recently upgraded my computer to a Dual 2.3 G5 with 2.5 GB of ram. I anticipated that the printing would be faster, but it is not. It appears that the slow printing is due to two reasons: 1. Slow spooling. The actual printing, or "ripping" takes very little time on the computer. But it takes many minutes for the information to spool. 2. The printer waits for all information to spool before printing. Under OS9, the printer would print during the spooling process. As a result the printer would print continuously, only waiting while the print dried before cutting. It would print while it was ripping. Currently it often takes 15 minutes to print one greyscale print. This is a tedious process to run any quantity of prints. So the question is, does anyone know how to speed up the spooling process? And does anyone know why the printer waits for all spooled info prior to starting to print? The printer is hooked up to a JetDirect Ex Plus which is connected by Ethernet to a Router and Switch.

Hi all, I know there's been a lot of posts lately on VectorWorks 11.5 being really slow (a lot slower compared to 11.5) but I want to be a little more specific here about what kind of slowness I'm experiencing. I don't know if it's similar to the Quicktime or upgrade issues that were already talked about. This is for the Windows version. So in VectorWorks 11 I had no speed problems at all. But after the upgrade to 11.5, I found that my menu (of all things!) and ctrl-based commands were very, very slow to respond. For instance I might click on the File menu and I can count to two or three seconds before something appears. Or I might hit Ctrl-G for "Group" or even something as simple as a cut and paste operation, and yep, there's that wait again before something happens. I wrote a vectorscript that allowed me to bind "Zoom Line Thickness" to a Ctrl-button. Also slow now, although it worked instantaneously in 11. But everything else runs very quickly. Zooming, panning, drawing, anything that I can rely on via a shortcut key (which don't utilize the ctrl button) or by clicking on the toolbar, functions just as quickly as it did in VW11. So the problem isn't that VW11.5 is slower overall--but for certain portions of it, it is. And I don't understand why, because it's not like these were upgraded in 11.5 (right?). Does anyone else experience this? Is there anything I can do? When I have to wait between commands it severely affects my drafting rhythm...

Adobe Air is very slow to install, give it time. Even the stand alone installer from Adobes web site is achingly slow.