Page 1 of 1
| Unauthorised Passing Signal at Danger 18/01/2014 at 00:32 #53989 | |
LucasLCC
94 posts |
 This shows 2B00 having SPAD through signal 184. This isn't the first train I've noticed that has ignored a signal on this. Over the course of the session 176 and 145 were also subject to similar issues. A bit of a pain! Lucas Log in to reply |
| Unauthorised Passing Signal at Danger 18/01/2014 at 00:57 #53990 | |
|
Stephen Fulcher
2023 posts |
Trains in SimSig do not normally "ignore" signals. Real SPADs are something that are not allowed for in the coding, which was I believe a policy decision taken in the earliest days of SimSig. I know we had trouble a couple of years ago, maybe even longer now, where people in multiplayer sessions were messing around authorising trains to pass signals at danger without cause etc. and hope this sort of thing has not made a reoccurance. Do you have a save game by any chance from just before this happened? Log in to reply |
| Unauthorised Passing Signal at Danger 18/01/2014 at 01:04 #53991 | |
|
LucasLCC
94 posts |
Afraid not. But it has happened in the past two sessions we've held on Saltley. There was no authorisations to pass any signals at that given time. Due to the fact there was once case where I needed to stop a train to let another past. I will see if I can repeat it with another whilst this session continues.
Log in to reply |
| Unauthorised Passing Signal at Danger 18/01/2014 at 01:13 #53992 | |
|
Stephen Fulcher
2023 posts |
Seems odd that the TD stepped as well - that cannot happen without a route set (and signal off in a real signal box). I have played Saltley a lot, especially when it was first released as I lived in the area at the time and knew it very well. I also played it solo a lot, which resulted in a lot of trains detained at just about every conceivable signal and never had any issues with trains going past them. I know there was an issue with the Incident Panel command to "pass next signal irrespective....." with the older sims, but again this would require some form of user intervention. Log in to reply |
| Unauthorised Passing Signal at Danger 18/01/2014 at 03:31 #53993 | |
GeoffM
6280 posts 
|
I've had a look at the Saltley data and S184 is correctly defined at the end of track T412. As Stephen correctly notes, the TD appears to have stepped as well - or somebody has re-interposed it. Again, checking the data and it correctly requires R184AM set to step. Yet clearly there was no route set because (a) there is no route locking beyond the occupancy; (b) there is a DOFI set in the opposite direction (which itself is odd as there is nothing set the other way but here I do see a fault in the data - but only to release the DOFI, and I can see that you likely did have an up train via P1 at Moor St recently from the reversed points, which explains that one). Again, as Stephen correctly notes, trains will not pass a signal at danger unless commanded to do so by the user. Without further information like a save, my conclusion at this point is that the host authorised the train past the signal at danger and somebody manually re-interposed the description. The train got stuck at the reversed points because they weren't in the correct position to continue. (Saltley.exe is relatively old; the Loader logs a lot more detail now which would have been helpful in this kind of situation) SimSig Boss Last edited: 18/01/2014 at 03:32 by GeoffM Log in to reply |
| Unauthorised Passing Signal at Danger 18/01/2014 at 12:41 #53998 | |
|
AndyG
1834 posts |
Note that in mplay sessions it is possible for clients to force trains past a signal at danger, without the host's knowledge.
I can only help one person a day. Today's not your day. Tomorrow doesn't look too good either. Log in to reply |