Atomic Systems

Hello all,

Before you ask, yes I have a folder Scenery_bak as I made the scenario with scenery off. The issue is, I saved the scenario and it decided to crash with a SBHH. I put the finishing touches in, made the player path and then when saving it went bang.

Now when I either try to drive it or edit that scenario (the others are fine) with or without scenery, it won't let me in, just coming up with the SBHH message.

I spent all day making it, and as it was a peak hour realistic run as I always do, and from London to Brighton, there was a lot of AI and a great amount of detail to make it realistic. I fear all this hard work has just crash landed

Is there absolutely any way I may be able to rescue some or part of it?? I haven't backed up as I haven't done such since (I don't have much room, before I reformatted last week, my HDD was almost full with backed up this, backed up that, I just don't have space to do such, so I didn't. To be honest I've done a lot of scenarios and not had to back up the WIP.

Hopefully I don't have to start it again, or need to back up after every AI train I insert.

Does anyone have any ideas? If you do you'd be my hero!


Cheers,

James.

Your only hope is to open the Scenario.bin and ScenarioProperties.xml files with RW Tools (or similar) and see if there's anything obviously amiss, and attempt to edit if possible.

You could try removing the Scenario properties.xml.MD5 file, then using RW_Tools just change the weather, this then creates a new Scenario properties.xml.
Has worked for me in the past. But wouldn't it be nice if a SBHH actually told you what went wrong...

Thanks for the replies guys

I'll try that when I'm back from the weekend, I also forgot to add my consist is a 455 + 2 x 456, the latter being an AI train. I didn't think of it at the time, however could that also be an issue for a player train? The lead train with the driver on is the Class 455 though, and there is no reversals, so you wouldn't need to use the 456 either.

SBHH's in the editor for London-Brighton have been around since it's release. It has nothing to do with scenarios or computer specs, it is a general route problem which has not been permanently solved. There is a temporary work around for editing scenarios but you should only do that if you're comfortable with fiddling with files.

Would be so nice if SBHHs did give some idea of what went wrong, or even better if error handling was improved to deal with more problems without crashing. I imagine most would be fairly easy fixes. I call them "Derpy errors", or that Railworks has Derped again, http://www.youtube.com/watch?v=LOljwJCujLk (character is known as Derpy).

tubemad wrote:I haven't backed up as I haven't done such since (I don't have much room, before I reformatted last week, my HDD was almost full with backed up this, backed up that, I just don't have space to do such, so I didn't. To be honest I've done a lot of scenarios and not had to back up the WIP.

Easy to say so afterwards, I know, but you don't have to keep backing up the whole of TS or even the route whilst developing a scenario. I usually clone the scenario I'm working on at each key stage, at least you can drop back to the previous one if something like this lets you down. If you number-suffix them (or letter them, as I do) they will appear together in a sensible order on the screen so you know the last-listed is the latest version. Doing it that way won't gobble noticeable disc space.

Hope you manage to recover it, anyway - I know how much work goes into putting full timetables in on the Brighton line from my own efforts.

John

PS - Highly recommend a portable disc for backups, good for storing off site against theft, flood, damage etc too.

I don't know if it's related.

Because it's a separate route the Kuji folder is not normally ticked.
Had problems putting DT Mk1's in a L2B scenario which was ok until I tried to couple to them and SBHH.

If you have not already ticked the kuju folder it might be worth it as so much freeware refers to items in the folder.

Peter

749006 wrote:I don't know if it's related.

Because it's a separate route the Kuji folder is not normally ticked.
Had problems putting DT Mk1's in a L2B scenario which was ok until I tried to couple to them and SBHH.

If you have not already ticked the kuju folder it might be worth it as so much freeware refers to items in the folder.

Peter

Myself and many others have ticked the Kuji folder already. The SBHH error still remains. As I said, the error lies within the route itself.

ive been meassaging rsc about this for over 6 months and they cant replcate the problems people are having ive been told it my graphics card i jus laughed as i have a g-force, been looking in steam forums and its something to do with the scenery file which i have told rsc but still no help from them now looking at taking the route out

Hi Simon, Which gforce card & 32bit or 64 bit operating system? More onboard graphics memory with 32bit means less for program use.

believe its a 64bit, runs other routes no problem jus l2b im having trouble with keep getting something bad has happened

connorurry wrote:
Myself and many others have ticked the Kuji folder already. The SBHH error still remains. As I said, the error lies within the route itself.

Sorry tubemad did not realise you had changed you log on

So can you create a scenario with default stock or does it stop you doing that ?

Hi Simon, If you are near the London end and your computer isn't beefy enough to load everything that you have requested, it will SBHH. Try turning settings right down & try again. You omitted to mention which graphics card you have and also to confirm which operating system you are using. The rest of your system specs would be quite handy too, it will give us a clue as to whether it is a hardware weakness or problem with your installation of the route. My system which has a GT550Ti gets down to 16 FPS around Clapham junction with most settings on high so it is quite demanding!

Thanks for the help guys but unfortunately editing the weather by deleting the .XML and having it replaced through RW Tools, still produces a SBHH.

Looks like it's completely stuffed, so I'll delete it and start afresh. What I'll probably do is save, backup and repeat the process every so often.

Thanks once again for the help and suggestions though