Upcoming Games

No games to display

Full list
Add a game

Upcoming Events

No events to display

Three issues found

You are here: Home > Forum > Simulations > Released > South Humberside > Three issues found

Page 1 of 1

Three issues found 31/03/2011 at 16:30 #2729
Underwood
Avatar
746 posts
Hello,

Again please let me know if I have done something wrong and had a dim moment to make it work, but the issues I have had I have tried to get them to work.

1. Barnetby Rec Sidings- Brocklesby Jn issue. I routed a train from Signal BE33 to the Up Fast towards Brocklesby Junction, and I set the path down the ladder by clicking through all the shunt signals (BE33 - BE35 - BE39 - BE42 - BE25 - BE21) and train stopped at BE35 to report that he had a wrong route set. The Timetable location was Barnetby Reception - Brocklesby Junction - Harborough - Grimsby Town - Cleethorpes. I abandoned the TT, let it run down the ladder to BE21 and restored TT and set the next location Brocklesby Junction, and it worked fine after.

2. Great Coates - Grimsby Marsh Jn issue. Another wrong route complaint from a driver stopped at Signal GD19. I set the route from GD19 - M22 - M4 as the train reverses at Grimsby Marsh Jn sig M34. I told him to abandon the timetable and he passed sig GD19 then I restored the TT and set it to next location Grimsby Marsh Jn rev. It worked fine after.

3. Is there any way to route a train into the Kirkby Lime Sidings loop? There is 2 freight trains I was going to add to my TT that were booked to sit in this loop but I couldn't add them as I couldn't path it into the siding (the TT editor wouldn't have it). Could anyone kindly advise me if there is a way of doing it if I am missing something, or could it be added into the next update otherwise?


Regards,

James.

Log in to reply
Three issues found 31/03/2011 at 16:30 #14627
Underwood
Avatar
746 posts
Hello,

Again please let me know if I have done something wrong and had a dim moment to make it work, but the issues I have had I have tried to get them to work.

1. Barnetby Rec Sidings- Brocklesby Jn issue. I routed a train from Signal BE33 to the Up Fast towards Brocklesby Junction, and I set the path down the ladder by clicking through all the shunt signals (BE33 - BE35 - BE39 - BE42 - BE25 - BE21) and train stopped at BE35 to report that he had a wrong route set. The Timetable location was Barnetby Reception - Brocklesby Junction - Harborough - Grimsby Town - Cleethorpes. I abandoned the TT, let it run down the ladder to BE21 and restored TT and set the next location Brocklesby Junction, and it worked fine after.

2. Great Coates - Grimsby Marsh Jn issue. Another wrong route complaint from a driver stopped at Signal GD19. I set the route from GD19 - M22 - M4 as the train reverses at Grimsby Marsh Jn sig M34. I told him to abandon the timetable and he passed sig GD19 then I restored the TT and set it to next location Grimsby Marsh Jn rev. It worked fine after.

3. Is there any way to route a train into the Kirkby Lime Sidings loop? There is 2 freight trains I was going to add to my TT that were booked to sit in this loop but I couldn't add them as I couldn't path it into the siding (the TT editor wouldn't have it). Could anyone kindly advise me if there is a way of doing it if I am missing something, or could it be added into the next update otherwise?


Regards,

James.

Log in to reply
Three issues found 31/03/2011 at 21:28 #14638
Lardybiker
Avatar
771 posts
I'll look into 1 and 2 as I don't think they've been reported previously.

As for 3, the loop is not suitable as a passing place as its not track circuited, there is a GF at one end which makes automatic operation impossible and its also not very long. Unfortunately, there isn't anyway of doing what you need currently as even if you could route in Kirton Lime Sidings, the train would leave the sim.
Given the above, I don;t think it would be practical to add it.

Log in to reply
Three issues found 01/04/2011 at 03:45 #14648
Lardybiker
Avatar
771 posts
1) I can't see anything wrong with S35 but I could see a train calling from either S33 or S34 given the TT you mention. This has now been fixed for the next release version
2) Fixed for next release version.

Log in to reply