Tamsin Slatter

Edit > Paste in Place?

The Wall End Cap tool will do this for you. https://app-help.vectorworks.net/2023/eng/VW2023_Guide/Walls/Creating_wall_end_caps.htm?rhsearch=wall end cap&rhhlterm=wall walls end caps cap

Here it is: https://university.vectorworks.net/mod/overview/view.php?id=5243

In haste Michal, yes, look at Draped mode. With draped mode, you modify the site with grades or other modifiers to have the exact control you want. Then apply the hardscape to the surface and tell it to drape. It will also cut the site model if you wish for cut and fill calcs. Just finding you the webinar we did on this recently...

Hi Sarah I have just tested in 2022 and I am not able to recreate the problem. I created two files with identical georeferencing, and the same coordinates on the internal origin, my reference works correctly. I tried both a Design Layer Viewport (onto a Georeferenced design layer). And in another file, with layer import referencing. Ensure that the Internal Origin has the same coordinates in both files. This is critical. Then ensure that layers are georeferenced in both files.

The hardscape profile controls the surface of the hardscape so that it is not planar. You might use it to create a camber, or to slope towards drainage set within the surface of the hardscape.

Add a Grade Limit modifier around the area you want to grade. It's a mode of the Site Modifiers tool.

The Hardscape object already contains the information you need, which will save you so much time. Try Tools > Reports > Create Report, and then pick one of the example Hardscape worksheets. You'll see that it automatically pulls the information you need into the resulting worksheet. Vectorworks University has some great workflow tutorials to help you get the best out of Landmark. This hardscape-specific course would be a great place to start: https://university.vectorworks.net/mod/scorm/view.php?id=2938

OK Linsey - can you confirm your computer specs? And then I really think a chat with tech support will be the best thing. (Looking forward to seeing you at the end of September 😊 🎵)

The orange is the usual selection highlighting you get when you select an object - that's why I think it's very, very zoomed in from the image you've posted. Have you measured something on the site to make sure it has come in the size you are expecting? Probably best to send in to tech support if you can't resolve it.

Hi Linsey Looking at the image, it looks like you've imported a DWG. My guess would be that you've used the wrong unit of measure on import (say, millimetres instead of metres) which has made the objects 1000x smaller than they really should be. So, that's the orange bounding box around things, but you are zoomed in very, very close. Perhaps try the import again in a fresh file, and choose metres on the import dialog, and see if that solves it. Then metres in the DWG will be converted to metres in Vectorworks. I think they've been converted to millimetres...

@David SLooking forward to seeing what Grainne does with this one.

Try this course in the University: https://university.vectorworks.net/mod/overview/view.php?id=2490 Start 7 mins in - if you are storing on the cloud it doesn't matter which option you choose as it will use internet protocol, not AFB or SMB. If you are storing on a server instead, we strongly recommend all SMB. Also, when sharing with Dropbox, share only the FOLDER in which the project file resides. So, set up the folder, share it, create the project file somewhere else, and MOVE it into the shared folder. Otherwise, you will get sync errors.

The issue is resolved in SP2.1.

Just to confirm. Vectorworks has no plans to "abandon" the FileMaker database. The long term issue with the FileMaker solution is that FileMaker is a third party product, and FileMaker no longer support the application specific licence that is bundled with Vectorworks. It continues to work, which is why it is still available for you to use. However, at some point, it may stop working, and our engineers will have no control over this as it's not our software. At the Design Summit, I suggested that customers familiarise themselves with the Plant Catalogs which provide an interim solution that IS within our control. Ultimately, our goal is also to provide links to external databases through the web and not rely on anything proprietory.

Our industry expert @Katarina Ollikainenand I had a meeting with the engineers yesterday and discussed the way forward with this. We expect a resolution in the early part of the new year. In the meantime, if you would like to send me a file which contains ALL the plants you want updated, via a PM, and tell me which parameters you want updated, we can get this done for you. For example, I know you want the tags all set to By Style and None. I can also set the Height and Spread to By Style as a workaround to the issue. There is a script, but it is not something that can be run on a public release of our software.

I completely agree - Data Tags are the way to go.

If you put your drawing label or Scale Bar within the Viewport annotation space, it should correctly scale to the scale of the viewport.

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.

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.

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.

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

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

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.

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.