Railworks America

Hi Guys,

Since I have bought this route, I have not been able to get it to load. It starts the load up screen...then the music stutters, and I get a blue screen. All it says is the "Something Bad has happened" message, nothing else. It locks up my computer, and I have to do a restart. All of my other routes work, just this one gives me problems. I have done all the usual stuff....clear cache, check and verify file integrity...etc. Any Ideas?

Thanks,

Galen

I would delete it from the asset folder and then verify local files and re-D?L. It sounds to me like you got a bad download if everything else is OK. Also delete it from the content file. It is 00000027-whatever.

Also, verifying local files rarely works the first time.
You have to do it again until it says all local files verified OK.

Well.... I did this, and still no route.... I look in the folder though, and unlike any of the other routes, it only has 2 files.. Blueprints.pak, ans PacificSurfLiner.ap... No other files... Any Ideas? Thanks!

Chacal wrote:Also, verifying local files rarely works the first time.
You have to do it again until it says all local files verified OK.

Statements about the need to verify the cache multiple times keep popping up here, so I've done that occasionally. In my experience, a second verification has never turned up any files that need to be reloaded, so it seems to me that additional sequential verifications are a waste of time. It doesn't seem possible that my case would be unique in this regard.

Well... I used 7 zip, and unzipped the ".ap" file. Now I have the route.... With the ES44, It starts out "jerky"...then once in the cab, it dumps....same kind of error. I have never had this problem with a route, and it seems, most others did not with the download.... Did everyone have to "unzip" this route, and am I missing something? Thanks!

I haven't verified the cache in a year, probably, but I used to have to do it with some frequency, when buying new DLC, and when I did, subsequent verify operations almost always turned up more files needed. Once I had to do it four times before it said nothing needed downloading. Perhaps that has improved lately.

Old Prof wrote:Statements about the need to verify the cache multiple times keep popping up here, so I've done that occasionally. In my experience, a second verification has never turned up any files that need to be reloaded, so it seems to me that additional sequential verifications are a waste of time. It doesn't seem possible that my case would be unique in this regard.

My experience is the contrary: cache verify never succeeded on the first try.

I believe it is normal that our results differ because of the nature of the beast. The files are verified by comparing local information (often a hash of each file) to the corresponding information from a server, over the internet. If the request times out, or if there is any kind of network problem, some files will "fail to verify", even if they are not actually corrupted.

The internet being a fickle network, some will have more luck than others, depending on their connection to the Steam server.

Chacal wrote:I believe it is normal that our results differ because of the nature of the beast. The files are verified by comparing local information (often a hash of each file) to the corresponding information from a server, over the internet. If the request times out, or if there is any kind of network problem, some files will "fail to verify", even if they are not actually corrupted.

The internet being a fickle network, some will have more luck than others, depending on their connection to the Steam server.

Now, that's an interesting observation. If I've understood you correctly, you're saying that the fault that may require multiple verifications lies with a user's internet provider and connection, rather than with Steam.

Through the years I have watched the D/L some of the time and there is a dramatic difference in D/L speed by the time of day and which server I'm using so I say yes, there are many things affecting this besides Steam.

Old Prof wrote:Now, that's an interesting observation. If I've understood you correctly, you're saying that the fault that may require multiple verifications lies with a user's internet provider and connection, rather than with Steam.

May lie.
The verification may fail for any of multiple problems, including connection and Steam server.