Jump to content

Search the Community

Showing results for tags 'nohiddendata'.

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

  1. What we do currently is create a "line of heights" symbol then place that in the annotation space of every relevant veiwport. Knowing that the symbol can be updated one place and will show correctly in all places. We do the same with plan grids. The big problem here is that information exists in two places and one of them will be wrong. Someone changes the symbol but not the layer heights and the model is wrong, reverse and the drawings are wrong. This is a major problem as council holds us the written dimension not the overall look. So this is a source of co-ordination nightmares (ie wake up at 3am Sunday Morning then have sleep till arrival in the office to check and deal with) We did this before Storeys were introduced in VW2013 but thought well at least storeys shows promise. Then again before VW2013 getting usable elevations from a model wasn't as much a thing as it is today. Given Storeys has been upgraded many times to improve it's function why hasn't it been upgraded to present it's information on the drawings? This would make it both the easiest and correctest way to set heights in the project and anything not conforming to the information presented is most likely wrong. It would also vastly improve to busy work needed to get model to presentation.
×
×
  • Create New...