I am trying to apply an end condition exception to a template that has a right outside edge of pavement that is controlled by a horizontal feature constraint so the outside edge of pavement is able to vary (for example, at a turn lane taper transition). Because of this horizontal feature constraint, my model has an edge of pavement that is further to the right than its original location in the template. When I try to apply an end condition exception, the template editor that opens up does not recognize that my edge of pavement is not at its original location, so the new end condition is placed at its original location in the template and not at its actual location in the model, which is, again, further to the right because of the horizontal feature constraint. Has anyone encountered a similar issue, and is there a solution that involves still being able to use an end condition exception rather than modifying the template itself? Thank you.
Joe Moslemian said:is there a solution that involves still being able to use an end condition exception rather than modifying the template itself?
Long story short, Not really. (example posts/answers below)
Traditionally, I've steered away from EC Exceptions... they always seemed buggy and many times moved on quickly. Not saying there isn't a better way to harness them, but typically find other ways of entering unique "exceptions" with common design controls (display rules, triggers/switches).
End COndition Exception Parent Component Relationship
End Condition Exceptions Not Working
Bentley Accredited Road Designer | Bentley Accredited Road Modeler
colliersengineering.com