Upcoming Games

(UTC times)


Full list
Add a game

Upcoming Events

No events to display

Unknown problems (Vic C)

You are here: Home > Forum > Simulations > Released > Victoria Central > Unknown problems (Vic C)

Page 1 of 1

Unknown problems (Vic C) 08/04/2015 at 17:28 #70864
rodney30
Avatar
165 posts
having been playing this sim with the the january to may 2015 tt in 2014 version and latest version of loader 4.4.

i keep getting messages up saying something wrong with xxxx. then sim closes.

attached is a copy of the game.

hope someone can help.

rodney 30

Post has attachments. Log in to view them.
Log in to reply
Unknown problems (Vic C) 08/04/2015 at 17:34 #70865
GeoffM
Avatar
6376 posts
Online
I've run your save and have not seen any problems. Please elaborate as to the exact message and what you were doing at the time.
SimSig Boss
Log in to reply
Unknown problems (Vic C) 08/04/2015 at 17:52 #70866
rodney30
Avatar
165 posts
I was conrolling the crystal palace panel. I was at about 8am.

The following trains have issues.

5C02-1 and 5K90-1 from Battersea Park sidings to Victoria do not step up the tt.

1U61 which forms 5T61
3A00 which forms 3E05
2L05 which forms 1H02.

The message is

Interal Error: Exceeption (train number) in DoStation (Econvert Error is not a valid integer value)

rodney 30

Log in to reply
Unknown problems (Vic C) 08/04/2015 at 17:57 #70867
GeoffM
Avatar
6376 posts
Online
Thanks, that's somewhat more helpful!
SimSig Boss
Log in to reply
Unknown problems (Vic C) 08/04/2015 at 18:09 #70868
rodney30
Avatar
165 posts
No problem Geoff i didn't relise that I had asked the query properly.

Rodney 30

Log in to reply
Unknown problems (Vic C) 08/04/2015 at 18:35 #70870
GeoffM
Avatar
6376 posts
Online
Found the problem: some in-development code that wasn't coping terribly well.
SimSig Boss
Log in to reply
The following user said thank you: rodney30
Unknown problems (Vic C) 09/04/2015 at 05:46 #70909
clive
Avatar
2789 posts
" said:
Found the problem: some in-development code that wasn't coping terribly well.
My fault: I'd left some experimental stuff in that shouldn't have ever been activated because nobody knew the secret runes to make it happen. Then somebody made a trivial typing mistake that triggered it.

Log in to reply