Jump to content

Search the Community

Showing results for tags 'story'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


  • In-Person Training - US
  • In-Person Training - UK
  • Coffee Breaks
  • Essentials Seminars
  • Webinars
  • Community Groups


  • Knowledgebase
    • Tech Bulletins
    • Troubleshooting
    • Workflows
    • How To
    • FAQs


  • 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


Last Updated

  • Start


Filter by number of...


  • Start








Found 5 results

  1. I wish roofs could recognize stories and their levels. I've got an addition project where I have two different plate levels. It would be nice to have the roof object recognize those levels. Thanks, Rudy Beuc
  2. 1. I think it needs a way to export Story and Level settings from one File to the other. And in current state, an Error Message when you try to send Story/Level bound Objects into another File, that this will not work. 2. Default Level should keep Linking. I think it is not good when you do changes and end up with lots of duplicates of Levels with same name, that will only disappear when you activated the current ones manually for each story, if you can ever keep overview. 3. Also I do not understand the Default Levels Naming hidden under Layer Organisation while in Story Settings you can edit their Z Values only.
  3. Please allow Stories and Levels to be imported into a new file. When confronted with a file that gets corrupted and refuses to open without crashing Vw, the suggested method to try and recover the file is to use the Layer Import trick (outlined in THIS thread). The problem with this method is that Stories and Levels are NOT imported; Any object that was either bound to a Level or a Story is broken as they do not exist in the new file. You end up with a bunch of objects in the OIP saying Top / Bottom Bound "doesn't exist". Stair objects refuse to be created. If the file is so corrupted that you are unable to open the file, you cannot see how the Stories and Levels were constructed. Which leaves you with a new file that is better than having to completely starting over, but not ideal.
  4. When creating a new Storey and a layer already exists for one of the Level Types we get the following message: "A layer named "example" already exists in the document. Please use a different layer name prefix/suffix" If there are no negative implications could we instead have an option to adopt the relevant layer into the Storey? "Would you like to adopt this layer? Yes/No"
  5. Is there a way to get a handle to the lowest Story in a file? For layers there is vs.GetFLayer(), But I can't find a similar way to get the lowest Story...
  • Create New...