Flat ITL

Question

Hello, 
 I'm using PowerRail Track SS4 and it seems that my ITL file has been corrupted and, somehow, all the templates of the ITL has their constrains with value 0.

Do anyone knows what is reason of this? 
 Thank you in advance, 
 Carlos Molina 
 
 The ITL was completely ok the last time I opened it and I don't know what happened. See the file attached. I also attach the file propperly working before the lastest changes. Without bug.itl 
 Bug.itl 
 I

jpln · Answer

We know the issue and I am also experiencing this issue. Unfortunately I have been unable to understand how I get there. I would say that it is when editing template drop but really not sure and it does not occur all the time. 
 It is definitively an issue with decimal separator. My windows setting is . as decimal separator and , as list delimiter. This setting doesn't change. 
 To fix the issue with the ITL, close Rail Track/Openroads/Openrail and go to windows setting to change . to , (or probably the reverse if your default setting is , as decimal separator). Launch the software and open the ITL. It should be ok. Save. Close and go back to your normal setting.

jpln · Answer

This issue should be fixed with 2019-R3 (10.08.xx.xx). 
 When it does occur I found that you could recover doing this: 
 
 close Openrail 
 change windows setting from . to , 
 open Openrail 
 check the itl is good 
 close Openrail 
 change windows setting back to usual, so , to . 
 Open Openrail 
 
 Painful if you have the issue many times per hour but at least you don't lose anything. This recovering workflow worked each time until now. Hope it will be the same for you. 
 And hopefully we won't have this occurring anymore with 2019-R3. I haven't use it enough to say yes.

vincent · Answer

I can confirm this workflow (changing to comma then back) works, the ITL has to be the default one CIVL_ROADWAY_TEMPLATE_LIBRARY 
 UPDATE : 
 I'd like to share another parameter that seems to mess things up: I had changed my windows language preferences to French, and had got since a lot of flat ITL issues. To check, I copied the flat ITL to a Virtual machine in US language, but France as Region, comma as decimal separator. 
 The ITL loaded FLAT. 
 I changed the region setting to "United States", and ITL loaded intact. I had changed nothing else, no change in decimal separator, ... So from this experience, if flat ITL syndrom happens, then check you region settings: 
 
 If your region setting is set to your local area, set it back to United States and check the ITL loading is ok. If not then apply Jean-Pierre's procedure. 
 As stated "Windows and Apps might use your country or region to give you local content". So my guess is something in Wondows or ORD takes into account this setting rather than the effective one you had set in your prefs as decimal separator. So ORD expects default setting for locale that is in my case a comma for French. Since I changed "Crountry or Region" to "United States", not flat ITL.