woodhead 76 error

[david1]

Just made a scenario for the Woodhead BR version using the default 76, on starting the scenario I get the messages to say the traction motors have burnt out - the loco is a failure, resistance bank a and also bank b have burnt out - the loco is a failure, I have not even set up the locomotive so I have not caused any damage, after a couple of minutes TS then crashes.

Has anyone else had this?

[gptech]

I'm not a producer of scenarios so obviously I haven't seen the error, but what happens if you delete the offending item and stick another on the track?---just leave it as a static consist, no driver assigned and test. If that results in a stable game/scenario give it a driver and test again. If that works just shrug your shoulders and say "one of those things...." but if it again causes a crash give it a Final Destination and re-test, the idea being to determine if there's an issue with consists that have drivers but no instructions.

[david1]

Will give that a try, thanks

[bvetmd]

Are you starting the scenario directly from the editor ?

If so, exit the scenario and restart it from the game 'drive' menu and all should be fine.

[david1]

Also get error messages when starting from drive menu, but the error messages are bogus as the train runs, the error messages are also present in the scenario editor and remain on the screen blocked the righthand flyout to access asset list, after playing the scenario and testing the crash seems to be caused by the rolling stock used worked fine until I tried loading passengers which seems odd, I had been modifying the folder to add AP sounds to them, I have not done that yet, but also noticed the stock numbers were wrong so that is the only thing that has been changed maybe I have a corrupt DCSV file, will investigate after completing the scenario.

[bvetmd]

Also get error messages when starting from drive menu, but the error messages are bogus as the train runs, the error messages are also present in the scenario editor and remain on the screen blocked the righthand flyout to access asset list, after playing the scenario and testing the crash seems to be caused by the rolling stock used worked fine until I tried loading passengers which seems odd, I had been modifying the folder to add AP sounds to them, I have not done that yet, but also noticed the stock numbers were wrong so that is the only thing that has been changed maybe I have a corrupt DCSV file, will investigate after completing the scenario.

I know making scenarios with the blue 76s can be a bit awkward as I've just done a few new ones for myself recently but havnt had the problem you are describing to be honest. There is an issue however when loading the scenario editor with the 76s as you describe, where the loco status flyout messages block the right hand pane preventing you access to it. I find that by clicking the bottom right 'drive' arrow icon in the editor to load the scenario and once it loads exit straight back into the editor with CTRL + E, then by clicking the scenario tool icon on the the left hand pane when the scenario reloads into the editor the loco status messages dont re-appear so you can then access the tools on the right hand flyout panes.

When you start playing any scenario with the blue 76s you will always get messages on the right hand side letting you know the loco formation, panto effects and whatever else the current state of play with the loco is as set by the scenario maker, however these shouldn't show fault conditions at the start. As I said, if you try driving a scenario directly from the editor then you will have problems, not just the loco showing the fault messages but other issues also, namely signalling. There were some posts here regarding this not long after the BR blue Woodhead was released if I remember correctly.

[gptech]

the crash seems to be caused by the rolling stock used worked fine until I tried loading passengers which seems odd,

Which coaches?

maybe I have a corrupt DCSV file,

A corrupt, unreadable, file would cause an immediate crash, but as you have numbers it's probably more a case of an incorrect edit. Dead easy to check if the stock comes in a .ap archive, just temporarily remove the extracted folder and the game will use the 'as supplied' version from the archive.

[david1]

Which coaches?

The Stock was from who we are not allow to discuss, not used the stock for a long time, thinking there might be a problem with either 64bit or the new AP sky effects on the stock I tried the scenario in TS2018 with default sky, but same errors, either stock has become corrupt, no longer likes upgraded TS which would be odd as each upgrade the new content and assets get deleted and the previous version folders are copied in.

A corrupt, unreadable, file would cause an immediate crash, but as you have numbers it's probably more a case of an incorrect edit.

That's what I would have thought, I have edited bin and DCSV files before, if I make a mistake it either crashed the sim on startup or when trying to use the affect stock, using DT stock and it works fine, will try the stock on a different route to see what happens.