Jump to content

Search the Community

Showing results for tags 'door tool'.



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
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
  • 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
    • Terms of Service and Community Guidelines

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 12 results

  1. Hi, I need to draw a double door set, similar to the image, but without the fanlight, so full height double doors with side panels...any ideas?! thankyou!
  2. We need more options for displaying ID tags. For instance to be able to display the fire-rating of a door (separately from the door ID). WinDoor has some good examples, see below. We also need support for superscript and subscript as some nationalities utilise these for fire-ratings.
  3. We need support for bi-folding sliding doors. There shouldn’t be any limit to the number of configurations (i.e. please don’t use a drop-down list of options, use a Custom Door Options graphical user interface instead perhaps). Examples of common bi-folding sliding door arrangements:
  4. We'd like to get rid of the “complex door” XOXOXO drop-down menu and replace it with something more akin to the Custom Sash Options interface in the Window Tool.
  5. The separation of the window and door tools poses a problem for scheduling, visual accuracy and editing. In the real world doors and windows are usually part of the same unit, especially for external units. So we need to be able to define doors and door thresholds as part of window units (or "external opening" units) separately and in addition to the window sash/sill settings. This is probably my most wanted enhancement in Vectorworks. JIRA reference: VE-97948
  6. We should be able to define a ‘Fitting Gap’ for the door leaf (gap between jamb and leaf), which is typically 1 to 3 mm either side of the door and may include smoke seals or weather seals. If this gap is not supported then we have to make the shim gap or the casing the wrong size to compensate, which apart from being visually wrong also means we can’t schedule accurately. For the same reasons we need to be able to define the gap between the door leaf and floor. As well as being able to define the shim gap to the top of the door separately from the sides, as this can often be different. UK defaults should be as follows: WIDTH DEFAULTS 7 shim gap 32 casing 3 gap 826 leaf 3 gap 32 casing 7 shim gap = 910 Wide Structural Opening HEIGHT DEFAULTS 15 shim gap 32 casing 3 gap 2040 leaf 20 threshold gap = 2110 High Structural Opening ARCHITRAVE SIZE DEFAULTS The default architrave (trim) should be of the following size: 19 x 69
  7. We need the door tool to support frame stops. These can be both planted or rebated, as attached image. We need this for a number of reasons: Correct visual representation in 3D and 2D views The ability to visually check that we're providing the correct clear opening For accurate scheduling
  8. 1. We need new fields added to the Leaf tab of the Door Tool Settings to deal with Meeting Stiles. Double door meeting stiles have five common arrangements as illustrated below, which are square, rounded, rebated, astragal and T astragal. An astragal is a timber profile/molding fixed to the secondary door leaf to act as a stop. 2. The object in the current version of Vectorworks called "Astragal" is not an astragal and should instead be called a Fixed Mullion. An astragal is in fact a holding that attaches to one of the leafs and closes the gap between the two leafs when closed (see above).
  9. Support for louvre vents in the Window Tool is welcome. Now we also need them for the Door Tool, which is the majority use case for us.
  10. We'd like custom ID tags for windows and doors. One of the main reasons we need them is to display the fire-rating of doors on floor plans for instance. We used to use symbols for doors, including our own custom ID tag (linked to a record format), and this included a fire-rating field. But now that we're using the Door Object we don't have this capability. The fire-rating is there in the door data but we're unable to display it as part of the ID tag, because ID tags are limited to ID Prefix, ID Label and ID Suffix. You might say that we could use the ID Suffix field to show the fire-rating but we already use this field to identify a door type (and the fire-rating is already has its own field). So a typical door number for us would look like this: D-09-B (D=door, 09=door number, and B=type) WinDoor, for instance, has custom ID tags, which are symbols the user can edit. They also have a second field that you can use for any piece of data you like, such as the fire-rating.
  11. As we can with Symbols I'd like to be able to define the Wall Hole Component of Window and Door Objects, so we can more easily model modifications of the wall that are associated with a window/door.
  12. We need to be able to generate a live 2D front view representation of doors and we need to be able to dimension them with associative dimensions. We’d also like to be able to edit/override individual line-types and line-weights as you can with a viewport.
×