Jump to content

Search the Community

Showing results for tags 'cpu'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

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

Calendars

  • Training Events
  • Coffee Breaks
  • Essentials Seminars
  • Webinars
  • Community Groups

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 5 results

  1. Hi Vectorworks Team, Can somebody please paint an updated picture of which bits of Vectorworks and Renderworks use how many processor cores these days? It would really help us out with picking hardware specs. I assume most Vectorworks processes are now able to use multiple cores... How many should we be aiming for? Also please let us know any changes in the pipeline that might appear over the next couple of years i.e. enabling more processor threads.. Thanks! A
  2. Hi folks, I currently split my work flow between my desktop machine (i5-6600, 32GB RAM, GTX 970) and my Macbook Pro Retina 2012 (i7-3820, 16 GB RAM, G650M), but I'd really like to move to a smaller laptop. Everything I've read about Vectorworks hardware requirements suggests that you'd be a fool to attempt Vectorworks with any less than a 1GB video card, but I'm wondering how much of this is due to rendering? I use Spotlight to draw lighting plots and site layouts, and I'll simply never, ever use the Vectorworks rendering engine. Heading into a long summer tour, I'm looking at ultrabooks like the XPS 9370 or the Yoga 920 (both are i7-8550u, 16GB RAM, Intel 620 graphics) and obviously this would be considerably less capable for rendering, but I'm wondering what kind of experience I'd see if I simply never, ever leave wireframe or Plan view? Any advice appreciated. Thanks!
  3. I only use Vectorworks in 2D. I don't use it for rendering and i don't use renderworks etc. I am trying to understand whether Vectorworks 2017 uses the graphics card to draw or the CPU to draw vectored 2D. I have an 8 core CPU at 4.2Ghz but it really struggles with Vectorworks 2017. I think this is because VW is a single core process only in the drawing space and therefore performs slowly. Is this correct? The system requirements recommend at least 2GB dedicated graphics memory which i have. But is this only for renderworks? or is the graphics card used for 2D vector drawings? To get better performance in 2D (despite my current PC more than meeting the recommended specs) should i upgrade my graphics card or my CPU? many thanks, H
  4. We are probably investing in a couple of new computers soon and I'm wondering if the new AMD powerhouse will be a good processor for Vectorworks. We have done some in house tests on render times, and it is pretty clear that multiple cpu cores with as high clock as possible, and ram with high speed and timings have an impact on render time. Will Ryzen be supported? Ryzen have 8 cores and 16 threads, and supports memory up to at least 3200 MHz.
  5. Hi there. We use VW2017 to add electrical engineering features to architect issued plans. In a rather big project we get multiple 500 MB - 1 GB plans from the architect that we have to import and save as VW documents to be able to work on them. This happens a few times a week and it surely adds up time before we can work with those plans. As of now we are using the biggest baddest iMacs and VW2017 for the planing and even they slightly buckle when importing those plans. Trying out different MacPro and Mac minis we determined, that during the import process it's the clockspeed and the usage of real CPU cores that truly makes the difference. For example a MacPro 2009, 4-Core 2.66 GHz XEON on 8 GB RAM, SATA2 SSD with 10.11.6 and VW2017 will have around 2min 30sec to import a 10 MB .ifc file. We tested it with the standart GT120 (512 MB VRAM) and a GTX760 4GB and there practically no difference between them. GPU seems to make no direct impact at that point. Also it shows only the real cores under pressure, so no hyperthreading during import. So there are a few questions that need confirmation: Is the observation correct, that it is the clockspeed and the physical cores that really count during import? Can VW2017 actually use more than 4 Cores? How is it in WIndows 10 64bit? Will 32 GB RAM bring a significant boost against 16 GB RAM? Would a RAM disk containing the file to be converted bring a significant difference? We threw round a few suggestions and thats what we would go, if the before mentioned points can be confirmed: AMD Black Edition FX 9590 4.7 GHz 8-Core on a FX990 Chipset board, AMD RX480 (8GB VRAM), SSD, 16 GB RAM (or 32 if it really makes a difference) In the end we are aiming for the setup that will allow us to max out on the import process (within reason of course). Thanks for your input, your tips are really appreciated! Best Regards Thomas Alt
×
×
  • Create New...