Jump to content

Search the Community

Showing results for tags 'viewport cache'.

  • 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. Documenting in 3D with VW will get you pages and pages of Sections/Elevations (good!). However, if the viewport caches are not properly saved, then you end up with pages upon pages of blank pages with empty red rectangle frames (no good!). The problem here is not that we do not render our viewports often enough, it is that updated viewports are not synced properly across the various machines in Project Sharing. The end result after a few rounds of 'save and comment' is that we end up with blank viewports again across all the terminals. So, if a staff was expecting to 'fix up' something in an elevation we printed out, he would finds himself having to re-render that section/elevation in his machine, because there is no viewport cache. Unfortunately rendering a hidden-line viewport is not a quick process (will post a separate feature request for fixing this). VW has to better log which VP is the most recently rendered, regardless of when a particular terminal performs the 'save and commit' function. As an office that needs to produce drawings for issuance. This fix can't come soon enough. This fix really needs to happen NOW. (and if you were going to ask whether 'save viewport cache' is checked across all terminals. Well, obviously, yes)
×
×
  • Create New...