I got the derailment as well, indeed a few miles out of West Wycombe. The IA train derailing is Service 10 which performs a shunting & coupling action in High Wycombe North Yard sidings 6 and 4 Coal. There appears to be a destination instruction missing here after the coupling instruction in the timetable, so I added a destination instruction (hand with pointing finger symbol) for service 10 to move to 'High Wycombe North Yard' et voilà the derailment did not happen anymore when I re-ran the scenario. I am not at all an expert with timetables but I found it strange that there was no destination instruction for this service after the coupling instruction. Anyway it worked. In addition I found in the timetable view, when clicking on the errors symbol (little traffic sign with exclamation mark at the bottom), that 2 wagons had a duplicate number 141321. Duplicate numbers are possible causes of problems as well I heard, so I changed one of the wagon numbers (the one in Wheatley Siding 2 coal, I believe) to 141325 and the error disappeared. Last but not least, on my installation, the tenders of the Thompson B1 hauled Service 8 (the one overtaking you in Princes Risborough) and Service 1 were running with invisible tenders. I found out that the tenders used on these trains were missing the B1_Tender.GeoPcDx files, so after copy/pasting the one from the default B1 tender these trains now run with visible tenders.dledge wrote:I got the AI train derailment (I think for Service 10) just after West Wycombe.Ajay1 wrote: Continuing on, and when approaching West Wycombe up platform the scenario stops abruptly with the message of an AI train derailment at Long -------- Lat ------------ ( sorry wasn't quick enough to catch it ) . Anyone completed this yet?
Antony
Dave
Anyway, apparently a few errors slipped into this scenario. I am not sure which one, or perhaps a combination of errors, causes the derailment and perhaps also the invisible service 8. After the changes I made the approaching service 8 was now visible all the time when I re-ran the scenario.
Cheers
Jos