Upcoming Games


Full list
Add a game

"Internal error" shortly after start-up

You are here: Home > Forum > Simulations > Released > Motherwell > "Internal error" shortly after start-up

Page 1 of 1

"Internal error" shortly after start-up 31/03/2020 at 10:28 #125194
lazzer
Avatar
478 posts
Just a quick error to report shortly after starting a new game using the 1984 TT.

I was literally two minutes in and the error message shown in the attached image popped up. I was able to click OK and continue. I am assuming that 0D99-P must have entered at Ravenscraig No. 4 with no headcode (I didn't see it enter at M491 but I saw that headcode **** had stepped up into the berth at M503). I've never seen this happen before, and I play this sim and TT regularly.

I've also attached a save of the game taken immediately after it happened.


Post has attachments. Log in to view them.
Last edited: 31/03/2020 at 10:28 by lazzer
Reason: None given

Log in to reply
"Internal error" shortly after start-up 31/03/2020 at 10:44 #125195
y10g9
Avatar
585 posts
Online
Lazzer, could you please confirm which version of Motherwell, and which version of the TT you are using please. I haven't been able to reproduce it first time round with V4.5 of the sim and V3 of the TT. Also would you mind attaching a copy of the Log File, the message shows there are 7 errors in total, but the sim will only show the dialog for 1 of them
Last edited: 31/03/2020 at 10:53 by y10g9
Reason: None given

Log in to reply
"Internal error" shortly after start-up 31/03/2020 at 11:04 #125197
Peter Bennet
Avatar
4729 posts
CCOVEU is to do with an up train approaching COVE crossing.
It's querying item 2 of 7 in that piece of code.

Peter

I identify as half man half biscuit - crumbs!
Log in to reply
"Internal error" shortly after start-up 31/03/2020 at 11:15 #125201
y10g9
Avatar
585 posts
Online
Have reproduced it now, Mantis 29848 raised
Log in to reply
"Internal error" shortly after start-up 31/03/2020 at 11:19 #125202
lazzer
Avatar
478 posts
y10g9 in post 125195 said:
Lazzer, could you please confirm which version of Motherwell, and which version of the TT you are using please. I haven't been able to reproduce it first time round with V4.5 of the sim and V3 of the TT. Also would you mind attaching a copy of the Log File, the message shows there are 7 errors in total, but the sim will only show the dialog for 1 of them
Yeah, I'm using Loader 4.15.1, with Motherwell version 4.5. The timetable filename is Motherwell_1984_v2.WTT.

I've attached the part of the log file that relates to this problem. But as I was going through it I remembered I'd had another error when I was playing yesterday. It must have been the same one, as the log contains the same references to "CCOVEU". I've put both days' logs in the file, separated by a couple of line breaks.

And in response to Peter's comment - the train approaching Cove crossing in both cases is 4S50. With regard to 0D99-P's missing headcode at Ravenscraig 4, would that have anything to do with me choosing "Standard" difficulty at the start instead of the default "Perfect", or is that something else?

Post has attachments. Log in to view them.
Last edited: 31/03/2020 at 11:30 by lazzer
Reason: None given

Log in to reply
"Internal error" shortly after start-up 31/03/2020 at 11:25 #125204
Sacro
Avatar
1057 posts
Yes, "standard" means more realistic, so you won't always get entry headcodes auto populated, not all sidings have the equipment in real life, they phone you up and expect you to enter it.
Log in to reply
"Internal error" shortly after start-up 31/03/2020 at 11:30 #125206
lazzer
Avatar
478 posts
Sacro in post 125204 said:
Yes, "standard" means more realistic, so you won't always get entry headcodes auto populated, not all sidings have the equipment in real life, they phone you up and expect you to enter it.
I did wonder, as I tend to not bother changing that setting most of the time.

Last edited: 31/03/2020 at 11:30 by lazzer
Reason: None given

Log in to reply
"Internal error" shortly after start-up 31/03/2020 at 11:33 #125207
y10g9
Avatar
585 posts
Online
lazzer in post 125202 said:
y10g9 in post 125195 said:
Lazzer, could you please confirm which version of Motherwell, and which version of the TT you are using please. I haven't been able to reproduce it first time round with V4.5 of the sim and V3 of the TT. Also would you mind attaching a copy of the Log File, the message shows there are 7 errors in total, but the sim will only show the dialog for 1 of them

Yeah, I'm using Loader 4.15.1, with Motherwell version 4.5. The timetable filename is Motherwell_1984_v2.WTT.

I've attached the part of the log file that relates to this problem. But as I was going through it I remembered I'd had another error when I was playing yesterday. It must have been the same one, as the log contains the same references to "CCOVEU". I've put both days' logs in the file, separated by a couple of line breaks.

And in response to Peter's comment - the train approaching Cove crossing in both cases is 4S50. With regard to 0D99-P's missing headcode at Ravenscraig 4, would that have anything to do with me choosing "Standard" difficulty at the start instead of the default "Perfect", or is that something else?
Quick look through the Log file, it is the same errors that I managed to reproduce putting a train across Cove crossing. and the same errors that you got up on the 2 different occasions. At a quick glance from testing across the different eras it looks to be because of the Auto Lower feature for the later eras

Log in to reply
"Internal error" shortly after start-up 31/03/2020 at 14:47 #125222
Peter Bennet
Avatar
4729 posts
Found it's just trying to execute an surplus instruction so not critical to anything, just annoying.

I'll give it a couple of days to see if anything else comes up.

Peter

I identify as half man half biscuit - crumbs!
Log in to reply
"Internal error" shortly after start-up 31/03/2020 at 15:44 #125226
lazzer
Avatar
478 posts
Peter Bennet in post 125222 said:
Found it's just trying to execute an surplus instruction so not critical to anything, just annoying.

I'll give it a couple of days to see if anything else comes up.

Peter
It only does it for the first train in the sim (4S50 in this case). Everything after that over the crossing is fine.

Log in to reply
"Internal error" shortly after start-up 31/03/2020 at 16:21 #125228
Splodge
Avatar
436 posts
^ Yes, found the same. First train on loading (new or from a save), rather than of the day.

One other thing I've found - the banner repeaters on Motherwell P2 don't appear to work for the diverging route - when the approach control allows M399 to pull off, the train is shown occupying beyond the repeater but the banner doesn't change - however the repeater for the main route will pull off with a train occupying beyond it (which is the behaviour I'd expect, and appears to be the case here https://flic.kr/p/2iE9BRU)

The banner graphic also changes between eras - though I presume this is to allow the shunt move to be set in the 80s mode.

There's the right way, the wrong way and the railway.
Log in to reply
"Internal error" shortly after start-up 31/03/2020 at 19:23 #125240
y10g9
Avatar
585 posts
Online
lazzer in post 125226 said:
Peter Bennet in post 125222 said:
Found it's just trying to execute an surplus instruction so not critical to anything, just annoying.

I'll give it a couple of days to see if anything else comes up.

Peter
It only does it for the first train in the sim (4S50 in this case). Everything after that over the crossing is fine.
It you will only get the error message displayed the first time that the error happens in that session. The error still happens every time that the cove crossing is activated, however all further internal error boxes are suppressed, but the error will still be logged in the log file

Log in to reply
"Internal error" shortly after start-up 19/04/2020 at 14:30 #126022
markt
Avatar
36 posts
lazzer in post 125226 said:
Peter Bennet in post 125222 said:
Found it's just trying to execute an surplus instruction so not critical to anything, just annoying.

I'll give it a couple of days to see if anything else comes up.

Peter
It only does it for the first train in the sim (4S50 in this case). Everything after that over the crossing is fine.
Same fault occurred with a 4:45 seed start on the default timetable, 6S43 approaching in this case.

Quick question which may be answered elsewhere - Cove crossing lowered itself, is this prototypical? It was when I went to 'clear' the crossing that the error flagged up

Log in to reply
"Internal error" shortly after start-up 28/04/2020 at 21:11 #126412
9pN1SEAp
Avatar
345 posts
I had this error at the start of a multi-play resume and the barrier now seems to auto-raise when down trains approach, even when auto is off !
Post has attachments. Log in to view them.
Jamie S (JAMS)
Log in to reply
"Internal error" shortly after start-up 29/04/2020 at 11:04 #126419
Albert
Avatar
728 posts
Online
Running Motherwell with ARS on, I can only partially reproduce what we had last night. If auto-raise is unticked, the barriers raise again as soon as they're down, but with auto-raise ticked and ARS on the crossing functions normally.

I suspect running with ARS off made the problems worse yesterday night.

AJP in games
Log in to reply
"Internal error" shortly after start-up 30/04/2020 at 10:56 #126444
danners430
Avatar
10 posts
9pN1SEAp in post 126412 said:
I had this error at the start of a multi-play resume and the barrier now seems to auto-raise when down trains approach, even when auto is off !
Aye, that was myself fighting the bug - First instance I had two trains following very closely, so I turned off auto-raise. This caused the barriers to immediately raise in front of the train, causing the signal to fall back to danger, and a very annoyed driver!
After that, I repeatedly tried to lower the barriers, which worked... but a split second after I pressed "Clear" the barriers raised again - they were only down long enough for the approach signals to flicker yellow.
I eventually got it to behave by putting it back on full auto, with the approach signals also on automatic... but even then I got occasional bugs - occasionally the barriers would lower really rather early for an approaching train, then go back up again - all before the train got within four blocks of the crossing. It would then again lower itself automatically when the train was closer, which worked...

All in all a very strange evening!

Log in to reply