Inroads V8i SS2 end condition exception with superelevation doesn't work

The origin of your end condition must be constrained to the end of your backbone.  With no constraints on the end condition it will maintain its position relative to the template origin, regardless of superelevation or other controls on the backbone.

Hi Ray, I tried that too earlier and got same results. I am re doing it just to show you the screen shot with constraints.

It's a little difficult to tell, but is your end condition actually attached to your backbone?  I believe that the origin of the end condition must be attached to a point on the backbone.  It looks to me like the start of your end condition should be Lt_Road_Elane.  You may want to uncheck the box for "Check for Interception"; otherwise it may catch between the Lt_Road_Elane and Lt_Road_Verge1 points.

By the way, I've never had any luck moving an end condition from one backbone point to another and getting it all to work the way I want it.  I usually end up attaching a new end condition to the appropriate point.

Thanks for the reply. It is connected to the backbone. My Lt_Road_Elane is end of pavement and then I have a shoulder protection area (Verge, which follows the same slope as road pavement) and then end condition. The end condition is connected to the verge component. I double checked and actually re did this thing with whole new data set. It just don't work.

Are superelevation flags set at centreline and EOP? Have you considered 'vector-offset' instead of 'slope' to these two points?

This is SS2 so there are no superelevation flags.  Changing the constraint type is definitely worth a try.  You might also try controlling Lt_Road_Verge1 with a superelevation point control rather than some sort of slope constraint.  I have to admit, I'm running out of ideas.

Hi Ray, thanks for the idea. I have to admit too I don't know what else can be done. FYI guys, the superelevation by itself is working it's just the connection between backbone to the end condition. It feels like the connection between the end condition and backbone is gone. It doesn't change with horizontal curve and super rotation. Means it stays at the first location where I put it at the begining chainage. No shift between horizontally and vertically to follow the corridor. I might try applying the superelevation point control on Lt_Road_Verge1 point too. Will let you know soon. thanks. 

Gary Thanks for the idea of Vector-offset. Will try soon and update.

Hi Ray, thanks for the idea. I have to admit too I don't know what else can be done. FYI guys, the superelevation by itself is working it's just the connection between backbone to the end condition. It feels like the connection between the end condition and backbone is gone. It doesn't change with horizontal curve and super rotation. Means it stays at the first location where I put it at the begining chainage. No shift between horizontally and vertically to follow the corridor. I might try applying the superelevation point control on Lt_Road_Verge1 point too. Will let you know soon. thanks. 

Gary Thanks for the idea of Vector-offset. Will try soon and update.

The other type of constraints also results the same thing. Also noticed another thing now when I try go change the constraints, the constraints get removed once I get out of the template modification and run the model. Next time I go in to edit the end condition exception template the past constraints from Lt_Road_Verge1 get removed. It doesn't stay. 

Since it's in the backbone, I don't think you can control the location of Lt_Road_Verge1 with an end condition exception.  I think you will need to change the constraints on that point in the template.

another thing I would like to inform, I have display rules for the backbone component. This rule switches off kerb and turn on verge at the end of road lane. This switching is controlled with parametric constraints to trigger at particular chainage. 

I haven't used display rules very often.  But since the break is between the verge and the end condition I wouldn't think that would be the issue.

One option is to use the corridor as is, with the end condition exception but without override and add the alternate grading as a secondary corridor or linear template along the last feature.