Jump to content

Search the Community

Showing results for tags 'slow'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
    • News You Need
    • Job Board
  • Feedback
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted / Issues Resolved
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
  • Customization
    • Marionette
    • Vectorscript
    • Python Scripting
    • SDK
    • 3rd Party Services, Products and Events
  • Solids Modeling and 3D Printing
    • Subdivision
    • Solids Modeling
    • 3D Printing
  • Vectorworks in Action
  • Archive
    • Resource Sharing
    • Machine Design

Categories

  • Knowledgebase
    • Tech Bulletins
    • Troubleshooting
    • Workflows
    • How To
    • FAQs

Categories

  • Marionette - Objects
  • Marionette - Networks
  • Marionette - Nodes
  • Marionette - Menu Commands

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Occupation


Homepage


Hobbies


Location


Skype

Found 11 results

  1. chrispolo

    3D Urban Model too slow

    I've been workin on this model from a while, and it's been difficult since the beginning with constant freeze and crash of the program, I'm actually using VW 2019 SP 2 in windows 10 Lenovo Y50-70 with i7 processor and 960M Nvidia graphics. My problem is that rendering the model to Unshaded Polygon and then export a viewport is taking forever and eventually the program get freeze, I'm using 150 DPI for the sheet layer. Somebody please help me I have no idea what is the problem, the 3D model has multiple extrudes but I expect my laptop can work it.
  2. I've imported a PDF. it is 11.6 MB. 4 pages, but I'm only taking in 3 of them. I've un-grouped the PDF. I've deleted the bitmap and a number of rouge rectangles. I also found that AFTER i've un-grouped the PDF, i'm left with an additional, 'hidden' group inside that group. I double click that group, and enter the group edit window. There, I have to manually pull the additional 'layers' from the PDF out to get to the line bits. Then I exit the group edit window and I have my layer of lines. in fact, I'm left with a really nice bunch of lines and polygons. About 700,000 polygons. I run a 'Compose' command on a bunch of them and that drops the number by almost 100,000. I'm still left with a bunch of polygons that have a fill associated with them. I need that fill gone. I've tried several things here, but the result is the same - It takes forever. If I do a custom select, and only select polygons that have a fill associated with them, I get a more manageable number of like 58,744 polygons. I move to the format pallet and choose the 'no fill' option. I get a beachball spinning for a long time, and the fill state never changes, and I have to apple+option+delete out of Vectorworks. By a long time, I mean hours on hours. If I do a smaller selection (like 15 - 20 polygons by tedious hand selection), or marquee select small sections of the drawing, I can change the fill state and it only takes minutes. Like 10 - 15 minutes. Still, to me, that seems like a really long time. My questions are this: Am I asking too much of the software? Is this 'expected' behavior in real world applications? Is there a better way to remove fills from polygons on a drawing? Is there a good way to 'pre-prep' a PDF for import? This PDF has no layers, and isn't that big. Working on my import PDF - turn it into a model workflow. So far, it's great. Except the underwhelming speed of the fill removal. The 'breaking apart' of the PDF takes a little bit of time, but not nearly the time that the fill removal does. Not by a long shot. Repro steps - Set up new drawing File-import PDF. highlight PDF. Apple+U to un-group Delete the rectangle and the bitmap so I'm left with just a singe 'group' item. Double click that group item. Enter the group editor. delete the various rectangles that represent the 'pages' or white space in the PDF. Exit editor. you're left with several 'blobs' or groups of PDF parts. In my case, I imported 3 PDF pages. Now I have three big groups of lines and Polys. Click the group of lines and Polys. Apple+A (yes, you are doing this a second time). Now you have a bunch of lines and poly's on your layer. Custom select: type = Polygon Fill = (solid black box in my case) Check OIP, verify there are like 60,000 polys selected now. click format pallet. on fill pull-down, select 'No Fill'. leave the office an literally come back in the morning. Might be done.
  3. Asemblance

    VWX 2019 Significantly Slower

    We've been doing some testing on some live projects, with the hopes to move things onto 2019. However disappointingly, we're finding 2019 seems to be significantly slower, with a lot of 'hangups' in between actions. In particular I've been noticing this going through and editing sheets. Doing the same actions in identical files on vwx 2018 (Sp4) is smoother and faster. This is quite the opposite from what we were hoping for! Has anybody else found this?
  4. ericjhberg

    Irrigation Tools...So Slow!

    When doing a large irrigation system (I'm working on several with over 70 stations), the connection time is incredibly cumbersome and slow. The file I am currently working on takes up to 15 seconds to make one connection. Additionally, we have already turned off the Auto Calculation Update feature, so that is just processing time. Some simple math to show you how cumbersome this actually is... 830 outlets of just one type (over 2000 total in the project) = 830 connections 830 connections at 15 seconds each = 12,450 seconds = 207.5 minutes = approximately 3.5 hours of drafting to make the connections. When compared to our traditional methods, we could do this drafting in approximately 1 hour or less. So for 2.5 extra hours, what do I get? Some data attached to the pipe network? That would be great, except half the time there is at least 1 error for every 20 outlets, which has to be found, diagnosed, and corrected, adding at least another hour to the mix. I get that we are supposed to be moving into the "smarter, not harder" category, but this is only coming at it from the "smarter" perspective while making it a whole lot harder to meet your targets. Expand your horizons Landmark and start thinking bigger than a single, lot residential project. We need BIG applications here that scale easily!
  5. Asemblance

    Push/Pull Tool Impossibly Slow

    Hi All, Bit of a problem at the moment - For some reason the 'Push/Pull' tool is impossibly slow in certain files. Generally speaking the file I'm working on runs fine, I'm able to work on it smoothly in Open GL mode and thats how I'm working for the most part. However, for some reason selecting the 'Push/Pull' tool causes my system to all but freeze up (in any rendering mode, including wireframe). If necessary I'll record a video, but it basically shows the following: - 2 Storey building with some simple doors, windows, stairs, a couple of references - Roaming around and spinning about smoothly in 3D in open GL - Find a simple cube which I want to extrude a little - Select 'Push/Pull' tool - Move mouse over to cube, but sit watching 'spinning wheel' of Mac loading for about 5 minutes. - Nothing happens, give up and deselect. After another few minutes, system will unselect the Push/Pull tool and file works fine again. Any ideas? Is this a known issue?? Thanks, A
  6. Hi, 2018 keeps driving to a complete unusable halt in my sheet layers after introducing a 3rd or 4th viewport. My drawings are pretty light and are not too complex and only rendering in wireframe (to consider another rendering format is unthinkable) the program then becomes unusable with massive delays, jerky zoom and content disappearing when zoom is halted. The same file in 2017 works fine, is this a known issue with 2018? A quick check on the system shows CPU running @6% and RAM only @ 8gb of 16gb
  7. Hi, I am finding that after ~30mins of using Vectorworks 2017 & 2016 the redraw rate and the object info boxes flicker and the program becomes really slow. Changing between tools and moving objects around the screen is laggy to the point where it affects my workflow. Text boxes are almost impossble to work with as i can't select text or move text without waiting a few soconds per operation. I would like to think that i am running powerful enough hardware to not have a problem but clearly something is not right and i can't seem to track it down. I phoned up the Vectorworks support line and they tried to fix the issue but to no avail. The girl was very helpful but basically just changed some of the graphics properties within vectorworks which made no difference. It does not matter how large or small the file is, how complex or how simple the geometry is. I am working only in 2D plan. Sketchup, 3DS Max, Photoshop, Illustrator, Premier Pro etc. all work absolutely fine without any issues but AutoCAD suffers the same issue. I am hoping someone else had had the same problem or knows where i can next look for a solution. My specs: AMD FX 8350 CPU (8 cores overclocked to 4.7Ghz) AMD radeon R9 270x 2gb dedicated RAM (this is a dedicated graphics card) 16GB Corsair DDR3 1333mhz ram both programs are running on an SSD (samsung 840 pro) ASUS TUF Sabertooth 990FX R2 motherboard Windows 10 2 screens @ 1080pi each. i would be hugely grateful to anyone who could shed some light on the problem. I am not sure how to track down if its a hardware issue or a software issue. Many thanks 402-102-B-GroundFloorPlan.vwx
  8. Hi, We have been attempting to use the new data visualization tool, which clearly has the power to become very useful. However we are having some difficulties. Firstly, even using this tool in a basic way seems to cause extreme slowdown. Secondly (and more critically for us currently), the display for some areas seems to be buggy and 'stuck' on an incorrect hatch colour. Please take a look at the video below which shows the issues. The beginning of the video shows how quickly our systems handle navigation on a normal sheet without data visualization turned on. The second sheet shown is using simple data visualization to show space objects with various coloured hatches applied. You can see how much more slowly this sheet refreshes as zoomed or panned, which is infuriating to work with. But the area which is coming up as as a black hatch at most zoom levels is the most problematic. This type of issue has cropped up on a couple of our drawings, and is still present on pdf's if printed at this scale.
  9. dinga

    Rendering Times

    Hello everybody, First time posting on here. I did a quick search but really didn't find too many answers. One of my end users builds a lot of large music festival designs in his VW (currently using 2017). He primarily uses the Hidden Line view for all his stage plots. Each page has a different stage and each stage has about 50-100 lights, a stage, a roof, barricade, video walls, and stage risers. Basically, a lot of stuff haha. He was doing this from his MBP and was working pretty good until the designs got bigger and bigger. Currently we have built him a nice little setup an i7, 32GB of ram, and a GTX 10 series GPU. When he publishes in Hidden Line mode the render times take well over an hour. The system memory has peaked at 28-30GB and the GPU load currently sits a 0%........ What can we do to get some of that work load moved over to the GPU? I understand that the openGL render will help offset that, But the openGL view will not work for what he is trying to accomplish. He needs line mode so each light and device shows up in a nice sketch up view with all the names, labels and positions associated with those devices next to the device. openGL mode takes all of that stuff out of the render and that information is more important than the actual render itself. Is there a way to have the Hidden Line mode render through the GPU? Is there anything we can do to speed up the Hidden Line render mode? When we render via openGL it works very nicely, just baffled how a Hidden Line mode takes longer than an actual full color render takes? There HAS to be some way to the GPU to help the render speed on this, right? Sorry if I'm not cleat enough on all of this. I'm more of a computer tech and our end user is too swamped to reach out so I'm trying my best to help Thanks for any help you guys can pass my way. Have a great week! *On a side note, does VW work better on multi cores, or a very fast single core?*
  10. MRD Mark Ridgewell

    VW2017 file unresponsive

    I’ve got a vectorworks file that’s become very unresponsive/ pretty much unusable. It’s 151mb – is that just too big? It's only one floor so no complex stories or layers going on. It’s a 3d model with some renderworks textures, 3d objects (as symbols), and lighting, but even with these classes turned off it makes no difference. It was created in VW2016 originally but I’ve recently set up viewports on about 10 sheets using the ‘create interior elevation viewport’ .There’s about 30 sheet layers – is that too many for one file? What's the most efficient way of working out what is slowing it down so much? Suggestions appreciated so I can get drawings out from this file later in the week!
  11. Hi we just bought a new Imac and installed the new Landmark 2017 . The software dosen't work correctly... even a smal file ( 10MB) ist extremly slow! Any Idea what's wrong? Thx Laurent

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×