The International Simutrans Forum

Simutrans Extended => Simutrans-Extended development => Topic started by: Junna on October 16, 2015, 10:35:21 PM

Title: Signals and boxes don't seem to connect at all
Post by: Junna on October 16, 2015, 10:35:21 PM
Build from yesterday. Doesn't seem that any signals and boxes are connected any longer as they used to.
Title: Re: Signals and boxes don't seem to connect at all
Post by: jamespetts on October 16, 2015, 11:37:59 PM
I can't reproduce this, I am afraid. Can you give more details? Please note that narrow gauge signals in Pak128.Britain-Ex have not been updated to work with signalboxes yet, so if you are using narrow gauge signals, this might be the issue.
Title: Re: Signals and boxes don't seem to connect at all
Post by: jamespetts on October 18, 2015, 12:17:49 AM
I have now updated the narrow gauge signals so as to work with signalboxes; can you confirm whether the error has now abated?
Title: Re: Signals and boxes don't seem to connect at all
Post by: Junna on October 18, 2015, 02:27:26 PM
It's with standard signals though. There's been no change to the signals in the pak since last I updated ,but I'll guess I'll look into that.
Title: Re: Signals and boxes don't seem to connect at all
Post by: jamespetts on October 18, 2015, 09:21:01 PM
Is this with your own version of Pak128.Britain-Ex or the Swedish pakset, or is it with the official Pak128.Britain-Ex from Github? How is the Swedish pakset getting on, incidentally? That is a splendid project.
Title: Re: Signals and boxes don't seem to connect at all
Post by: Junna on October 19, 2015, 03:13:50 AM
It's the pak-britain one. I tried to update makeobj, as evidently it had become out of date, but I get compile errors with makobj-experimental now:

(http://i.imgur.com/uXaY5aC.png)
Title: Re: Signals and boxes don't seem to connect at all
Post by: jamespetts on October 19, 2015, 10:38:38 PM
Thank you for that report: I have now fixed this issue. I should be grateful if you could let me know when you have tried again how you get on.
Title: Re: Signals and boxes don't seem to connect at all
Post by: Junna on October 21, 2015, 07:49:42 PM
That sorted it. But it crashes an awful lot when working with signalling, it seems?
Title: Re: Signals and boxes don't seem to connect at all
Post by: jamespetts on October 21, 2015, 11:49:44 PM
Can you give steps to reproduce a crash so that I can fix it?
Title: Re: Signals and boxes don't seem to connect at all
Post by: Junna on October 22, 2015, 05:43:31 PM
Well, resignalling an old section of line, deleting the old signals, then placing several signals and boxes with the game paused -- when unpaused, it will randomly crash. Not always; but every other time or so, it has crashed for me.
Title: Re: Signals and boxes don't seem to connect at all
Post by: jamespetts on October 22, 2015, 09:31:38 PM
What type of signals were you using? Are you able to upload a saved game in which this occurs?

Edit
: Also, did you delete the signals individually, or by deleting their signalbox?
Title: Re: Signals and boxes don't seem to connect at all
Post by: Junna on October 23, 2015, 03:27:11 PM
It's 1875, so it's semaphores mostly with different boxes depending on the sections (small and intermediate size boxes mostly).

Pak:
http://www.mediafire.com/download/xhdb9oa4hf4qbq1/Pak128.Britain-Ex-0.9.2J.rar

Save:
http://www.mediafire.com/download/bbosb8ba53zbj4y/tass10.sve

It doesn't seem to matter much where it is done, but whenever swaths of signals are removed on a section, new signals are placed with boxes, etc, and the game is unpaused, it will often (but not always) crash. Perhaps it has to do when any of the blocks are occupied by trains? It works fine if you save before unpausing-- you can then load the game after it has crashed with no issues.
Title: Re: Signals and boxes don't seem to connect at all
Post by: jamespetts on October 23, 2015, 08:21:43 PM
I see that you have a number of time interval signals that you are replacing: is it only on deleting time interval signals that you get the trouble? I did fix a possible issue with this last night, although that fix is more of a workaround with some side effects and I am hoping to come up with a proper fix soon; but, in any event, with the latest commit, this should not crash any longer.