Back to back scenarios SBHH

[styckx]

I've been fighting this for ages, even reported it w/ a dump file which went absolutely no where. So.. I'm polling the millions (Annnd Millions) of the Railworks fans on here to see if I'm the only dummy in this boat.

It seems this game (for me) isn't very found of running a scenario right after you run a scenario. Whether it's 5 minutes or 50 minutes.

Common scenario played out.

1. Play a scenario
2. Get bored/finish it exit out
3. Pick another route/another scenario - Click play
4. SBHH while loading
5. Return to game, choose same scenario and it loads.

Rinse repeat.

I'd say I have a 60-65% chance of getting a SBHH while loading a scenario if I have played one previously without shutting down Railwork first.

[phat2003uk]

I've also had similar experiences Bill. As a rule, I always restart the sim before starting a scenario or testing some sounds. It's funny how one gets used to working around the many quirks of the sim!

[chrisreb]

Same for me 9 times out of 10

[nobkins]

Depends on the route for me. Working on the WCML-N scenario pack I have noticed this a little more. However, one of the tests I do is a "does it load" test.

I loaded up 20+ scenarios when initially checking the pack one after the other with no issues. Didn't play them obviously. Maybe that points to a problem being caused by running a route. Perhaps related to loading up lots of tiles as you drive making it more likely to SBHH when you try a 2nd scenario.

[bdy26]

I'd say about 70% chance for me too.

B

[AndyM77]

Well, I don't have much love for the simulator at the moment and haven't really touched it much..

But yes, running scenarios back to back either results in "Jelly Cabs" / Strange AI behaviour / the odd SBHH . It doesn't always happen though, as I'll only run a back to back scenario if they are short (i.e sub 30 minutes), so either the length of the scenario could be a contributing factor or a classic case of the game not releasing memory and therefore it's either overloading the users system by running it out of memory OR it's not flushing out previous code from the scenario it's just run and as a result receives something that it wasn't expecting.

[msdejesus]

Just in case it is of any help for anybody, here's my two-pence

I have found that, when testing scenarios - especially WCML-N - it is useful to load just a custom, "1-route-only" Content folder.

I do this by renaming the complete Content folder something like "Content_Full", to avoid confusion.

Of course, this is only necessary for repetitive loading - testing - reloading processes.

I also agree it is advisable to exit the game and reload after a complex scenario / route has been used.


Regards

Manuel

[styckx]

Woohoo.. Thanks for the replies.. Glad I'm not the only one suffering from this `annoyance.'.

And no one pointed out my awful use of The Rocks catch phrase? Shame!

[FoggyMorning]

It tends to happen to me only when running a second scenario on a different route to the first - e.g. running two consecutive scenarios on Newcastle - York is fine, but following a Y-N scenario with an Oxford to Paddington scenario will result in a failure to load.

And that's the bottom line.

[smarty2]

Same here Bill, especially after coming out of the scenario editor to play the erm scenario, and DING! Get it back to back too fella.

[styckx]

And that's the bottom line.

[salopiangrowler]

not had a problem since dropping the Texture Filtering to Bilinear and the FSAA to either 0 or 1