Page 1 of 1
| Set Swap TRTS 06/02/2012 at 19:08 #28960 | |
guidomcc
246 posts |
I had a small issue with Lime St, but a really great sim by the way! I was playing throat + p1 + p9 closed and I needed to perform a set swap between two 156s in p2. This I did, and afterward the front 156 TRTS'd and departed immediately and was on time (just!) and once it was out the platform the other 156 TRTS'd immediately, even though it had 10 minutes to departure time. I have searched the forum but excuse me if I have missed anything. :S PS If anybody wonders why I didn't just hold the first 156 outside Lime St and wait for the other one to depart, it was my first set swap and I took a while to do it :side: Log in to reply |
| Re: Set Swap TRTS 06/02/2012 at 19:40 #28966 | |
|
mfcooper
707 posts |
It can depend on how you did the swap. Did you use "Run to Another Timetable" on both trains? Did you set the next location correctly?
Log in to reply |
| Re: Set Swap TRTS 06/02/2012 at 20:00 #28970 | |
postal
5263 posts 
|
Something similar at Euston has been reported to Clive as a bug. I was stepping up incoming sets due to a points failure locking a set into one of the platform and running to a new TT was generating a TRTS before due time. Clive has identified it as a core code bug and is taking steps to fix it.
“In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe Log in to reply |
| Re: Set Swap TRTS 06/02/2012 at 20:21 #28971 | |
|
Noisynoel
989 posts |
Have you got a save of the probkem, might help ID whatb the issue is
Noisynoel Log in to reply |
| Re: Set Swap TRTS 06/02/2012 at 20:22 #28972 | |
|
guidomcc
246 posts |
Quote:It can depend on how you did the swap. Did you use "Run to Another Timetable" on both trains? Did you set the next location correctly?i used run to another timetable, yes. and i set the next location as lime street. Quote: Something similar at Euston has been reported to Clive as a bug. I was stepping up incoming sets due to a points failure locking a set into one of the platform and running to a new TT was generating a TRTS before due time. Clive has identified it as a core code bug and is taking steps to fix it.this sounds like it. thanks for the quick replies 
Log in to reply |