Jump to content

Python Scripting

Peer-to-peer Python script development support and exchange

134 topics in this forum

  1. vs.AngleVar()

    • 5 replies
    • 266 views
  2. Python vs C++ SDK

    • 14 replies
    • 1,370 views
    • 1 reply
    • 279 views
  3. EAP

    • 0 replies
    • 258 views
    • 8 replies
    • 536 views
  4. Dimension Standard

    • 2 replies
    • 402 views
    • 1 reply
    • 202 views
    • 4 replies
    • 558 views
  5. Error

    • 1 reply
    • 310 views
  6. access program settings

    • 5 replies
    • 422 views
  7. Question

    • 2 replies
    • 309 views
    • 4 replies
    • 362 views
    • 1 reply
    • 391 views
    • 5 replies
    • 788 views
    • 5 replies
    • 2,014 views
    • 0 replies
    • 226 views
    • 1 reply
    • 609 views
    • 0 replies
    • 224 views
    • 0 replies
    • 227 views
    • 2 replies
    • 373 views
    • 1 reply
    • 304 views
    • 4 replies
    • 750 views
  8. Don't Delete Resource in Use

    • 15 replies
    • 1,440 views
    • 0 replies
    • 288 views
  9. DeleteLayer

    • 1 reply
    • 334 views
  • Upcoming Events

  • Posts

    • All super valid input from everyone above. My latest file for an event was way over 2GB ..., and it slowed down my work processes a lot! So I learned that various settings help:   1. When I work on larger presentations then I purposefully separate corresponding VW files.    Keeping various VW file separate as "MASTER Files' e.g. main building, symbols, photos of the project, images for creative inspirations, etc.  And then --> creating 'Referenced Viewports on Design Layers' / 'R-VP -DL' within your current VW file.       Note - 'Referenced Viewports on Design Layers' don't import information from another VW file, and only provide the drawing in your working file, keeping the file size down.   2. Importing DWG's makes my VW files explode in size.     Check/uncheck at the import settings which elements you really need to import.   Also keep imported DWG files as separate VW files and reference them as 'R-VP -DL' . Or clean them up and delete all unnecessary elements prior to importing them into your file. Either in the separate VW file or in Illustrator.   3. Textures  These take up a huge amount of space. I usually reference textures on import. And then purge later on what I don't need any longer.   4. Some of imported furnitures I use from the internet have a huge amount of Mesh Geometry. Either I re-draw them if they are not too complex or I use  --> Tool - 'Simplify Mesh'  This will help to bring down the file size. Test it in a separate / empty VW file to see the size difference.   5. Sheet Layers & Viewport Renderings These take up a huge amount of space in my VW files. This as I do a lot !!!! of test renderings in order to compare and find the best RW Settings.   Once I am happy I usually duplicate the VW file ( keeping it as an Original and/or Backup file ) and then delete all unnecessary Viewports and Sheet Layers on my current VW file.   6. Publish to PDF Personally my main problem is when I 'Publish to PDF' for presentations from Sheet layers with lots of renderings. Then the PDF's are huge and I have to sacrifice on quality/dpi in order to reduce the file to a digestible size small enough for emailing my project portfolios to potential new clients whom I don't have an FTP accounts with.  
    • Thank you michaelk ! that was IT  
    • Had a RAM replaced on my computer and now Vectorworks 2012 won't open.
    • So it sounds like this is a confirmed bug, according to Service Select support it's something that Engineering is 'working on'....no further information provided.... In the mean time it's still incredibly frustrating since I'm trying to work on a number of very class-dense drawings this week....anyone found a work-around? Clean install of VW2018 SP4, brand-new machine, Windows 10 Home with latest updates, i7-7700, 32GB RAM, GTX 1070 8GB....
    • Make sure Unified View is off (in the View Menu)  
×