This can reproduced in any workspace in which I have tried, including the Bentley sample workspace. This report has been duplicated in SR Number: 7001047309
I cannot resist a bit of commentary: If you want adoption of these tools, you really need to quit breaking things which have been working for years.
On a less critical note: The effect of this bug renders drainage and sanitary workflows virtually useless in this release.
For anyone else facing the same dilemma as myself, the following is the only workaround I have found:
Not only does this workaround take 10 times as long, but I must move Civil Accudraw training effort tot he front of the line when I would prefer to save it as an advanced topic for some of our designers.
I totaly agree with you about the software that keep on breaking thing that were not broke before. About your post I just want to add that you can input precise data in the storm water properties.
You can only edit the elevation there if you first change the "set elevation to start" property to false. Otherwise, the conduit is locked to the invert of the node.
Regarding the change in behavior. The reason this property was ignored in previous versions is because of the following reasoning: In a pure hydraulic sense, it is a reasonable simplifying assumption to have these two properties set to true. By doing thus, the inlet pipe elevation would always be locked to the invert of the node, as is the outlet pipe. Thus there is zero elevation change across the structure itself. This simplifies edits to the network because you only need to edit the node invert elevation and you ignore the negligible effect on hydraulic calculations caused by not modeling the elevation drop across the floor of the structure.
However, now that the former StormCAD is now three dimensional, the change in elevation along the floor of the node, which still has a negligible effect on hydraulic calcs, is not negligible when considering the impacts on conflict detection. Thus, it was determined many years ago, that in a 3D context a better assumption was to 1) ignore the Set invert to start and stop properties 2) when creating the conduit use the invert of the node as a starting elevation but 3) conduit is immediately independently editable.
Now we find ourselves in a world where these properties are no longer ignored and the manipulators are broken and hundreds (maybe thousands?) of libraries have been created using the expected behavior of past versions. What can be done. It's really quite simple:
Robert Garrett Senior Consultant
www.envisioncad.com
The change in behavior was documented in the Release Notes. The placed conduit will have whatever settings the conduit prototype tells it to. If you want the “Set Invert to Start?” And “Set Invert to Stop?” properties set to false, then set them in the prototype.
Conduits that have already been placed won’t be affected, because the prototype is only read when a new element is placed. If someone has placed new conduits, and wants to bulk change the “Set Invert to Start?” And “Set Invert to Stop?” properties – then this only takes a moment in a conduit FlexTable, using Global Edit.
There are many enhancements coming up on 10.08.01
We continue to improve the product and always appreciate your feedback.
For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki