Page 1 of 1
[0.12.32] Updating game causes signal state mistakes
Posted: Tue May 03, 2016 12:02 pm
by DutchJer
i found some broken signalling in my map. i just updated from 12.31 to 12.32 and then they were broken, thus getting a deadlock.
ill just take the signals out and put them back, but i dont know why this happend.
the save can be found here:
https://www.dropbox.com/s/g0368z8pqb5hp ... y.zip?dl=0
Re: [0.12.32]
Posted: Tue May 03, 2016 12:29 pm
by Klonan
Thanks for the report,
Could you provide some steps to reproduce?
The savegame from before you updated would be really useful
Re: [0.12.32][Pending] Train signals deadlock
Posted: Tue May 03, 2016 3:06 pm
by DutchJer
save coming up, uploading 200MB to dropbox might take some time
Re: [0.12.32][Pending] Train signals deadlock
Posted: Tue May 03, 2016 8:38 pm
by DutchJer
savegame added to the original post. this junction is the junction to oil 2. south of the main base.
Re: [0.12.32][Pending] Train signals deadlock
Posted: Thu May 05, 2016 9:39 am
by bobingabout
That does look like a bit of an elaborate junction.
Re: [0.12.32][Pending] Train signals deadlock
Posted: Wed May 11, 2016 3:05 pm
by d4rkpl4y3r
I too, ran into that problem when updating from 0.12.29 to 0.12.33. But in my case it doesn't include chain siganls.
In the save file, the coal train stops after a couple of seconds at the yellow signal.
https://dl.dropboxusercontent.com/u/104 ... 12_154.zip
Re: [0.12.32][Pending] Train signals deadlock
Posted: Wed May 18, 2016 5:55 pm
by youdoomt
d4rkpl4y3r wrote:
I have seen this problem too. it seems to be a "ghost" train the the block eg. the block after the signal is saying that it contains 1 train but there is none, updating the block by placing and removing a signal in the middle of it seems to fix it.
Re: [0.12.32][Pending] Train signals deadlock
Posted: Mon May 23, 2016 11:08 am
by Klonan
Has anybody come up with steps to reproduce the problem?
Re: [0.12.32][Pending] Train signals deadlock
Posted: Mon May 23, 2016 1:59 pm
by youdoomt
Klonan wrote:Has anybody come up with steps to reproduce the problem?
As I understand it seems to be a problem happening when updating the game to a new version, so we don't really have the tools try that out, as we can't revert to earlier versions on steam.