(Posted on behalf of Be Communities User)
GEOPAK Road V08.11.07.536
When display rules are added to the template, the superelevation does not work properly.
When creating a template that has display rules, verify that each component that will potentially display on/off has its own control line/point control defined for each superelevation "definition".
It appears there is another issue. Certain sections of this corridor with the same template and superelevation control are working just fine. What is the order of priority on a template? Do the point controls override the template constraints?
Hello EBauder,
Please see the link below for a blog that covers the order of process.
communities.bentley.com/.../roadway-designer-order-of-processing-template-points-components-rules-end-conditions.aspx
Our superelevation control is applied to the EOPs of our top layer of pavement. The lower layers of pavement are constrained with a slope equation equating to the slope of the top layer. So, these slopes are constrained back to the point controlled point and should be recalculated.
The doesn't seem to be with the specific template, any other ideas on things that could cause this behavior?
I'm a little confused by your description of the second layer. Are you just trying to get the second layer to have the same cross slope as the top layer? If so, please constrain the points to the top layer. (ex: your top layer consists of EOP_L, CL, EOP_R and your second layer consists of EOP_L2, CL2, EOP_R2. You should constrain your EOP_L2 to EOP_L with Horizontal/Vertical constraints. CL2 should be constrained to your CL with Horizontal/Vertical constraints, etc)
If this is not what you are looking for, would you mind sending your dataset to me for further troubleshooting?
Our problem has been resolved. After updating our templates with new display rules and synchronizing them in the template drops window, the "Enable Transition" option was automatically toggled on, which is what was causing problems with the superelevation. By simply disabling the transitions the issue was resolved.
Answer Verified By: Andrea Garecht