Jump to content

RMcK

Member
  • Content Count

    31
  • Joined

  • Last visited

Posts posted by RMcK


  1. Hello,

    I need to change the difference between the unit size and the rough opening size for some doors for some of our glazed sliders, so that the correct information will read out in the schedules for coordination with ordering.

    I don't seem to be able to find an option for this in the obj info. settings.

    Anyone know how to do this?

    It would also be great if anyone knows how to change the units in the rough opening column in the schedule to read out as inches for further ease of coordination.

     

    Thanks!


  2. I am trying to create a worksheet with multiple formulas in it. For this I need to be able to search different criteria in each column. The type is spaces. What is the order of the text I need to input into the cell to pick up with the criteria would do in a database row? I have looked through all of the following places and it is not very clear to a novice. 

    http://developer.vectorworks.net/index.php/VS:Function_Reference_Appendix#attrCrit

    http://developer.vectorworks.net/index.php/VS:Search_Criteria#Search_Criteria_Format

    http://app-help.vectorworks.net/2016/eng/VW2016_Guide/Worksheets/Worksheet_Functions.htm

     

    Thanks!


  3. On 6/22/2012 at 11:52 PM, Assembly said:

    I can easily create a Database row and get a list of all wall styles and the related area.

    Cell 1 '=WST' [sum]

    Cell 2 '=WALLAREA_NET'

    This is how easy it should be.

    To make it easy I should continue and

    Cell 3 =('__NNA_Wall_Style_Format'.'Cost Index Code')

    Cell 4 =A2*A3 and I will have an estimate of cost for all the walls.

    Now I try the same for slab. I can't see any way to emulate the same set up for slabs as I can for walls.

    There is no similar 'SlabArea'

    '=WST' does not have a corresponding '=SST'

    I am able to get a read out from this method for everything except the Cell 4 which would be the resulting cost estimate shows #value. Any ideas what I am doing wrong?


  4. On 6/23/2012 at 7:25 PM, Robert Anderson said:

    There is no "Slab Area", but there is "area()" which works with a slab object. Please review the worksheet in the very first 'quantify.VWX' document I posted above. (I fear we may be discussing in circles?)

    Is there any way you could direct me to this post?

     


  5. @tfloraditchthe only time annotation dimensioning does not work is if you are dimensioning a rotated viewport, for example where you have a difference in project north and true north. This is the only case where I have a class and design layer dedicated to dimensioning. I have tried eliminating this by splitting files where I need to show site plan (true north) sheets in a separate file to floor plans (project north), however I loose the automated elevation/section notations when doing this.


  6. Hello,

     

    I am developing worksheets to give me take-offs for my zoning and code area requirements for permits.

    I am currently doing this through assigned zones in space labels which seems to tie everything together well.

    However, it is taking a long time to change the settings, class settings, label setting to the space labels in each new project.

    Is there a way to change and save the default space label settings so that this is already done?

     

    Thanks,

    Rebecca

     


  7. @markddYes, this works to a certain extent.

    Thanks for the help.

     

    The slab object cannot be assigned a surface hatch from the attributes palette unless it is un-styled, which removed some of my control over this slab type in the whole project.

     

    Keeping the slab 'styled' for other take-offs, I can get the following: the best result showing hidden line for both foreground and background. Draw-backs of this are that symbols display their 3D look and not their 2D look, and we still don't get the top/Plan hatching in the walls. Currently resulting to using two viewports layered on top of one another to get the best of both worlds, although this work-around is very time consuming to both create and maintain/update.

     

    59bffec07e3c8_HIDDELNLINEFOREGROUNDDASHEDHIDDENLINEBACKGROUND.png.80259f68ca5c795c5fd89de0406c3a71.png59bffebfef233_HIDDENLINEBOTHFORANDBACKGROUND.png.d27c482ce5614f57c72f097b1b7ea993.png


  8. @TomKlaber The floor is a slab object. It does not show the surface hatch in Top Plan. Maybe I have my settings messed up? I would like it to be showing the surface hatch of the texture I have applied to the top component of the floor slab by class. Is there another way I should be doing this?


  9. Hello,

     

    I have a graphic representation problem.

    I would like to show the plan in TopPlan view in order to see the wall detail (default at wireframe) (image 1)

    However, I'd also like to show the hatch of the floor finish below. (image 2)

    Is there anyway to achieve this in a single viewport without layering by using the background/foreground options?

    So far I have not found an answer.

    Any ideas?

    59b6be83ae304_Back-WireframeFore-HiddenLine.png.0825fc5883c460675d8f549d19a86223.png

    59b6be829c8c6_Back-HiddenLineFore-HiddenLine.png.844c6545f3934b9347c7e5daaca6e718.png

    59b6be846ec5b_Back-HiddenLineFore-Wireframe.png.0814875d2e68a117bf1e9c57d2a213b3.png

     


  10. On 8/17/2017 at 10:00 AM, Jim Smith said:
    On 8/18/2017 at 0:48 PM, Jim Smith said:

    Well, for Grids our work-a-round is to have multiple viewport on details and scale them down then line them up with the grid line.

    @JimSmith Thats a good idea, we may try this. For grid bubbles we currently create a symbol of the grid setup and copy it into the annotation space on viewports of different scales


  11. 18 minutes ago, Jim Smith said:

    This happens with other items as well, Grid Bubbles come to top of mind. I think all of these tags should have the ability to be illustrated at a real world (i.e. print) size in either Point Size, or Height in Imperial or Metric

    @Jim Smith, Do you mean there is no way to do this? If so, what do you suggest is a good work around? Only put tags into annotation layer? or have multiple classes for tags of different sizes in the design layer? Thanks!

 

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