Railworks America

After recovering from "stuffed scenario" syndrome (take 2 re-installs and don't call me again, ever), my TS2013 installation zipped along quite well for a while; even long editing sessions did not send it down the SBHH chute. Then, sometime between Christmas and New Year, it became hypersensitive again. Small things, like passing between editing a scenario and test-driving it more than twice during the same running session, sent it into an SBHH tailspin. Even running more than three scenarios without restarting the program could bring on an SBHH migraine. Sometimes I saved the crash report files, other times not; every two or three SBHH's I bored my way through a cache verification, which always found at least 50 defective files. Yesterday, after purchasing some bit of DLC or other, T(es)S(ty)2013 refused to start; without even passing through an SBHH, a cache verification reported that 98 files had failed to register.

Today, I returned to work on a complex switching scenario I've been creating off and on for several months. I started by editing one instruction and placing a couple of cable reels where the player had to stop before reversing for a pick-up. Then I saved, clicked the big orange arrowhead, and started a test run. About 10 minutes in to the scenario, with everything going well, S-B-H-H.

So, what I'd like to know is whether I'm alone in this or whether TS2013 has seemed hypersensitive to others recently, as well. No purposeless anti-RSC venting, please, just calm, reasoned comments. Thanks.

CALM??? REASONED COMMENTS?? ARE YOU NUTS????????

I have had some issues but everyone one of them after spending a bunch of time has always so far had a root cause. I am still formulating a sort of personal "go back" backup so when this happens I can hopefully replace some section of this beautiful monster and get it to behave again.

OTHER THAN SOME dern PROBLEM WITH ONE SCENARIO ON THE Bay of Quinte which must be caused by SOME BUG INSTALLED BY RSC since they didn't invent this route and MUST BE SABOTAGING IT"S USE SOMEHOW WITH THEIR CONSTANT STEAM NINJA UPDATES!!!!!!!!

I get very few SBHH, and always it comes from a change I had just made, so I can easily trace the problem.

I'm beginning to doubt the report displayed by the local cache verify function in Steam. There's very little plausible reason for a file to become corrupted on your PC if you don't open it for writing. I can see why your scenario file could become corrupted, but to be suddenly missing 98 files makes no sense, unless you just installed some DLC.

I suspect that "Failed to verify" should be taken literally, as in "the verification of this file failed", and not "this file is corrupted".
One possible cause is file corruption (or file missing), but the most probable cause is just that the verification timed out, or some network error happened.

I agree with that.

I'm not just making this up, as you guys seem to be suggesting.

After this morning's SBHH, I launched Steam and saw that something was downloading for TS2013. After the download had completed, I rebooted again.

Then, I tried launching TS2013 again and this is what appeared on my desktop:



Evidently, whatever downloaded through Steam brought back this **&&%%$$## error again. Surely, I'm not the only one seeing this?

I got it SBHH just now and it fixed itself after a second try.

Old Prof wrote:I'm not just making this up, as you guys seem to be suggesting.

No no no. I'm very litteral. There is no hidden meaning in my posts.
But sorry to have started on a tangent. I tend to do that.

Old Prof wrote:After this morning's SBHH, I launched Steam and saw that something was downloading for TS2013. After the download had completed, I rebooted again. Evidently, whatever downloaded through Steam brought back this **&&%%$$## error again. Surely, I'm not the only one seeing this?

According to people on UKTrainsim, there seems to have been problems for some people with that ninja update.
Steam has been very slow, so it's possible the update was not completed successfully.

I'm happy to report that I'm no longer getting the dreaded "Line 113" error. Just in case it proves useful to someone else, here is the process I followed after the error appeared and I recovered my usual composure:

1) I opened Microsoft's System Restore utility and discovered that a restore point had been created just a day or so before the "Line 113" error reappeared, due to installation of a Windows update of some kind. So, I restored my computer to that restore point. Afterward, TS2013 launched again, but the Munich-Augsburg route did not report for duty: not a trace of it. I closed TS2013 and looked for the route again using RW_Tools: not there, either. For the record, I had been editing a scenario for this route the last time that TS2013 SBHHed before the "Line 113" error occurred.

2) Not knowing what else to try and figuring that I could always return to that restore point again and just kiss all my editing work on that scenario goodbye, I initiated a cache verify, which took several hours to complete (actually, I went to bed while it was still running). Ultimately, the verify process reported that 11,054 files had failed to validate (please note: no mention of corruption, just failure to validate, whatever that may actually mean).

3) This morning, TS2013 launched without problems, including the Munich-Augsburg route and my scenario in development (although I haven't had the gumption to open it for editing again yet, nor have I tried running it. More about that in another post soon.

I plan to create another restore point right away.

{ Sidebar: I sent an error message to RSC support, including a screenshot of the "Line 113" error box. In reply, they asked me to tell them in what route or scenario, or at what location the error had occurred. Quite obviously, they had not read my initial message, which clearly stated that TS2013 would not launch at all! This sort of negligence is hardly unique to RSC, but it is perpetually annoying to me and, I imagine, all computer users. }

See this thread for an example of a backup script for a scenario.
I use it every 20 minutes or so.