AI collision ending scenario

[bhyde]

Does anyone know of a workaround to avoid "AI collision" ending scenario crashes - have experienced this on Ox-Padd (lost in the shuffle) and Newcastle-York (need for speed) - managed to complete "need for speed" in the end by reloading and speeding up so that I didnt experience the AI consist in the same area but I`m stumped by "lost in the shuffle", it seems to happen south of Reading whatever I do. The only thing I can think of is to disable the services which cause the crash but I dont know how to do this safely without ruining the rest of the scenario.

[lwaxl00]

I dont think you can do anything to the scenario's till the editors are released.

[bhyde]

I think its possible to enter world editor during the scenario and make changes to trains which have appeared in the route but I would have to re-save then and I think this may ruin the rest of the scenario, may try to back up the route tonight then try this. Has anyone else experienced this problem?

[jamesinbolton]

Yeah act ended just after passing tilehurst for me on "lost in the shuffle".

Grr :bad-words:

[ianm42]

These AI crashes do seem to be dependent on how long it takes you to drive through the scenario. Some people manage to complete most of the scenarios OK, some get the crashes. Not sure if you have to be quick or slow or on-time to avoid the crahes though.

[jamespetts]

I suspect that the problem arises from the known deficiencies in signalling.

[Dralex]

Had the same problem once. On another attempt I could successfully complete the scenario (Lost in the shuffle). As far as I know, there is a signal missing that should protect the first crossover your playertrain is to take after having left Didcot. If you are too fast then you'll encounter a head-on collision with the oncoming passenger train (whose path is also not protected at that very same crossover - happened to me on yet another attempt). I think you should not go too fast with your freight, or else.

Dralex

[ewsjo]

Right then, I have it saved in Didcot yard ready to depart for Reading. The first time I drove the route, I was quite easy on the speed, coasting a lot of the way, and taking it easy over crossovers, as I knew they had to be taken, but was unsure where they were exactly. I was sat on a red in Reading having done the loading/unloading for about a minute. I then tried it about 3 or 4 times again, but travelling quicker, didn't get held on the red, but get the AI issue as I depart Reading for Slough.
Also, with the Return Ticket activity, I didn't get held on the red like others have reported, but I did drive very slowly becuase I knew it was there, and the F3 display showed it change from red to green literally as I was 5 or 10m away from the AWS magnet

HTH

cheers

jo

[AndiS]

I am sure that both error sources will strike on the default routes. A) The signals have several issues as they are in the box. I am working on a fix. B) Route builders will have made errors. If there is a crossover where they forgot to place a signal, or if someone put a link of a signal in the wrong place, there can be accidents at that location, if two trains happen to arrive there at the same time.

The fact that AI traffic is sparse and RSD are very reluctant regarding timetables means to me that they are well aware of the problems.

What we need is a task force for each of the routes to fix it. There is already some discussion on that going on: http://forums.uktrainsim.com/viewtopic. ... 15&t=75701 .