Jump to content

Search the Community

Showing results for tags 'best practices'.

  • 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
    • 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

  • Community Calendar
  • Training Calendar
  • 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 3 results

  1. Hello, I’m wanting to start to push the boundaries of what can be done with Vectorworks, and am seeking direction for best practices, Scripting resources, and or any additional materials that you may deem helpful in this endeavor. Really looking to program repeat tasks and sequences that I currently use in my daily workflow. And I would like to be able to develop a customized “super” template that has a centralized repository for all future drawings to save time on production efforts. Which language should be best utilized from a programming point of view, and is there recent documentation for the most current release? Thanks, Ryan Russell
  2. Another one of those, try, try again until you succeed posts. I posted this awhile ago and included a video, to no avail or answer yet. When using the new irrigation tools, once a pipe is drawn and components are added to it, there is no way to rotate the graphic symbol other than to a true north. What is interesting is that the OIP will show a rotation angle even though the graphic symbol doesn't rotate. You can see the video for a better explanation (sorry, no voice over). https://screencast-o-matic.com/watch/cDX33GQh5g This is really annoying because we almost never get so lucky to work in a true north orientation and our best practice has always been to relate system components and their rotation to the line on which they are placed. It just adds graphic clarity. This problem is also true of any tags or labels that are created from an irrigation object. They cannot be rotated so as to appear horizontal on a sheet layer viewport. This is common practice and I don't understand why the usability hasn't been integrated. We have largely avoided the entire irrigation suite, and this problem is a large reason why. Fix please!
  3. Recently I've been working with a lot of AutoCAD files. Obviously as a native file, navigation/editing/modeling functions all perform very well in AutoCAD. But when I try to import the DWG into VWX2017, it is crazy slow and unmanageable. FYI - a 75MB dwg file turns into a 400+MB vwx file. I can tell this is caused by VWX turning AC objects into thousands of polygons. Being more comfortable in VWX, I would like to work there. Are there any DWG import settings that will cut down on the "thousands of polygons" issue but still retain the models integrity?
×
×
  • Create New...