Beyond frustrating.

[GaryL]

Problems, problems, headaches, headaches, SBHH's, SBHH's.

I was in the Scenario Editor for a good six hours this evening for the Edinburgh & Glasgow route creating a scenario based on the real timetable (as I always do). Once I finally got everything the way I wanted, it was time to hit 'save' for the last time, exit and play the thing. Not one SBHH was had within these 6 hours of being in the editor. Smooth as silk.

So, it's now that exciting moment when you get a chance to 'play' it after all that graft in the editor. Low and behold, the loading screen comes up, it stutters and splutters then plunges back to desktop with a dreaded SBHH to greet me. Great.

I'm at a loss. I've tried everything I can think of.....reduced the Kuju folder size vastly, removed the blueprints in the Scenario Properties XML file, deleted the .MD5 extension files, cleared cache, reduced graphics to lowest settings from my highest settings (I have a top end gaming machine and it eats TS2013 no problem), restarted PC etc etc. I cannot access it via the scenario editor at all either. Talk about being deflated.

I have 24 AI services in this scenario. Could this be causing a problem? Is there a limit to the amount of AI you can have in one scenario? Plus, the only trains used are 170, 156, 158, a 37, a 66, HAA's and some tank wagons. And it's a fairly simple scenario. There's no complex moves for the dispatcher to become flustered.

All other scenarios work no problem on this route, even with my Kuju folder at it's max of 10.9GB. It's just this scenario throwing a wobbler for some very sad reason. It's so frustrating considering I had no problems in the editor for hours and everything was fine. Not one error.

Have I missed something totally obvious?

Can anyone help or come up with some suggestions as to what the cause could be?

I'm off to bed now. Hopefully I'll wake up in a few hours and someone will have a cure for my 6 hours of work in the editor.

Thanks for anyone who can help.

[Acorncomputer]

You have not mentioned checking for zero btye folders. This is a long shot but use RW Tools to find and destroy any folders in your Railworks folder that have nothing in them. (There are a few sound files with zero bytes but these would not be the problem. You can delete these as well as any others as these legitimate ones will be created again).

-

[smarty2]

I would suggest running your scenario through RWTools and see if any errors in stock whatever come up.
Just out of interest did you re-start TS2013 before running your scenario or did you try to run it straight from the editor? I have found that complex scenario's will not run from the editor but give an SBHH, resources I think.

[3DTrains]

Check the scenario folder for InitialSave.bin and InitialSave.MD5 - if present delete. I'm not sure why these are created, but the files always seem to cause issues with loading routes and/or scenarios.

[smarty2]

Check the scenario folder for InitialSave.bin and InitialSave.MD5 - if present delete. I'm not sure why these are created, but the files always seem to cause issues with loading routes and/or scenarios.

Good to know, cheers Marc.

[malkymackay]

The InitialSave.bin does serve a purpose. A quick look reveals it saves the states of junctions at least.

[phat2003uk]

Have you made sure that the Kuju>RailSimulator box is ticked in case any stock requires couplings as a dependency?

[3DTrains]

The InitialSave.bin does serve a purpose. A quick look reveals it saves the states of junctions at least.

That may be true, but I find that when an error occurs that removing these files appears to fix things, and I've yet to have to go back and recheck the files or have further errors, even after resetting switches. Perhaps things get wonky on initial creation?

[GaryL]

Have you made sure that the Kuju>RailSimulator box is ticked in case any stock requires couplings as a dependency?

Hi guys,

Apologies for the late reply. After much head scratching etc it turns out that the above was what was causing the SBHH. I had been using malkymackay's bolsters and without the Kuju>RailSimulator box ticked, it was throwing me the SBHH. With it ticked, absolutely no problem whatsoever. In order for me to get back into my scenario in the editor, I had to removed the malkymackay folder from the Assets folder, saved the scenario (minus the bolsters), put the malkymackay folder back into the Assets folder and fired up the scenario without a hitch this time. Tried placing them again without the Kuju>RS box ticked, bang! SBHH. Then, tried placing them with Kuju>RS ticked and no problem.

Thanks for all the replies guys.

[malkymackay]

Have you made sure that the Kuju>RailSimulator box is ticked in case any stock requires couplings as a dependency?

Hi guys,

Apologies for the late reply. After much head scratching etc it turns out that the above was what was causing the SBHH. I had been using malkymackay's bolsters and without the Kuju>RailSimulator box ticked, it was throwing me the SBHH. With it ticked, absolutely no problem whatsoever. In order for me to get back into my scenario in the editor, I had to removed the malkymackay folder from the Assets folder, saved the scenario (minus the bolsters), put the malkymackay folder back into the Assets folder and fired up the scenario without a hitch this time. Tried placing them again without the Kuju>RS box ticked, bang! SBHH. Then, tried placing them with Kuju>RS ticked and no problem.

Thanks for all the replies guys.

And I mention in the readme for all my wagons that the Kuju/Railsimulator folder needs to be ticked when adding them to scenarios

[phat2003uk]

Great to hear Gary. I know how frustrating it can be when you think 6 hours of work may have gone to waste!

[GaryL]

Have you made sure that the Kuju>RailSimulator box is ticked in case any stock requires couplings as a dependency?

And I mention in the readme for all my wagons that the Kuju/Railsimulator folder needs to be ticked when adding them to scenarios

It was a quite a while ago I read that readme