sticking with imported cant when changing things

Question

Hello 
 We got the following situation: 
 we get track geometry including cant via an xtr 
 the cant defined in there assumes a rotation about center, 
 But, after importing the xtr to ORLD the program assumes a rotation about the inside rail. 
 So then, when i then change the rotate about option, all the values for applied cant change. 
 To avoid the values for applied cant changing (they are defined by the customer and binding!), i disable the rules in the cant editor. 
 But when i do that, and then change the rotation to "about center", the cant is always applied to the same rail. (i.e. the right one) 
 when i don't freeze the rules, the values change. 
 how do i get to the point where i can stick with the imported values but set the rotation to about center? 
 also as a side note we need to stick to the imported values anway, as they are not always following or corresponding to what would be calculated. for example the values are drastically reduced inside a station.

jpln · Answer

I did a quick test, and in 2021 R2 (10.10.21.04) changing the rotation point with rule deactivated just change the elevation of rails not the cant. And elevated rail looks good wheter I am using inside rail or center. 
 But if rule is activated, then when changing the rotation point, it recalculates all from the rule even value that have been forced. Maybe not something we always want to happen. When changing rotation point, cant is ruled back to the speed table even if you forced some value. Nothing changes if rule is deactivated and reactivated but next edit of the speed table with rule on will update all the cant value. 
 Anyway, I filled an enhancement to get an indicator on each line in the cant editor to show if rule is activated or deactivated and to be able to change on each line (or by selection set). The aim is to have a clear understanding of what is happening with the value. The indicator should be set by default to deactivated when importing geometry. 
 Could you share the XTR so that I can do some testing? If the rotation point is defined in the XTR it should be used as such to create the cant in OpenRail.