[Csantucci]

In the past I tried solving the problem of station stops messed up in loop paths, but I gave up.

[jdgremsjr]

Csantucci, on 02 December 2017 - 12:56 AM, said:

In the past I tried solving the problem of station stops messed up in loop paths, but I gave up.

So Should I change the final stop to Burkes #1 and then end the activity by parking in the Diesel Facilities? That way there are no station stops in the loop? Will that fix the problem? Or because it is still a loop the problem will persist?

[Csantucci]

I don't remember exactly the behaviour. You should try :)

[James Ross]

jdgremsjr, on 01 December 2017 - 02:20 PM, said:

Sorry, I attached the photo rather than the actual activity. Activity here.

Thanks, but I am having trouble extracting the APK; tsunpack says "Expected more files, package damaged!" and APKExtractor3 says "UNABLE TO PROCESS apk FILE DUE TO INCOMPLETE or CORRUPTED DATA.". I've tried downloading it again, in case it got corrupted, but it still won't work.

[jdgremsjr]

James Ross, on 02 December 2017 - 02:16 PM, said:

Thanks, but I am having trouble extracting the APK; tsunpack says "Expected more files, package damaged!" and APKExtractor3 says "UNABLE TO PROCESS apk FILE DUE TO INCOMPLETE or CORRUPTED DATA.". I've tried downloading it again, in case it got corrupted, but it still won't work.

Yeah me too, will zip it, the old fashion way and repost.

[jdgremsjr]

Download Activity (zip file)

[James Ross]

jdgremsjr, on 02 December 2017 - 04:13 PM, said:

Download Activity (zip file)

Thanks, I've reproduced the problem and it seems to me that there are definitely issues with the loop handling in OR. It's been a struggle to decode the arcane code involved but I now understand what it is doing and why it doesn't work: roughly speaking, when you depart the first station inside the loop (Nuggett) OR thinks it has completed the loop and discards everything else inside the loop (all the remaining station stops except the final one).

I'm still trying to figure out what the intention of the code is (which is much harder to figure out than the function without good comments), before I can try out any fixes.

[jdgremsjr]

James Ross, on 03 December 2017 - 02:34 PM, said:

Thanks, I've reproduced the problem and it seems to me that there are definitely issues with the loop handling in OR. It's been a struggle to decode the arcane code involved but I now understand what it is doing and why it doesn't work: roughly speaking, when you depart the first station inside the loop (Nuggett) OR thinks it has completed the loop and discards everything else inside the loop (all the remaining station stops except the final one).

I'm still trying to figure out what the intention of the code is (which is much harder to figure out than the function without good comments), before I can try out any fixes.

I code in Javascript, jQuery, PHP, and Python. I understand trying to figure out code that isn't commented, I sometime can't even figure old code I did, because I was too lazy to comment it.

So, I have the same question as before, should I change the final stop to Burkes #1 and then end the activity by parking in the Diesel Facilities? That way there are no station stops in the loop? Will that fix the problem? Or because it is still a loop the problem will persist?

[mbm_OR]

Hi James,
Checking this new functionality, I have noticed that, once "Automatic platform and siding visible" state, it's enabled, if there is a label visible at activity start, this label disappears when the train starts departure, without label intensity effect.

Attached a patch to solve it.

 OSDLocations.cs.patch.txt (2.74K)
Number of downloads: 244

[James Ross]

jdgremsjr, on 03 December 2017 - 07:03 PM, said:

So, I have the same question as before, should I change the final stop to Burkes #1 and then end the activity by parking in the Diesel Facilities? That way there are no station stops in the loop? Will that fix the problem? Or because it is still a loop the problem will persist?

Please don't change the activity, I am fixing the bug in Open Rails. :)