Railworks America

I was beginning to see some strange things happen, such as a player train that, moving through areas with automatic switches only, began moving in peculiar directions that diverged from its programed path. Since the last time I verified the cache, no SBHH errors had occurred, but I asked for another verification anyway. 144 files "failed to verify". Why? Like doctors who do not explain our illnesses to us, RSC does not offer explanations--perhaps because they themselves (both the doctors and RSC, that is) simply do not know. 144 files that were recognized as unhealthy, maimed, abnormal in some way due to normal, SBHH-free editing and play.



Does anyone?

I suspect some files just litterally failed to verify, meaning only that the verification failed. This may not mean that the file is corrupted. It could be a network problem of a Steam server problem.

Correct me if I am wrong... When verify the integrity of the Game cache is run...Doesn't it flag and download/re-install any Steam installed file that has been changed such as sound files and modified shape and texrture files.... etc. In addition to any other altered/corrupt steam installed core and DLC files.

Which brings up another question. If one has to re-install his system the current instructions are to delete everything in the Steam Folder with the exception of steam.exe and the steamapps folder, then running the steam.exe. With last month's update, all of the content information was removed from the steamapps folder leaving only a few files one of which being appmanifest_24010.acf. It appears the local content data (probably some sort of checksum) that was in the old steamapps folder now resides in the depotcache folder which resides in the Steam Folder. So the question is if one has to rebuild their system Is the method of saving the steamapps folder and deleting everything else except steam.exe still valid?

Yeah. If you edit a wagon's sound file, that will be marked as "failed to verify", by the verify tool. "Failed to verify" does not necessarily mean that a file is "corrupt". Editing any default object, causes it to be corrupt in the verify tool's point of view. (I'm talking about the dumb thing like it has feelings! )

Another possibility is that another application or service touched the files. This was a problem back when anti-virus programs started to become mainstream. In fact it was only a couple years ago I had to work in depth with McAfee because they were inspecting one of our database files while it was being written too. It never flagged it or show a warning, it was simply looking at our file... but it held it long enough to cause a write error. We ended up needing to be white listed with them.

PapaXpress wrote:...it was only a couple years ago I had to work in depth with McAfee...

No wonder the man is so paranoid, and here I thought it was the jungle heat!

So, any modification to an RSC-originated file will cause it to fail verification? For example, sound modifications, rolling stock camera modifications, etc.? Does that mean that such modifications also lead to SBHH errors? The only modification I apply regularly is the TaD RW Loco Upgrade, which is currently undergoing some kind of perpetual adjustment to TS2013 compatibility. Does using this package lead to file verification failures?

The modifications will not likely lead to an SBHH, but you are right when you say that all those things, will cause it to fail verification and it will be reverted back to it's default stage.

Yes, if you verify the local files then you will have to re-apply any modifications you made to RSC files (more exactly, any files you got from Steam).
That's the reason for all the discussions you've seen in this forum about batch files.

Hack wrote:No wonder the man is so paranoid, and here I thought it was the jungle heat!

One man can bear only so much trauma!

AFAIK even changing the date or time on the file will cause a verification to occur. If the attributes are changed in any way then the same happens ie R A S H or -R -A -S -H.
As someone points out above this a dumb "CHECKSUM" app which btw is not infallible and if it finds any changes in any RSC file it will report a verification error and that the file needs to be reacquired.
The other problem with cache verification on STEAM is that if you don't log off from Steam between verifications (or better reboot your pc) the second and any subsequent verfication may fail or return a false positive.
Using Doc's (Lisboa) batch file is a must after a verification.
Regards
pH