Upcoming Games

(UTC times)


Full list
Add a game

Upcoming Events

No events to display

Motherwell V4.3.1

You are here: Home > Forum > Simulations > Released > Motherwell > Motherwell V4.3.1

Page 2 of 2

V4.3.1 07/03/2018 at 19:39 #106538
VInce
Avatar
579 posts
... And I bought a third monitor with USB video adapter so as I can, using new view and patching one area to another down the AB lines, get most sims completely on the three screens

Vince

I walk around inside the questions of my day, I navigate the inner reaches of my disarray, I pass the altars where fools and thieves hold sway, I wait for night to come and lift this dread away : Jackson Browne - The Night Inside Me
Last edited: 07/03/2018 at 20:57 by VInce
Reason: None given

Log in to reply
The following user said thank you: Ar88
V4.3.1 08/03/2018 at 20:44 #106555
BarryM
Avatar
2158 posts
Have run into a minor Access Violation whilst playing this sim: Game still playable.

Internal exception in MajorCycle stage SIG (EAccessViolation: Access violation at address 00404296 in module 'SimSigLoader.exe'. Read of address F685D88B)

Mantis referral: #19893.

Barry

Barry, Sydney, New South Wales, Australia
Last edited: 08/03/2018 at 20:46 by BarryM
Reason: l

Log in to reply
V4.3.1 09/03/2018 at 17:00 #106561
nnr
Avatar
170 posts
Much improved TT, many thanks.

There's still a snag at M423 however in that some of the "mainline" (ie long!!) trains will pass it on a yellow and stop in the platform, whereas others just sit at it with a red aspect. It does not appear to affect non - stop workings.

I've tried changing the stopping point, but this has had limited success.

Could it be something to do with approach control??
Cheers
N,.

Last edited: 09/03/2018 at 17:01 by nnr
Reason: None given

Log in to reply
V4.3.1 09/03/2018 at 18:50 #106562
postal
Avatar
5264 posts
nnr in post 106561 said:
Much improved TT, many thanks.

There's still a snag at M423 however in that some of the "mainline" (ie long!!) trains will pass it on a yellow and stop in the platform, whereas others just sit at it with a red aspect. It does not appear to affect non - stop workings.

I've tried changing the stopping point, but this has had limited success.

Could it be something to do with approach control??
Cheers
N,.
It is prototypical. I raised this a few weeks ago with Henry Munro who signalled at Motherwell for a lot of years and he confirmed the situation. The interlocking keeps track of the train length from the number of track circuits occupied as the train approaches Motherwell. M423 is held at R for trains over a certain length until M399 is showing a proceed aspect. As things are set up in the sim, pendolinos and voyagers are within the length parameter so M423 will clear but the ECML IC225 sets (and one train of empty coal hoppers which has a crew change in P2) are overlength and held at M423 until M399 is cleared.

That does mean you have to be careful with the empty hoppers (4S34) as there is no point in signalling the train into P2 until you know that the relief crew is going to be there. If you clear M399 to let the train into P2 before the relief crew is available you risk locking up the station while you wait for the relief crew.

“In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe
Last edited: 09/03/2018 at 18:51 by postal
Reason: None given

Log in to reply
The following user said thank you: BarryM
V4.3.1 09/03/2018 at 20:17 #106564
nnr
Avatar
170 posts
Ah, mystery solved. Many thanks for your help.
N

Log in to reply
Motherwell V4.3.1 14/03/2018 at 10:04 #106755
BarryM
Avatar
2158 posts
Running Motherwell's 2006 timetable using latest Loader V4.6.12 train 1S26 at Carstairs at 06:16 finished joining and consequently created 4 error messages: "Bad type for CurrentTrain evaluating" SMC413 PDA twice and Bad type for 413AM PDA twice.

Referred it to Mantis # 0018542

Barry

Barry, Sydney, New South Wales, Australia
Log in to reply
Motherwell V4.3.1 23/03/2018 at 14:16 #106961
John 23
Avatar
176 posts
I'm running V4.3.1 using loader 4.6.12 and TT v4.2.3 0445 start.
I'm finding trains exiting the sim toward Shotts won't pass M626. If instructed manually they cease to be ARS and now won't leave the sim after being authorised to pass signals at danger toward Shotts. Eventually they come up as "No further trips".
Suggestions, please!

Log in to reply
Motherwell V4.3.1 23/03/2018 at 15:10 #106963
Peter Bennet
Avatar
5402 posts
John 23 in post 106961 said:
I'm running V4.3.1 using loader 4.6.12 and TT v4.2.3 0445 start.
I'm finding trains exiting the sim toward Shotts won't pass M626. If instructed manually they cease to be ARS and now won't leave the sim after being authorised to pass signals at danger toward Shotts. Eventually they come up as "No further trips".
Suggestions, please!
You need timetable 4.4.1, which should come from the updates.

Peter

I identify as half man half biscuit - crumbs!
Log in to reply
Motherwell V4.3.1 23/03/2018 at 16:14 #106964
John 23
Avatar
176 posts
Strange: I'm fully updated and I'm not being offered that TT via the Loader.
Last edited: 23/03/2018 at 16:29 by John 23
Reason: None given

Log in to reply
Motherwell V4.3.1 23/03/2018 at 16:52 #106965
Peter Bennet
Avatar
5402 posts
Check the timetable folder and see what's there.
The timetable no longer has a version number in the title and should be "last modified" on 1 March.

If you delete the earlier ones then you should be re-offered the updates.

Peter

I identify as half man half biscuit - crumbs!
Log in to reply
The following user said thank you: John 23
Motherwell V4.3.1 23/03/2018 at 17:07 #106966
John 23
Avatar
176 posts
That seems to have got it sorted.
Log in to reply
Motherwell V4.3.1 23/03/2018 at 19:07 #106971
bill_gensheet
Avatar
1413 posts
I have not yet looked at the 1984 timetable in respect of this update.
If anyone is having a go then please point me to any fixes needed.

The ARS is known about and not fixable, causes trouble with the loco run round at Holytown.

The 2E at Newton is news to me. I do not recall any problems with them. Will look when time allows.
This may also kick the 1993 timetable into action.

Bill

Log in to reply
Motherwell V4.3.1 26/04/2018 at 00:51 #107700
bill_gensheet
Avatar
1413 posts
Have checked a 1984 timetable with the new sim data. The usual problem areas seem OK, so I conclude that v2 is still OK.
I did not find any problems with 2E services at Newton.
Sleepers at Mossend behave OK
ARS gets confused by the run round at Holytown

Note that there are earlier versions of the 1984 timetables that WILL NOT be OK.

Updates attached, also available in the downloads. As user timetables these DO NOT come though the update process.

Bill

Post has attachments. Log in to view them.
Last edited: 26/04/2018 at 01:17 by bill_gensheet
Reason: None given

Log in to reply
The following user said thank you: BarryM
Motherwell V4.3.1 26/04/2018 at 09:44 #107701
postal
Avatar
5264 posts
bill_gensheet in post 107700 said:
Have checked a 1984 timetable with the new sim data. The usual problem areas seem OK, so I conclude that v2 is still OK.
I did not find any problems with 2E services at Newton.
Sleepers at Mossend behave OK
ARS gets confused by the run round at Holytown

Note that there are earlier versions of the 1984 timetables that WILL NOT be OK.

Updates attached, also available in the downloads. As user timetables these DO NOT come though the update process.

Bill
File naming seems to fall foul of Geoff's desired position in this thread.

“In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe
Log in to reply
Motherwell V4.3.1 28/04/2018 at 00:18 #107723
bill_gensheet
Avatar
1413 posts
>>
File naming seems to fall foul of Geoff's desired position in this thread.
<<

It is a user timetable so is not being distributed via updater. That is where the problem of having version numbers comes from as it prevents the updater updating.
Therefore those getting it manually do need to know the version from the filename.

I am avoiding decimals in the name, the problem noted in that thread.


regards
Bill

Log in to reply