nahekul

Here are the issues I found. I've attached the 2025 Vectorworks files. This works in previous versions but not in 2025. 1. Drainage slopes show when it is a fixed-thickness slab. 2. Drainage slopes show when the tapered component is the bottom layer 3. Drainage slopes don't show when the tapered component is the top layer 4. Drainage slopes don't show when the tapered component is the middle layer (When a new insulation layer is added below the concrete layer in #2) 5. Drainage slopes show when the slab fill is removed. 6. Drainage slopes show when the tapered component is the bottom layer. (When the taper is moved from the concrete middle layer to the insulation bottom layer) Slab Drainage Tool.vwx

Thanks, this will probably be what we have to do. Ungrouping the PDF lost a lot of the line work for some reason.

Just trying to get a consolidated line file for the consultant team to work off of as a basic background. We have a master site plan file with 5-6 apartments and multiple townhouses all on their own separate vectorworks files, as well as civil and landscape drawings. A lot of the viewports show a much bigger area than we want to export (city scale in the case of civil). So if there is a way to export just the crop of the sheet layer viewport as 2D lines, then it would be easy for other consultants to use it as their background. (They also don't want to use PDF as their background either since the PDF includes extra information they don't need). I've tried converting the PDF to DWG in Illustrator as well but the PDF has too much information (over 15000 objects), it would just crash.

Is there a way to convert multiple (more than 10) viewports that is referenced either from different files and from the same file but different scales into one 2d line drawing? I've tried converting this to PDF and then importing it back into Vectorworks with "snap to geometry". But ungrouping it just turns it into a white rectangle.

In Vectorworks 2024, when the slab gets more complicated than a rectangle, some slope arrows do not have the handles to move them. Some arrows are in locations that are not very graphically clear, so being unable to move them to a better location is a problem.

Here's a clean file which still shows the issue. As you can see, every newly added vertex shifts the existing value counterclockwise by 1 node. (And it doesn't matter where I add the vertex). Site modifier test VWX2024.vwx

Hi Pat, Yes, that sounds about right. The only thing is that some of the polygons might not always be on top of the space object. (ie. Balconies would be outside) 1. If that is the case, then I wouldn't need to assign a record. (Previously, the record allows copy/pasting to the space easier) The record also allows me to enter the unit number to tie it to the space object, if that helps. 2. Sometimes yes. (ie. 2 balcony polygons that are not connected could be tied to 1 space object. In that case, the areas would be summed) However, if that's too complicated, the balconies can be entered manually as before and the rest of the polygons can still use the script as described.

When using the site modifier retaining edge, adding a new vertex will shift all the previously entered Z-values on the existing vertexes. This is a problem on large complex sites with multiple vertexes. At the start of the project, we usually don't know where all the vertex locations are, and as the project progresses, we'll need to add new vertex for key locations (ie. stairs, entry, etc...). However, we don't want to re-edit all the previously entered Z-values every time we add new vertexes. Also, there needs to be a better way to edit the vertexes. Currently, every time you click on the site modifier object, it defaults to "entire object". To edit the vertex, you'll need to go through a drop-down menu to access the "retaining modifier vertex" mode to even see the Z-values. Then you'll need to cycle through all the vertex one by one to get to the one you want to edit.

I could create a class for each type of polygon. (ie. storage exclusion, leasable area, etc...) Then each polygon will have a record format that can display the suite it relates to and the areas. (ie. 101, 102, etc...)

This will be used to list the floor area of suites and the other associated data of that specific suite. For example: Suite 101 will have: suite number = 101 gross area = 500 sqft leaseable area = 450 sqft storage exclusion = 50 sqft balcony exclusion = 20 sqft wall exclusion = 10 sqft The suite number and gross area can be transferred to the worksheet database using the standard formulas. The other areas have to be drawn as separate polygons and the areas have to be typed in manually into the record format of the main space object of suite 101 (for it to be displayed on the worksheet). A smart tag can be used to transfer the required data from the OIP into the record format for each of the area polygon. The key is to transfer those data from each polygon into their respective data fields of the main space object. It would be possible to add a suite number to those polygon record format so there's a link between the main space object and the area polygons. Eg. All polygons with record format space name [101] will transfer their data to the record format of the Space object with Space name 101

Is there a way to transfer record data from multiple objects to the record format on 1 main object? For example: Object 1 has data 1 Object 2 has data 2 Object 3 has data 3 These 3 records need to be transferred to Object 4 which has the records from the 3 objects: Object 4 has data 1, data 2, and data 3.

I'm having trouble creating a sloped slab that is angled as shown. When creating a standard sloped slab, I use the drain tool to place 2 drains at the edge of the slab and use the connect drain mode to join the 2 drains. Then the slope is created by editing the valley to the elevation needed. However, if the slab has an angle of more than 160 degrees and I try to join the drains, I get this error message: "Adjacent valleys of a drain must be less than 160 degrees apart". Is there a way to create a sloped slab that is this shape?

The T lock doesn't work if another object is on the same axis as the mouse pointer when hitting "T". (This shows as a light red dash line) It only works when the mouse moves off of the object before hitting "T". (This shows as a solid red dash line) Can this be fixed so it always locks the axis regardless if there is an object along the mouse pointer or not? Currently, it's very cumbersome to keep moving the mouse out of the object's range to engage the "T" lock.

If you clear the content of those new database header rows, and now try to copy the first row into those empty database header rows, it will start offsetting.

It works correctly if you copy it to a new empty cell. It doesn't work if you copy it to an existing database header cell.