ericjhberg

Thanks @Tom W.. I saw this in the post, but can't figure out how to get to this dialog box

As I posted before in the forum, the fence tool is a great improvement. Now it is time to take it further. The gates are clunky. I've posted about the need to be able to control gate data different from the fence, but we also need their insertion and editing to act more like doors in walls. This is particularly true when trying to control the direction of a gate opening. For a single-swing gate, there are four potential opening configuraitons (in-right, in-left, out-right, out-left). Currently, to my understanding, you have to create four different gate symbols for each cymboonfiguration. That is clunky for essentially the same gate. Make insertion like doors where you can control the configuration upon insertion, using just one symbol.

We need a tool that can quickly analyze a site model to determine the watershed associated with a given point/stake/elevation. This is important for calculating drainage areas and performing basic stormwater calculations. It would be even better if the resulting watershed could be categorized into different cover types (pervious, impervious) with different runoff coefficients. Essentially and intersection of the various hardscapes/landscape areas within the watershed. These would then need to be able to be reported on for stormwater calculations.

This has been a long time observation and wish to improve, I've just never taken the time to post it here... Please surface the Smooth Corners and Close Open Curves toggle options, located within the Offset Tool Preferences, to the Tool Bar. This would eliminate so many clicks and seems like it would be relatively easy to implement.

This has been my #1 wishlist item for almost 10 years now...primarily because it should be simple...right?

This 100% looks like the site model isn't understanding your Grade Limits. Three basic troubleshooting questions... Do you have grade limits? If so, are they in a layer that the site model is reading (Site Model Settings)? If so, do your modifiers cross your grade limits?

Thank you. I feel like it has worked as desired in some versions and breaks down in others. No matter what, it never works in the version I am using when submitting plans...

I feel like this functionality has flip-flopped over the course of Vectorworks site modeling, but we need resolution in the current v2025 and what we're seeing for the Site Model Existing + Proposed 2D visibility. What is currently happening is that the PROPOSED contours extend beyond the Grade Limits...overlapping with the existing contours. What SHOULD happen is that the PROPOSED contours should be limited to within Grade Limits, and ONLY the existing contours should be visible outside the Grade Limits. @Eric Gilbey, PLA @Tony Kostreski @Vlado @Katarina Ollikainen

@Shortnort...I'm curious how you achieved your desired result given the tool's limitations. Do you mind sharing?

I believe this issue is with worksheets between Mac and Windows. We have noticed worksheets will end up smaller when updated on Macs than when updated on Windows. I thought it was a specific font issue (we use Century Gothic) between the two systems, but it might be universal.

Totally agree with this request. In fact, I think all of the "modifiers" whether they are actual Site Modifer objects, Grade object working as site modifiers, Stakes set as site modifers, etc. should all work together in a much more harmonious way. Linking them is an obvious first step, but another is the ability to "lock" particular grade constraints (i.e. 2% max slope, 8.33% max slope, etc) and have the network respond accordingly.

Actually, the "Curb" you think you seeing in this 2D version of the curb profile isn't actually the curb. It is the part of the base that is protruding past the horizontal back of curb fact. As I have been playing with curbs, there is NO WAY to represent a traditional curb and gutter in 2D using a single profile. Instead you have to create separate Components in the style to show the curb line separate from the gutter line. IMO this tool is really cool, but has some glaring functionality misses and this is one of them. NO ONE draws a curb and gutter the way it is represented on the left and it is really difficult to get it to draw it traditionally without some extreme workarounds.

Data visualization should be able to support calculations between parameters/inputs. This capability is possible when defining Tag Fields in Data Tags, and we're currently using it to calculate and annotate cost per unit (i.e. price per area x area = total cost). It would also would open up the opportunity to visualize density (population / area = population density). If this was a possibility within data visualization, many possibilities to help visualize design decisions would be possible.

Make that 7+ years?

First of all, let me say that the new 2024 Fence tool is such an improvement over the former functionality that I don't want to sound ungrateful when I suggest that it still needs some edits. I think the gate functionality is still a little clunky, but seemed to be workable until I realized that there is no easy way to quantify or add data to gates independently from the fence run they exist within. You should be able to select gates in a similar way to doors work within walls and you should be able to control their data independently from the fence line they exist within. This is extremely important when adding data tags, quantifying gates, and or reporting gate specific information.