Jump to content

Search the Community

Showing results for tags 'levels'.



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
    • ConnectCAD
    • 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 10 results

  1. Hello, Could someone direct me in which file I can rename default naming for stories/levels structure? Will new names work with symbols/walls/slabs/roof that are bound to stories? That is crucial part. Thanks.
  2. I don't know if this was proposed earlier, and if that's the case, just putting it up again. Wanted to request the ease of importing stories and levels from another file, or as a template, or choose to import part of stories from a different file more easily. This is especially the case if a referenced file uses stories, but the annotation file requires them to be added once more.
  3. So I have been using Roof objects as roofs and as ramps/slopes. I believe this is fairly common practice. Why on earth does vectorworks calculate everything from the bottom? We use Top of Ridge RL's, Roof Edge and Gutter RL's. Top of slope RL's and Bottom of slope RL's. Never in all of my architectural experience have I wanted to set the bottom of a sloped object to a specific level. When designing, the important features are on top of a sloped object. Apparently from the VWX perspective it is intuitive to set the bottom of the slope to the Top RL minus the cosine of the slab thickness to set the Finished Level. ??? It would make more sense to set the top of roof RL's that correspond with the top of the slope/roof, and let the roof thickness move down rather than up. Same for the slab tool. Why would I set my slab to -250 from the finished floor level and then add thickness on top of that. If I change my floor construction it just means that I have to get all my slabs and move them up or down. Surely it would make more sense to set a slab to the finished floor level, then let the slab thickness move the bottom down in the Z axis.
  4. I've created a hardscape by boundary, due to varying width and form - though the hardscape is essentially intended to be a path, and I need to treat it as such in terms of levels. I know using the roadway / pathway settings you can edit each point on the path to set the level and crossfall... is there a way to do this with a boundary hardscape? Essentially I want to be able to input the edge levels along the route in 3D, and then potentially make this a modifier for my site model. Is the workflow for this to edit a base site model, placing stakes at the required chainages, and then set the hardscape as a texture bed only? I'd ideally like to set the levels within the hardscape itself, and keen to use the slab settings within the hardscape to allow detail sections. Any help much appreciated.
  5. 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.
  6. Something I have been researching for a while and cannot find the answer is the creation of complex and easily created hardscapes, with the opportunity to have different elevations at each vertex. Much in the same way as you create a 3D polygon. One workflow might be: Create 3d polygon with different elevations at different vertexes > Create objects from shapes > Hardscapes Or Use stake tools to modify hardscapes in the same way they do a site model. This would improve the BIM workflow for Landmark immeasurably and move us on from simplistic modelling of external surfaces, to correct modelling which aligns with topographic information outside of our site and not under our control. Yes this can be created with site models but they cannot be utilised in the same way hardscapes can. Alternatively, If I have missed a trick here, please guide me in the right direction. Many Thanks,
  7. Is it possible to generate a set height contour for a proposed model? For example, I have built a proposed site model. I don't know the footprint of the lake on the on my model in plan, but I do I know the water level on site is 29.150. So, if I could generate a poly line at this height around the model, i.e. a contour line, I would be able to see the footprint of what will essentially be the lake and calculate area / volume etc?
  8. I have a series of stake points generated from existing levels to create an existing site model. I have now calculated the proposed levels, and generated another series of stake points, which I thought I could apply to existing to generate my proposed model. However, when I apply these new stake points as modifiers, they tie to the existing site model points and become 'spikes' in the existing model, rather than tying to each other. What am I missing with this? Can I set the proposed model data to ignore existing? Do I need to create a separate model for proposed? I want to be able to do cut and fill calculations, which is why I want to modify the existing site, but I don't know how to stop my modify points tying to existing data rather than just the proposed points?
  9. It would be good to have site model sections that automatically update with the model, and the annotated levels.
  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.

 

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