Page 1 of 1
| (Default timetable) duplicate Waterloo loop trains rules issue? 23/01/2015 at 22:39 #68322 | |
Muzer
718 posts |
After having a particularly bad time of it with various track circuit failures, etc., I've noticed there have been multiple Waterloo loop trains (2Oxx) that appear from Kingston before the train has departed Waterloo (Winsdor side). I don't believe I've noticed vice versa happening but I might just have missed it. For example, right now I have two 2O61s onscreen at once. It causes havoc with viewing timetables and the ARS. Is this intentional? Or is there an issue with the rules? Post has attachments. Log in to view them. Log in to reply |
| (Default timetable) duplicate Waterloo loop trains rules issue? 23/01/2015 at 23:06 #68323 | |
|
GW43125
495 posts |
How late is the train leaving Waterloo? If the train is very late, the inbound working may appear before the outbound disappears. Maybe there's something with the rules? However, it's the same train coming in to Waterloo as it was leaving, so I doubt this should happen. Jamie. Last edited: 23/01/2015 at 23:07 by GW43125 Log in to reply |
| (Default timetable) duplicate Waterloo loop trains rules issue? 24/01/2015 at 00:25 #68324 | |
BarryM
2158 posts |
Ordinarily timetables are compiled for normal running, maybe with odd delays from a depot. If you wish to create major failures, don't expect the timetable to adjust itself for your liking. Obviously the author has not taken loop train delays into account. Have fun. lol! Barry Barry, Sydney, New South Wales, Australia Log in to reply |
| (Default timetable) duplicate Waterloo loop trains rules issue? 24/01/2015 at 00:44 #68326 | |
|
Muzer
718 posts |
I didn't intend to create a major failure, it just happened by chance! (If you're interested, a down slow train was delayed at Wimbledon, so I started sending everything on the down fast just to get past the delayed train Wimbledon station. Unfortunately, just as the train delay ended and a train was passing from the down fast to the down slow, a track circuit failure occurred *on the junction* from the down fast to the down slow, which occurred in the peak and lasted over an hour, meaning I had to route every train on the down fast through Wimbledon, then pass the signal at the end of the platform at danger onto the down slow, then for fast trains immediately cross them back over to the down fast! This during the peak! Nightmare. I suppose in real life trains would be turned back (where?), but I always feel like a cheater doing that because in real life it would count as a train cancellation which would be penalised). Log in to reply |
| (Default timetable) duplicate Waterloo loop trains rules issue? 24/01/2015 at 09:29 #68332 | |
|
GW43125
495 posts |
In times of severe disruption, the first trains to be cancelled (throughout) are the Dorking trains, with ticket acceptance on Southern from Epsom. Next to go are the loopers- these will either be turned back at somewhere like Kingston, or just cancelled throughout, if it's a problem on the main side, the Shepperton trains may also be diverted via Twickenham. Hope this helps, Jamie. Log in to reply |
| (Default timetable) duplicate Waterloo loop trains rules issue? 24/01/2015 at 10:33 #68334 | |
|
JamesN
1608 posts |
It shouldn't be happening, something must be wrong with the rules there. Thanks for bringing it to my attention.
Log in to reply |
| (Default timetable) duplicate Waterloo loop trains rules issue? 06/02/2015 at 22:26 #68957 | |
|
JamesN
1608 posts |
Update to this - loading the save causes an access violation: "Access violation at address 40004D3C in module 'rtl60.bpl' Read of address is 00000085." All the rules that should prevent all the 2Oxx re-entering early are present in the TT, and I can't trigger the bug manually so something is definitely up here. Further investigation required. Can I confirm which versions of loader and simulation were in use? (Help > About if unsure) Log in to reply |
| (Default timetable) duplicate Waterloo loop trains rules issue? 07/02/2015 at 01:19 #68958 | |
|
Muzer
718 posts |
I'm very anal in keeping things up-to-date (I check the SimSig forum most days, for instance), so I'd be very surprised if it weren't the newest version available at the time of the first post in this thread. HOWEVER, the game was ORIGINALLY started with the versions available shortly after Wimbledon's release. I think there has been a loader update and a sim update too since then, so perhaps it's simply an incompatibility between the sim and loader update and the save game. Log in to reply |