Does anyone know anything more about this error message? I've had it twice now, once when driving Victory Works' Austerity on the Woodhead Line and another on the Penn Steam route. I didn't have any issues like this before the update.
Same here. But mine was with the 800 on the Huddersfield line. Exact same place twice. Exception Code: 0xE06D7363 Exception Info: UNKNOWN Fatal error in mode DRIVE during update within SCRIPT_MANAGER.
Contact Victory Works - it might be a Script Error similar to what has affected other Third Party Locos
I very much doubt that, because as I said I got the same error on Penn Steam and the Penn Steam locos apparently use no scripting. The errors also came a fair bit into the scenario, and not when I was doing anything I hadn't done in the scenario before without crashes.
I have the original BL&E version and ran 2 scenarios without any issues. It may be related to your system and may not affect all users. Have you tried a verify?
I don't think that necessarily proves anything, because I have also ran Penn Steam scenarios that didn't have any issues. It seems like it could be a bug that strikes randomly.
I am noticing a lot of texture flickering in the 800 cab, lights keep going off and then on again briefly before this incident, it may well only be a coincidence though?
error OxE06D7363 UNKNOWN - Fatal error in mode DRIVE during update within SCRIPT_MANAGER. - Additional information after update. I'm bit late to the party but I've been getting the same error on the Huddersfield line and it occurs in all northbound scenarios at the same place, that is at the 85mph sign just north of Marsden reported to DTG recently and told that it was in hand and the call closed. Also get the same error on a scenario on the Nuremberg and Regensberg line specifically [185] 6. Follow the Leader initially reported to DTG back in Dec 2020 although that time I was told that I needed to upgrade my PC.
It is still not fixed for me on the Leeds Huddersfield Line (OOM at Slaithwaite) - makes the route unusable and a complete waste of money. I raised a ticket too, and was told it was probably my end (despite everything else in TSC working fine). Quick scan of forums and reviews can see loads of people are experiencing the same issue but DTG have chosen to ignore, fix, or provide any fix updates. Was hoping one of the recent core or route updates may fix the issue, but to no avail so far. Such a shame as its one of my favorites from TSW days and makes me relucant too touch any more DLC made by DTG.
If it was a problem with the route then everyone else would have the same problem. Does the OOM happen in every scenario and with every type of traction Or is is just One Scenario that causes the problem?
It's not reproducible, so there's something else going on on your system. Could be rogue repaints or other modifications. The route as it is sold is working, else it would crash reproducibly for everyone. I have played all the scenarios without any problems. Start RailWorks\LogMate.exe before running a scenario and then post the logfile (found in the root RailWorks folder) here.
There seem to be two problems, one with a route, one with a scenario. I'm not versed in TSC lingo to know what ribbons are related to curves, sounds like some cryptic teen talk to me about girls. My best guess is Spikee checked, raised both eyebrows, and forgot to comment not having a clue. Did you try uninstalling and then reinstalling the route (using Steam DLC manager), to refresh its files? Do you use any external tools to tamper content? Such as extract files? It could explain the message complaining about mismatched files (mixing older and newer version). I generally doubt that the route would be entirely undriveable in a given direction, would have a lot of complaints. So it's 99% that something is messed up on your system. Extreme but standard troubleshooting advice: 1., Close (exit) Steam 2., Rename your RailWorks folder to RailWorksBackup (or anything) 3., Start Steam 4., Before installing TSC, unclick every DLC except Huddersfield (and maybe EU assets). 5., Install TSC. 6., Play your scenario. 7., If successful, you can compare files and folders by content.
Error 0xe06d7363 is usually a Visual C++ exception code, ie a system application error. Could be due to a number of issues. and maybe due to some issue(s) in your system files, Hence, it might be worth looking at "View Reliability History" or "Event Viewer" for any error codes, and probably run sfc/scannow via cmd.exe as administrator (until any errors are fixed). (Google).
to me those Exception Code: 0xE06D7363 Fatal error in mode DRIVE during update within SCRIPT_MANAGER happened too on huddersfield on scenario nr 1 with the class 158 resume from a save worked so i was able to finish the scenario altough the resume was without RW enhancer 2 enabled so maybe it relates to rw enhancer 2
Perhaps the thread below can be of assistance . . . https://forums.dovetailgames.com/threads/all-119-command-line-launch-options-which-ones-are-current-obsolete-incorrect-or-missing.74961/
