Jump to content

nahekul

Member
  • Posts

    51
  • Joined

  • Last visited

Posts posted by nahekul

  1. When flipping or mirroring doors that are inserted into walls, the program seems to reverse the direction of the doors but the handing remains the same. 

    For example, the outward swinging door still says out but the graphics is showing the reverse. 

     

    However, rotating them seems to maintain the correct door orientation and graphics. 

     

    image.thumb.png.466d4bc3d6ce583ef23ddc9f7a773d3f.png

     

     

    Flipping/Mirroring works in symbols. However, once the symbol is exploded, the doors are reverted to the incorrect orientation.

    Interestingly, only the symbols that were supposed to be flipped are messed up (top right and lower left).

    The lower right one is correct. (I assume that even though it was flipped, that orientation was achievable through rotation so it is not messed up).

    image.thumb.png.f409afb07a4d0a7af0b8be112e6f345c.png

  2. With the update of 2024, the new feature of interactive handing was added. 

     

    This works well with the standard configurations but I can't figure out how to get it to work with custom windows with a center mullion. 

     

    In 2023, I can set up the custom window and flip the operable side to the left or right.

    In 2024, the operable side only stays on one side and I cannot flip it to the other side. 

     

    Even making 2 window styles, one with operable left and one with operable right, it does not show correctly once inserted into the wall.

     

    Screenshot2024-01-03at9_17_10AM.png.951e0fa02f582a3eda52664f588c43ab.pngScreenshot2024-01-03at9_19_12AM.thumb.png.8d5978efa89096fb1728ba669f225fdd.pngScreenshot2024-01-03at9_27_11AM.thumb.png.2b91922975378894067e3d3262a18807.png

  3. You are correct. I must have misremembered how this works before. 

    Exporting doesn't work for saved views when I try to select it. 

     

    The only way this works is to go to each saved view and export it manually using design layers. 

  4. We've tried using wall closures but the problem is we cannot control the colour of the wrap independantly from the cladding. 

     

    For example, if the exterior cladding is white, we cannot have the wall closure as dark. 

     

    In the image, the left window is how we want the trim to work. (Currently done with lintel as a workaround. This doesn't work with corner windows.)

    The 2 on the right is with wall closure with the cladding wrapping in, which is not what we want. 

     

    image.thumb.png.584a8680e5c063ef6f67410b528f5811.png

    • Like 2
  5.  

    9 hours ago, Tom W. said:

    You can change the size of the marker using the 'Scale Factor' parameter in the OIP but this will change the size of all instances of the marker so you need to create an unlinked copy of the marker

     

    Thanks Tom. That's what we'll do for now as a workaround. 

     

    15 minutes ago, Tom W. said:

    Sorry I see where we're misunderstanding each other now. I meant when you have the same Section-Elevation Line object displayed in multiple viewports: you change one instance of that object + all the others change as well. I thought this was what @nahekul was talking about... Maybe I should have said 'sub-instance' 🙂

     

    Yes, if it is the same section-elevation line displayed in multiple viewports, then the scale factor parameter affects all of them (in different viewports). 

     

    Matt, the video only shows that different section-elevation lines can have different scale factors. 

  6. 2 hours ago, Pat Stanford said:

    You can convert text fields to numbers using the Value() function, but not if there is non-numeric text stored in the field. So Value(19.09) will work, Value(19.09 sq.ft.) will not.  If all the text fields are formatted identically, it may be possible to extract just the numeric part to use in Value() using the Mid/Right/Left/Substring functions to remove the non-numeric parts.

    Thanks Pat, this worked great. Just being able to change the text to value helps a lot. The non-numeric text such as the unit marker can be added in the suffix in the cells so it's not an issue. 

     

     

    2 hours ago, Pat Stanford said:

    Or if might be possible to write a worksheet script that would give you the area of objects in a specific class or with a specific record attached that overlap the Space object.

     

    If this is possible, it'll greatly help speed up entering all the areas for each space manually. 

  7. On 3/27/2019 at 12:26 PM, Matt Panzer said:

     

    Glad to help! 🙂

     

    The "printed" size of the markers should be the same across viewports regardless of the viewport's scale. IOW, a marker seen in a 1:50 scale viewport should be the same size (as seen on the sheet layer) as the same section line marker in a viewport of another scale.

     

    Is there a way to change the size (or style) of the marker on different viewports?

     

    For example:

    We usually have a larger-scale viewport of the plan with the section markers at scale 1. 

    We want to show a key plan with the section markers at a scale of 0.2.

    How can this be done?

     

    Same with the grid lines and reference markers and tags. 

    Is there a way to convert them to world-based instead of page-based like it used to be able to do? 

  8. Is there a way to link another polygon's area or line length to the Space object's "net area" or "additional data" parameter in the OIP?

     

    This would be really helpful for area calculations and area exclusions that the municipalities usually want to see on the floor plans. 

     

    For example:

    Unit 201 has a gross floor area of 567.48 sqft.

    There is an in-suite storage room exclusion of 27sqft (drawn as another polygon)

     

    Currently, I am entering this exclusion manually in the additional data parameter (AreaPerOccupant) in the space object OIP

    Then I subtract this area from the gross floor area to get the net area in the database header. 

     

    Note:

    This is the only parameter that returns "sqft" as data in the worksheet database.

    All of the "Additional info" fields return a text data, and I don't see a way to change the data type

     

    If I can change the data type for the "additional info" fields, this would allow for more calculation options in the worksheet database headers. 

     

     

    image.thumb.png.7bafaac467652623367bf373d368b142.png

     

    image.thumb.png.215125d42a3133054a6f3b6d27935b7e.pngimage.thumb.png.8533a17644677519124b30d87e891546.png

     

  9. The stair objects does not show the control points to move the stair data when it is activated on the "top graphics".

    The bottom or "cut graphic" shows the control point to allow repositioning of the stair data just fine. 

     

    Selecting the different note options on the "top graphic" will show the stair data randomly but offers no way to adjust the position. 

     

     

    Screenshot 2023-05-01 at 10.01.48 AM.png

    Screenshot 2023-05-01 at 10.01.59 AM.png

    Screenshot 2023-05-01 at 10.02.27 AM.png

    Screenshot 2023-05-01 at 10.02.41 AM.png

    Screenshot 2023-05-01 at 10.02.55 AM.png

    Screenshot 2023-05-01 at 10.03.01 AM.png

    Screenshot 2023-05-01 at 10.03.08 AM.png

  10. On 3/10/2015 at 4:25 PM, Matt Panzer said:

    Sheet layer viewports can also be grouped, then scaled by dragging a corner grip. Since viewports must be scale proportionally, I usually hold the shift key to constrain the proportions. This will give you a proportional interactive preview as you drag.

    @Matt Panzer 

     

    This doesn't seem to work with VW 2021 anymore. 

    The viewport when scaled in group becomes blank.

  11. Regarding the new reference marker in Vectorworks 2021;

     

    Is there a way to link viewports to another Vectorworks files (similar to how the publish function works with multi-file publishes)?

     

    This is mainly because our office works with a separate details vectorworks file from the primary plan/elevation/section file. 

    It would be ideal if we can link the reference markers on the plan/elevation/section file to the actual details on the details file. 

    • Like 2
  12. Hi,

    Is there a way to create a filter definition that contains multiple layer names?

    For example, if I want to filter out layers that are plans, sections, and elevation, I can add multiple criterias similar to how custom selection is done.

    Currently, the layer filter only allows one entry of each definition, so I can only create a filter that separate out plans, or sections, but not both at the same time. 

     

    The current work around is to add 1 tag (eg. PSE) to all three types of layers and filter that tag separately.

    But this is not ideal since sometimes you want just plans and elevations or plans and sections. Then you need tags for those combinations as well. 

     

    image.thumb.png.e6686fe59430ae7c956b739e5bc186bb.png

  13. It looks like we may have found the issue. 

    The problem occurs on the elevation design layer. 

    On this layer, there are 24 viewports referencing back to the main floorplans (with lots of symbols and multiple layers turned on). 

    Moving these viewports onto another design layer and turning it off when drawing on the elevation layer solves the slowdown issue. 

     

×
×
  • Create New...