The International Simutrans Forum

Simutrans Extended => Simutrans-Extended bug reports => Simutrans-Extended development => Simutrans-Extended closed bug reports => Topic started by: Rollmaterial on January 21, 2017, 10:59:22 PM

Title: [devel-new-2] End of choose signs don't work
Post by: Rollmaterial on January 21, 2017, 10:59:22 PM
Choose signals seem to ignore end of choose signs at platforms.
Title: Re: [devel-new-2] End of choose signs don't work
Post by: Junna on January 22, 2017, 12:42:48 AM
I noticed this just now as well, and can confirm.
Title: Re: [devel-new-2] End of choose signs don't work
Post by: jamespetts on January 24, 2017, 12:46:36 AM
Can I clarify - when you write of end of choose signals at platforms, do you mean that end of choose signals that are actually placed on a platform tile are ignored, or that all end of choose signals are ignored?
Title: Re: [devel-new-2] End of choose signs don't work
Post by: Rollmaterial on January 24, 2017, 12:51:12 AM
As far as I have spotted, trains are routed to alternative platforms regardless of whether they are protected by an end of choose sign. As for the other features of the end of choose sign, I haven't spotted any suspicious behaviour.
Title: Re: [devel-new-2] End of choose signs don't work
Post by: Junna on January 24, 2017, 04:03:41 AM
As in, end of chose signals that stop trains that come and reverse from going to through platforms but still able to use the chose signal advance of it (which should not apply to through running ones). I didn't have mine on a platform tile but a junction tile ahead of one. Trains went and waited at the two through platforms which the waiting ones are not supposed to use.
Title: Re: [devel-new-2] End of choose signs don't work
Post by: jamespetts on February 18, 2017, 01:14:47 AM
I am currently reviewing old bug reports and I notice that this one appears to have no reported resolution. May I ask whether this can still be reproduced?
Title: Re: [devel-new-2] End of choose signs don't work
Post by: Rollmaterial on February 18, 2017, 07:27:34 PM
It seems fixed.