Upcoming Games

(UTC times)


Full list
Add a game

Upcoming Events

No events to display

Who's Online

Trains Not Calling Back After being Told To Call Back - Tunstead Sdgs

You are here: Home > Forum > Simulations > Released > Peak District > Trains Not Calling Back After being Told To Call Back - Tunstead Sdgs

Page 1 of 1

Trains Not Calling Back After being Told To Call Back - Tunstead Sdgs 03/08/2019 at 18:08 #119828
Phil-jmw
Avatar
669 posts
Running the 2017 TT, I've noticed that if trains call up ready from Tunstead Sdgs and you ask them call back in 2, 5 or 15 mins, they never call back again but do grey out in the F4 window as if they have entered. I can't recall which trains it happened with earlier when I was experiencing some congestion but the latest is 6E00 0500 Tunstead - West Burton.

I've attached a save.


Regards,

Phil.

Post has attachments. Log in to view them.
Log in to reply
Trains Not Calling Back After being Told To Call Back - Tunstead Sdgs 03/08/2019 at 18:34 #119829
jc92
Avatar
3625 posts
There was previously a core code issue with trains calling back immediately if told to wait 2 mins. Not sure if its related.

Is this only affecting tunstead or other entry points too?

"We don't stop camborne wednesdays"
Log in to reply
Trains Not Calling Back After being Told To Call Back - Tunstead Sdgs 03/08/2019 at 18:39 #119830
Phil-jmw
Avatar
669 posts
Only Tunstead as far as I can tell Joe. I made 6L73 wait 15 mins when he first called up from Peak Forest and he called back as requested.
Log in to reply
Trains Not Calling Back After being Told To Call Back - Tunstead Sdgs 03/08/2019 at 22:37 #119833
jc92
Avatar
3625 posts
I can't reproduce this with a test timetable and have never had this issue before (I am using a newer test version of the sim however). raised on mantis - 26435 for further testing.
"We don't stop camborne wednesdays"
Log in to reply
Trains Not Calling Back After being Told To Call Back - Tunstead Sdgs 05/08/2019 at 17:05 #119877
TylerE
Avatar
149 posts
Don't have a save, but this happened to me a couples days ago.

Told to call back in 15, never did.

Bug that snuck into core?

Log in to reply