Upcoming Games


Full list
Add a game

Upcoming Events

Who's Online

StephenB2988, jem771, Jriver, CV409i (4 users seen recently)

Guiseley Wrong Platform

You are here: Home > Forum > Simulations > Released > Leeds Northwest > Guiseley Wrong Platform

Page 1 of 1

Guiseley Wrong Platform 11/01/2018 at 11:04 #104966
njimiller
Avatar
134 posts
Just FYI.
Ilkley-bound trains get a wrong platform penalty at Guiseley platform 1 despite it being the correct platform.

Thanks
Nick

Log in to reply
Guiseley Wrong Platform 11/01/2018 at 12:33 #104968
MarkC
Avatar
1035 posts
confirmed

Mantis 0019231

After 'Monday' and 'Tuesday' even the calendar says 'WTF'
Last edited: 11/01/2018 at 12:39 by MarkC
Reason: None given

Log in to reply
Guiseley Wrong Platform 13/01/2018 at 03:27 #105020
Noisynoel
Avatar
989 posts
Fixed in v1.3
Noisynoel
Log in to reply
Guiseley Wrong Platform 25/05/2018 at 16:55 #108216
phil1044
Avatar
143 posts
Noisynoel in post 105020 said:
Fixed in v1.3
Has Version 1.3 been released to fix the Guiseley platform problem does anyone know ?

Log in to reply
Guiseley Wrong Platform 25/05/2018 at 17:06 #108217
headshot119
Avatar
4444 posts
phil1044 in post 108216 said:
Noisynoel in post 105020 said:
Fixed in v1.3
Has Version 1.3 been released to fix the Guiseley platform problem does anyone know ?
No 1.2 is the latest version available.

The latest version is always available via the check for updates feature.

"Passengers for New Lane, should be seated in the rear coach of the train " - Opinions are my own and not those of my employer
Log in to reply
The following user said thank you: phil1044
Guiseley Wrong Platform 25/05/2018 at 22:39 #108224
phil1044
Avatar
143 posts
headshot119 in post 108217 said:
phil1044 in post 108216 said:
Noisynoel in post 105020 said:
Fixed in v1.3
Has Version 1.3 been released to fix the Guiseley platform problem does anyone know ?
No 1.2 is the latest version available.

The latest version is always available via the check for updates feature.
Yea I know that, just Noel said in the quote above that it was fixed in v 1.3. Just thought I may have missed something.
No worries, thanks anyway

Log in to reply