Jump to content

Tamsin Slatter

Vectorworks, Inc Employee
  • Posts

    1,888
  • Joined

  • Last visited

Everything posted by Tamsin Slatter

  1. If you put your drawing label or Scale Bar within the Viewport annotation space, it should correctly scale to the scale of the viewport.
  2. Firstly, the changes to the Plant to move to a true Object Style was requested by many customers, because it enables the rapid change of multiple plants on the drawing, by simply editing the style. However, it does mean that the tag information is also now tied into the Plant Style, and is no longer set as a tool preference. (The dialogue box is no longer called Tool Preferences, because all the options are now controlled by style). (Yes, Data Tags are the way forward). So, in SP1.1 the properties of the Plant Style were populating the Plant Tool based on the style settings, regardless of whether the property was By Instance or By Style. However, as the Tag properties had also become part of the Style definition, this was causing problems, as the styles you all have in your libraries may not have been set up in a consistent way. Our engineers fixed this in SP2. However, the fix also introduced the issue you were then seeing with the Height and Spread, in that it was using whatever was last used in the tool as the height and spread. So, reverting to SP1.1 will solve the height and spread, but not solve the tag issue. Our engineers are thinking this through very carefully, as we need to ensure that any change will make as many people happy as possible. Meanwhile, we recommend that any libraries you create should start life with ALL properties set to By Style. If you wish to override anything, you can do this by duplicating the Plant and changing the properties in the duplicate. (This will also ensure you don't have issues with multiple instances of Plants with differing properties that do not report correctly on the schedule). BUT, we are aware you have existing libraries where the properties may not be By Style. Our engineering team are working on a script which can be used to convert the styles properties to either By Instance or By Style, but I'm afraid this is not available yet.
  3. Hi all We are aware of this issue. It is actually only a problem in SP2 and has been caused by another change. Our engineers are working on a fix (internal ref VB-184074). But, you can revert to 2022 SP1.1 and you will find that the plants will pick up height and spread from the style again, even if those properties are set to By Instance in your object style definition. To revert to SP1.1, you can use the Vectorworks 2022 Updater application, which you'll find in the same folder as the Vectorworks application. Click on Advanced Options to display the menu. Click and hold either the Alt or Option key, and the option to change version will be displayed. If you revert to SP1.1, I believe you will find the Plant tool works as expected.
  4. The units issue remains. However, the colours do get reported in the worksheet in 2022. I have updated the bug report. Internal ref number VB-184033.
  5. I recommend you look at using the Data Tag tool instead of the built in tag if you want to customise layouts. It's such a powerful tool and can be used to tag anything that has data. And you have full control over the layout. Here's a course in Vectorworks University to introduce you to this powerful tool: https://university.vectorworks.net/course/view.php?id=98
  6. It creates a bounding box on the extremities of the data, just like a polygon does. It has no way of knowing which points are the edge, so looks at the extremes of data to ensure nothing is missed. You than edit as you wish. Hmm, I also can't see the data. Here's the solution: Choose Recreate from Source Data. Trace around your data to create the crop you want, cut it, and then paste it into the crop edit (deleting the original crop).
  7. I would recommend that you do this in a worksheet - report on the cut and fill, and then use a formula to increase the bulking ratio as appropriate to the site.
  8. Which version of Vectorworks are you using? I reported this as a bug some time ago, and it was resolved in 2021 Service Pack 2.
  9. @Peter Neufeld.Nice - yet another great solution!
  10. You can add Tags at any time, by either: Selecting the plants and choosing the desired tag options on the Object Info palette OR Using the Data Tag tool to apply tags to the Plants (this is my preferred suggestion. If you get into Data Tags, you can tag ANYTHING that has data attached to it.)
  11. Draw the curve using the polyline tool. In the Plant tool, choose your plant and the poly edged space mode, then choose the Fill Bucket mode (I can't remember exactly what it's called, but choose it instead of Insertion mode. Then click on the Polyline. It will convert it to a Plant object and the plants will be perfectly aligned along the path.
  12. The other thing you might want to consider is unchecking the Show in 3D checkbox. That is what's giving you white outline.
  13. You're very welcome. Warning - Data Tags are addictive... they are SOOO useful!
  14. Existing Tree Data Tag Example.vwx In this example, there are two trees, which are autonumbered. The tag is in a class which is invisible. I have then created a Data Tag which looks at the Existing Tree parameters, and displays the tree number with the Botanical Name field. WIthin its style, I have defined that it will always be centred on the Existing Tree.
  15. No, I don't believe so, but for all tagging, I would recommend you look at the Data Tag tool instead of looking at the tagging options within the individual tools. With Data Tags, you can include whatever information you want, control the layout yourself and tag multiple objects in one click. Here's a course in the University that will teach you about Data Tags. Don't be put off by the title - Data Tags are not just for hardscapes. They are for anything that has data attached: https://university.vectorworks.net/mod/scorm/player.php?a=85&currentorg=articulate_rise&scoid=170 I will also make a small example file and attach it here.
  16. The Get Plant Data button is in the Plant Tool, not the Existing Tree tool. The Existing Tree tool has a Get Species Data button on the Object Info palette. You'll find the place to set the class and tag options under Tag and Number Options.
  17. Agreed with @Nina Ivanova The author of the DWG should be able to tell you the unit of measure that they used when drawing the AutoCAD file. That is the unit you need to specify on import.
  18. I suspect that this is down to the use of "global" line thickness in AutoCAD. This is a setting where the thickness of the line varies proportionally with the extents of the drawing, instead of being a specific thickness. Vectorworks does not have an equivalent, so if the drawing is imported at a different scale, then the lines can become very thick. The solution is to allow the drawing to be imported using the suggested Fit to Page scale on the import dialog, instead of at 1:1. Then, the line thicknesses will be in proportion with the rest of drawing. The .ctb file is used in older AutoCAD files as a colour table. They use colour instead of line weight, and then the colour table translates this to line weights at plot/print time. The Map Colours to Line Weights option on the import dialog will list the colours found in the ctb file, and allows the Vectorworks user to assign different line weights to each colour on import. However, as the Vectorworks user hasn't yet seen the file, this is difficult to do. So, I usually encourage people to just edit the resulting classes once the drawing has been imported to set the desired colours and line weights. In the case of this file, use the Select Similar tool (setting the preferences to Class), and select one of the objects with the thick lines. On the Object Info palette, notice which class they belong to. Edit this class and set the desired line weight (remove the fill at the same time, unless you specifically want a fill colour). Then check the Use at Creation box to ensure any future geometry in this class adopts these properties. ALso, on the Attributes palette, click the arrow at the bottom and choose Make All Attributes by Class. This will force the objects to pick up the class settings. Repeat this process for objects in other classes.
  19. Hi @LisaLeaves I'm still around, but now work for Vectorworks' UK office. We do have a training team and are able to offer training on site modelling. I can't guarantee that I will be delivering the training, but all members of our team know their stuff! We'll get in touch.
  20. Beautiful work Kevin. Thanks for sharing the file.
  21. Do you also need a 3D Locus which determines the rotation point for the pan and tilt?
  22. The Cut and Fill display is a flat plan of where to cut and where to fill. Instead, there is a button to Update Cut and Fill Calculations. The Site Model Section command creates a 2D annotation, which you can include in a viewport. The single site model is a far more efficient way to work, but as I said in my post above, there is a learning curve. This course will help you: https://university.vectorworks.net/mod/scorm/player.php?a=1&currentorg=articulate_rise&scoid=2
  23. Hi No, the Slab modifier that is part of a hardscape is a planar object, so, it will flatten the site to match the hardscape, but it will not excavate from the site. It's good for visuals, but for calculation. I would recommend that you don't use the site modifier that's built in to the Hardscape tool. Instead, create the site modifiers separately. Your options are: Use the Pad with Retaining Edge option within the Site Modifiers tool. This creates an edge that can fit to the top surface of the hardscape, and a pad which can be adjusted to fit the base of the hardscape. The top and bottom elements of this modifier will be automatically offset by a small amount, so that they don't conflict. Find out more here: https://university.vectorworks.net/mod/scorm/player.php?a=1&currentorg=articulate_rise&scoid=2 Create your own site modifier - use 3D polygons to create what you need, and put them in the class Site-DTM-Modifier. But remember that the upper modifier must be slightly offset from the base modifier (in Top/Plan view) otherwise they will touching or overlapping and one set will be ignored.
  24. I'm a little puzzled why you have existing and proposed terrain on separate layers. A single site model can display existing and proposed. You apply site modifiers to the existing site, to create the proposed site. But Vectorworks keeps track of both, so you can calculate cut and fill. The Site Model Section command can then be used to create an annotation of the surface of both sites, together, with levels annotated if you wish. There's a learning curve, but plenty of information to help in Vectorworks University: https://university.vectorworks.net/course/index.php?mycourses=0&search=Vectorworks-Landmark&tagfilter[category]=0&tagfilter[type]=0&tagfilter[difficulty]=0&categorysort=default&mycourses=0&search=terrain And here's an overview of the process: https://app-help.vectorworks.net/2021/eng/index.htm#t=VW2021_Guide%2FSiteModel1%2FDesigning_landscapes.htm%23TOC_Concept_Sitework_overviewbc-2&rhsearch=terrain&rhsyns= &rhtocid=_9_0_0
×
×
  • Create New...