Jump to content

Search the Community

Showing results for tags 'stories'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
    • News You Need
    • Job Board
  • Feedback
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted / Issues Resolved
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
    • Hardware
  • Customization
    • Marionette
    • Vectorscript
    • Python Scripting
    • SDK
    • 3rd Party Services, Products and Events
  • Solids Modeling and 3D Printing
    • Subdivision
    • Solids Modeling
    • 3D Printing
  • Vectorworks in Action
  • Archive
    • Resource Sharing
    • Machine Design

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


About Me


Occupation


Homepage


Hobbies


Location


Skype

Found 11 results

  1. I would like to suggest some improvements to levels. The first and most important thing would be a simple list of levels, displayed in the navigation palette. This list should contain all the information belonging to levels. In this list you should be able to create, edit, copy, paste, duplicate, delete and replace all levels. All operations regarding levels should be possible from this list view. Especially copy and paste from one story to another. There should also be a mechanism to export levels to another file. In this case you would simply go to the level list, copy any desired levels and paste them into the other files level list. In order to move a level from one story to another you would simply drag it in the list, if desired also duplicating it by option-drag. If you want to get rid of a level you should be able to delete it from the list. In that case, there would be a dialog similar to the one, when deleting classes. This dialog should allow you to define a replacement level for the one you are about to delete. Default Levels are nice to have, but not mandatory, because it would be really easy to create a new level. Step 1: From the popup menu select "Create New Level" Step 2: Enter Name and Height (relative to story, layer or absolute height) Step 3: Drag it to the desired layer or story in the list. Finished. There is no step 4. There is a mock-up of the level list to illustrate the concept. (Bear with me there are some typing errors.) When connecting objects to levels pretty much the same list would be displayed in the form of an pop-up menu.
  2. Hi, I would like to know if everybody ese is having this problem or maybe I'm just understanding incorrectly how structural member work. When working in a file that has stories and levels adjusted, I create a structural member and when trying to adjust the Elevations (start bound, start offset, end bound, end offset) the structural member simply does not obey the levels I'm assigning to its boundaries. The element changes height inconsistently, this happens if the element has been drawn as a beam or column. I would appreciate if someone can tell me what I'm doing wrong or maybe it's just a bug and we need to wait for a service pack.
  3. Hi, I struggling to understand the best way to place my site model with respect real world elevation (feet above sea level). If my base elevation for the project is 150.0', I am currently setting Story 1, Level: "Finish Floor" to 150'. Is this even right? It feels a little weird to have the whole project floating so high up above the XY plane. Should Story 1 start at 0", and the design layer start at 150'? I then wonder if I should also relate my site model's design layer with respect to Story 1. Currently, I'm placing my site model on a design layer that is not attached to any story, and set to a 0" elevation. The Site model topography is drawn at its real world values, so the whole model floats up above along with all the story related building assemblies. Anyway, I would really love some feedback on what the best practice is for all this. Thanks! Matt
  4. Wish We'd like support for split levels built directly into the Stories feature. Reason As it stands we currently have to use Level Types to create split level building models (and multiple buildings in one file with different elevation heights) I don't think Level Types is logically the right place to provide this capability It means that any standard Level Types you'd typically have in a model need to be multipled by the number of split levels you have, which creates unnecessarily complex lists of Level Types If we want to control top and bottom bindings by Wall Style it means multiplying all our Wall Styles Or it means we can't copy a wall across from one part of the building to another without being forced to redefine the top and bottom bindings to suit that level Possible Solution Story Groups Each group of storeys could have its own elevations defined independently of other storeys We could then define Level Types that would work across Story Groups (e.g. FFL-0 would be the same definition across split levels, and the Storey Group would control any elevation height difference between split levels.) Which means we could have Wall Styles with top and bottom bindings defined by Level Type that work across split levels Or we could copy a wall from one split level to another and not be forced to redefine the top and bottom bindings Result The result, when dealing with split levels, would mean less Level Types, less Wall Styles and less manual manipulation of top and bottom bindings
  5. Greetings Something to ponder over the holiday: I have a 7 story mixed use building created in 2010 (i.e. no stories) It was a developed schematic design (all floors modeled, elevations and sections taken and rendered) Many duplicate apartment units which I made into symbols with some strange elevational results but it all held together for what was needed. 7 or 8 years later (now) the project may be coming back to life. I suspect many changes will ensue including story heights. I spoke to VW support and they suggested that I not move to stories due to the complexity of transferring the model layer by layer and the complicated setup. I currently use stories for literally everything (even single story additions, even though levels and walls can be cumbersome at times.) I have found when it works, the results are a real time savings. Anyone have any experience/thoughts/insights on something like this? Steve Steven Glickman Architect 400 Northampton St, Suite 500 Easton, PA 18042 V: 610.253.6536 E: stevenaia@gmail.com http://www.stevenglickmanarchitect.com
  6. On the hunt for a concise intro. to stories.... Got the overall idea, but all seems so over complicated. Must be missing something...
  7. I just made the mistake, against my better judgment, of setting up a project with different layer z values for different stories. What a mess it makes of my work process - and all because of one crucial, missing bit of functionality. Let me give an example: I have maybe 100 surveying stake objects from a survey on a steeply sloping site. I can't look at these objects from the side and tell which is which (labels from side view wish?). So I copy a particular locus, and paste-in-place on the appropriate layer to see if my measured floor finish corresponds accurately to the floor level of a particular story in this 4-story structure. Guess what - because of layer z values, that object does not paste in at the correct height. It pastes in with respect to the layer z value of the layer I am working in, not the z value relative to "world z". If we could have the option to paste in place relative to world z, that would be a great help and I could use the "story" structure that VW promotes as a major feature. I use paste in place across layers very frequently, maybe a dozen times a day for various purposes. I would post this in the Wish List forum, but I don't see that in forum navigation - does it no longer exist?
  8. Hi, I am having trouble with elements of my building model not appearing at the right height within a referenced file. We have a particular file set up within the office where the model is located within one file and then referenced into another file to create drawing sheets. The main model file is set up using stories within the design layers. When the file is then referenced the second file is unable to locate some stories (but not all). I have manually introduced stories to the second file to match, but this still doesn't work. Can anyone help?
  9. We are shifting our workflow into using stories. In past multi-family-residential projects where many units are the same, we've put these units in symbols so that we can make wide scale changes to them. However, when creating a symbol of the units with wall styles bound to story levels, the walls show up as having no height. There is a story aware checkbox in the create symbol dialogue box but I'm unclear to what it really does. Do styled walls work within symbols or do we need a new set of unbounded wall styles? Any tips relating to multiple unit type arrangements using stories would be appreciated.
  10. Vectorworks should have the option of not only Stories and Levels but also an option for Buildings. With "Buildings" on would be able to group stories and levels to buildings. This would allow more organization and control when working with buildings or structures in the same file that have different stories with varying levels.
  11. Gosh these stories drive me crazy, my walls and the windows in them are not based on the same heights, I think i need a fresh set of eyes here. Thank you Amerchem_exist.vwx

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×
×
  • Create New...