Atomic Systems

connorurry wrote:Does anybody know if the SBHH in the editor has been solved or not?

This is probably caused by your computer running out of resources rather than any specific problem with the route itself. The best thing to do is make sure you have no unnecessary processes running and save often!

Never really established if this error effected everyone or not. I am guessing not and therefore will probably not be fixed. I have a high spec gaming machine that had never had a problem until I tried writing scenarios on this route. Running it is fine. I got round the problem by following the advice elsewhere in this thread and created a copy of the route which I stripped right down and then use that for writing and export them over to the normal route to run. Bit of a pain but not too bad and better than SBHH. I have 12 GB RAM so never really understoiod why I suffered so badly and only with this route.

Will be interesting to see if TS2013 solves this problem. I've found frame rates in L-B are far better than with TS2012, and the stuttering seems less too (although still there). That said some AI train and dispatcher problems I was getting on a scenario I'm creating are still happening, suggesting that was more than just TS getting overloaded.

Um, I seem to have the no signals problem with the TS2013 London to Brighton, and I can't solve it. I've verified game cache quite a few times, and cleared the blueprint cache too, but nothing's worked so far. Anyone have any ideas what I can do to make the signals appear?

Hmm TS2013 has brought back the "every Electrostar is a 377/2" back again, at least for quick drive... :/

MallardFan wrote:Hmm TS2013 has brought back the "every Electrostar is a 377/2" back again, at least for quick drive... :/

Quick Drive uses the default numbers of the train which happen to be 3772** it seems!

Ahh... handy...

Was just trying some scenario editing, loving how fast and smooth it all was and thinking that perhaps the SBHH error was gone, then all of a sudden *poof* "Something bad has happened". So no, not fixed. Might be a little better, but it's still there. Makes me think it's more than a resource issue though as TS2013 is running much better when 2012 did.

I'm probably just slow and not played this enough, but anyone notice The Shard's been added to the london sky line? be it a bit too close, but still a nice touch!

y2flexy wrote:I'm probably just slow and not played this enough, but anyone notice The Shard's been added to the london sky line? be it a bit too close, but still a nice touch!

You've been slow and not played it enough
But yes, it's always been there.

never noticed it! though I think it might be partly due to the update having a far better graphics performance on me so I increased the view distance haha

Can I ask if the performance of this route has improved since TS2013 release.

I found it to be a real FPS killer, along with WCMLN under 2012, but WCMLN runs much better under 2013 than it did under 2012. Is it the same for this route also ?

it runs a hell of a lot better for me (non-tsx mode mind..) but I still do get a bit of stutter around the London area, certainly isn't unplayable to me anymore though.

Yes, I'm getting much better performance all round with 2013. Love the London to Brighton route - it would be good if the Woking to Portsmouth could be extended to Waterloo to complement LB.

DCB

Thanks guys.

Just played a PDL scenario and the performance increase on that route, was very noticable as well.