"Updating Scenario Database" takes forever !

[gptech]

but sadly I feel that all of the solutions offered so far, are beyond both of our skills to apply.

Not at all....
You can both ask and answer questions; you can both copy and paste, rename, move, delete folders and files; all you're lacking to make a start is confidence. Don't worry about any complicated looking stuff that's been suggested, just deal with things one at a time, step by step.

To go over what we know as being definite at this point:

the 64bit version of the game slows down when dealing with the scenario cache.

That's it...anything dealing with a fix for that is guesswork, which is the best any of us can do without more information.

So.… post an accurate time scale for the *pause*
post the location of the game


With those 2 wee snippets of information we'll be able to focus on the likely cause(s), at which point we'll ask more easy questions and possibly even suggest some easy steps to try.

[petermargetts]

Thank you 21C1645FighterCommand for your posting of the 28th October.As suggested I ran Namemyroute.exe and found 205 missing or failed scenario properties files.The majority of these turned out be be empty folders which I deleted and the remainder dealt with as previously mentioned. Although before with 210 routes loaded it usually took just over the minute to update scenario database this has now reduced by half. I have diarised to check on the routes on a regular basis to keep the errors downs.
PeterM

[shinymac]

Hi Gary

Thanks for the reply.

My friend has his installation in D/Games/Steam/Steamapps etc etc.
The time delay was around 3-4 mins but cant at present remember if this was from the words "loading scenario database" or "updating scenario database" appearing. Is it helpful to know which ?

Thanks
Derek

[runeborg]

My installation takes a consistent 6 minutes 35 seconds from pressing the Play button with Steam already running to the first menus appearing, most of which is updating the scenario data base. The timing is very close to the same in 32 bit and 64 bit.

[shinymac]

Hmmm...so theres at least TWO of us that have some part of the load up process taking MUCH longer now, than before the 64 bit version appeared !!!

Interesting.

[gptech]

so theres at least TWO of us that have some part of the load up process taking MUCH longer now, than before the 64 bit version appeared !!!

not really Derek...

The timing is very close to the same in 32 bit and 64 bit.

[brysonman46]

Derek - have you considered reducing the number of routes in your active Railworks\Contents\Routes folder? I have all my routes in a separate folder on another drive, and only about 6/7 in the active one. It takes about 20/25s to load up/build the scenario database. If I wish another route to run, it takes seconds to drag and drop it from the store to the active (and then delete any in the active that you have finished with). You can also remove any scenarios in the active folder that you have finished with, further reducing the load on the scenario build. I have some routes with 50 or more scenarios - when I put them in the active, I will remove a large number of them (after all, you can only run a couple before you have to restart)

Nick

[shinymac]

Hi Nick

Just a reminder...its my FRIEND that has the loading up probs not me.

As for ME...well before the upgrade to 64 bit I had done like you say and had moved some unused routes out to an external drive which reduced the time taken to do a full back up of the railworks folder considerably !

Wont be seeing my friend until early next week to see how HE is getting on (or not) but will update you all then,

Thanks as always

Derek

[shinymac]

Hi Gary, Peter etc

Well, after carrying out several procedures, my friend was nowhere near solving his long load time for the scenario database.

But as of today it LOOKS as if he has solved the problem ! (lets hope so !)....

He had removed all his workshop scenarios from STEAM and deleted all trace of them, but that didnt help. He then cleared the cache in both 32 and 64 bit and that didnt help either. What he did next seems to have cured things...

He did a right click on the TS64 Bit icon on his desktop and ran the "compatibility troubleshooter", and selected the option to "let STEAM decide how it runs" (or whatever is says similar to that ). And HEY PRESTO ! His scenario database for TS64 loads up in approx 20 seconds...instead of 3 and a half minutes ! He isnt really sure exactly which procedure sorted things out, but it was in the options for "compatibility" that did the trick. He is now one happy guy again !

Thanks to all those that offered help, and to those of you who still have similar issues, perhaps you should try the same ?

Thanks as always

Derek

[gptech]

selected the option to "let STEAM decide how it runs" (or whatever is says similar to that ).

You mean "Use recommended settings"? Nothing in there about letting Steam do anything Derek, it's all how Windows deals with things---in other words using that option has suggested that the issues had stemmed from a misconfiguration of the user's PC, by presumably the user. There can be no simple fix for unique errors (despite the messages seen on screen being the same as anyone else's) that are 'self inflicted', that would be impossible.

[shinymac]

Gary

My friend Jon has no knowledge of "mis-configuring" ANYTHING !

To be fair, he wouldnt touch anything like that as he wouldnt understand it, so always shys away from touching things like that.

Derek

[gptech]

My friend Jon has no knowledge of "mis-configuring" ANYTHING !

Unfortunately Derek, that's often why it happens--folk do things completely unaware of any consequences. It doesn't have to be an intentional change introduced when installing anything (for example), any wee glitch along the way--crashes, freezes--can, and will, affect more than we think. Another reason why fixing these kinds of errors is a long drawn out process, and often resolved more by luck (desperation?) than anything else---TS and Steam both work well without any configuration changes at the level he's had success with being needed, so wouldn't come to mind straight away as a possible cure for any ills.