Atomic Systems

I am trying the scenario 'BR 1A16 Penzance to Paddington' on the W.M. route. When I get to between Reading and Paddington, the sim stops with an A.I. collision somewhere. I have reloaded the route in case this has recently been fixed, but the problem is still there.
Any ideas, please?
Many thanks,
Stuart.

earwigo wrote:the sim stops with an A.I. collision somewhere

The message on screen will give the lat. and long. of the collision---you might just have enough time to make a note of them before the message disappears and providing that information will go a long way towards finding the cure to the problem.

Thanks. I'll make an effort to get whatever data I can.

It's usually caused by an AI train not starting when it should so what should be a following train crashes into the back of it. There is no equivalent to track circuits in TS so, once it has sent the move instruction to an AI train, the game assumes it's moved. A failure to move is not detected.

The errant train is likely to be at the coordinates shown on screen. Go into the scenario editor and enter the coordinates into the box in the top centre of the screen and press the arrow symbol to move there. I've found that a non-starting AI train is often caused by it being too near a signal. Move the train away from the signal (in either direction) and save. The train should now run.

This is a difficult error to eradicate because it appears to be system specific. A scenario will work fine on the author's computer and fail on a different one, while running fine on several more.

Keith

Thanks, Keith.
I have attached a screen grab showing the error message.
I'll try what you suggest.
Stuart.

Not a collision then....more one of the train *going the wrog way*, possibly if the points have been 'locked' to path another service correctly.

Oh dear! That's one I've never got to the bottom of. Best of luck!

Keith

Were you running to time Stuart?...if you were late and that held other services it could cause a 'ripple in the space/time continuum' which could confuse the game with regards to pathing other services.

Yes I was running to time!

OK, then a likely cause is that the updates to the route have forced a re-calculation of the pathings, so changing the start time sof whichever services are involved may be needed, Dead easy to say of course, and based on the assumption that another service is actually involved, but the timings would be an obvious place to start.

I think that this scenario came with Service Pack 2 and it was reported "faulty" at the time and was fixed in Service Pack 4??
Maybe not - could be worth reporting to Just Trains as they have fixed the scenarios that I have reported on WML.
pH

Has the op all the updates ? one came out today https://www.justtrains.net/support/west ... _term=here

Yes I've kept updating as fixes are released.