Verifying and clearing chache

[hygoose]

I have been having some serious problems with my game crashing when I try to run a free roam, some quick drives and any attempt to build or edit. A file verify says 5392 files fail and I can see they are reacquired when running verify again (why not have an automatic response when the reacquire is done?) I immediately run the game again and have the same problems and a verify says the same 5392 files fail. That problem has existed for some time, sometimes ok, sometimes just crashing. Maybe I need to clear the local cache but what exactly happens if I do?

Clearing the cache do I lose my 3rd party downloads or just the Steam/DTG ?

Can I clear just the basic game program files (I cannot access the current sale info or discussions from the main menu. They are there but don't work.

I'd appreciate any thoughts about all this and possible remedies.
Thanks

[OldAlaskaGuy]

Clearing the cache does nothing to your game files, it only removes files that are loaded for your current game session. A file verify can remove some customizations only if the origional files were downloaded through Steam from DTG and you changed those files within the .ap. Those customizations will revert back to their origional state. Generally any 3rd party will not be changed. Customizations made outside the .ap are safe. Customizations made within the .ap will revert upon a file verify.
Here is an easy way to clear cache without starting TS:
http://steamcommunity.com/sharedfiles/filedetails/?id=465303891

[hygoose]

Rwaday, thanks for the info about how a cache handles files. It doesn't appear that simply clearing the cache will deal with my problem. If I am getting crashes within the game when trying certain functions like editing a scenario in "Build" or running a certain free roam scenario, could a program file be at fault and how might I deal with that if Verify says things are OK?

[OldAlaskaGuy]

I see that you have over 1400 hours for the game. Can you provide some background as when this started to happen?

[hygoose]

The crashing problem has been around intermittenly for a year or more. At one time I thought it was related to the periodic updates of Windows which now seem more frequent. Verifying would often fix it. The crash usually happens when the Drive or Build function is being loaded - sometimes immediately and sometimes after 30 seconds or more of loading. Sometimes I think I can load a free run scenerio after first running a quick drive one - but mostly not. Sometimes it seems nothing will successfully load. Sometimers verifying the files and replacing the 5392 failed ones (always the same number) things will work. In the last couple of months however, that does not always correct the problem.

I do have a great deal of 3rd party content and sometimes its builds are the most reluctant to load although everything I have has successfully run numerous times before without problems. I have just finished verifying and see "all files verify." I will try a loading and report what specifically happens.

[OldAlaskaGuy]

I do not know how much system memory you have but if it is less tham 8GB this could be an issue. Try clearing the cache before game start and after each scenario.

[dcshoe]

There's an outside chance it may be a virus problem, possibly a false positive. Depending on your virus scanner, check the scanner logs. I had a problem with Windows Defender some time ago but was able to identify the file and exempt it from the scan.

[Phase3]

Most likey to be a workshop scenario, that yo have downloaded n the past (and forgotten) Maybe worthwhile to unsubscribe to WS files and delete them from your PC. Rebuild the scenario database file as well

[OldAlaskaGuy]

Good possibility.

[hygoose]

Thanks to all who have suggested cures (I have 12gb of ram.) I have just spent several hours testing exactly what works and what doesn't. After again verifying and finally getting a "all files validated," I began trying various combinations in Quick Drive, Career, Standard and Free Roam. Certain routes trigger a crash and others are ok, and each's group of scenarios either all work or not at all.. The failing routes (Donner Pass, Colton & NOrthern, Castle Rock, Sherman Hill, Rascal to Cottonwood, Far North, etc) might share some texture or scenery element. Ones that work ok (NY to New Haven, Horseshoe Curve, Cajon Pass, The Racetrack, London to Brighton, Marias Pass, etc) may not share the defective element that causes the crash.

It also seems that the defective routes also do not work when selected for Quick Drive or Standard and the good ones do. I have 74 routes including clones and many scenarios and have not tested every one in each way of running so I can't say what works in every situation except that the failures seem to be consistently the same and the "failed to validate" count is always the same: 5392 files. I don't know exactly what is being reacquired each time (watching in Resource Monitor Disk writes) it all goes past too fast to see all, but I have seen numerous AllAboard, 3DTrains, VNHRR scenic elements and textures, as well as a large mass of routes and scenerios all being re written to disc.

Questions: If I deleted my hard disc versions of the AllAboard, 3dtrains Vnhrr folders, would the Verify process restore and maybe repair them?

Given the above testing, would the deletion of workshop scenarios still be a potential cure?

Checking with Windows Defender I should look for what?

When referring to my "cache", is that the collection of folders I have on my hard disc in Railworks or is it just what is loaded into memory as called for? If they are different, is the flawed file(s) just being reloaded and not being basically having been repalced or repaired?

I'm sorta desperate and thank everyone that's offered suggestions. Please keep them coming.

[OldAlaskaGuy]

File verify will NOT correct 3rd party items. One last thing. Run logmate in your Railworks folder then start the game and preceed to where you are having issues. The last entry will tell you where your problem lies.

[76561198219211377]

Originally posted by hygoose:

...The failing routes (Donner Pass, Colton & NOrthern, Castle Rock, Sherman Hill, Rascal to Cottonwood, Far North, etc) might share some texture or scenery element.

Solely on this point FWIW I got Sherman Hill with TS2016 and Castle Rock from the Workshop a month or three ago. Sherman Hill uses it's own assets while Castle Rock uses the old US Loco's and Assets pack. I'll stand ready to be corrected on this but it seems unlikely that they share anything.

[hygoose]

I appreciate all the suggestions. Thanks.

RWADAY, I have run logmate on several of the failing free roam loads and get the same response each time:

[RunTimeError 10:47:40 PM] Trace mdump.cpp : 422 = error handlers have been set
[Content 10:47:40 PM] Trace cBlueprintLibrary.cpp : 417 = Blueprint set not found : Kuju, RailSimulatorCore
[Content 10:47:40 PM] Trace cBlueprintLibrary.cpp : 448 = Blueprint set not found for: Cameras\EditCamera001.xml
[Content 10:48:00 PM] Trace cBlueprintLibrary.cpp : 417 = Blueprint set not found : RWA , Lakeside
[Content 10:48:00 PM] Trace cBlueprintLibrary.cpp : 448 = Blueprint set not found for: RailVehicles\Diesel\RS-1\RWA\Engine\Alco_RS-1_001.xml
[Content 10:48:00 PM] Trace cBlueprintLibrary.cpp : 417 = Blueprint set not found : RWA , Lakeside
[RunTimeError 10:48:39 PM] cBlueprintSet::loadFile File exists in blueprint set, but is not a valid blueprint: RailNetwork\TrackRules\PONtrack.bin
[RunTimeError 10:48:39 PM]
[RunTimeError 10:48:39 PM] cBlueprintSet::loadFile()
[RunTimeError 10:48:39 PM]
[RunTimeError 10:48:39 PM] cBlueprintSet.cpp : 367

I'm not sure how to read this but it appears that either RWA or RailNetwork is creating the problem. Looking at Railworks assets in Utilities, it appears numerous ones are red (missing?) in kuju railsimulator US and castlerock scenery. Should I uninstall all railworks in Utilities and re acquire them via Verify, or should I just delete the cBlueprintSet.cpp :367? Should I also uninstall RWA Lakeside which I have separately?

All informed thoughts considered :)

[hygoose]

Again my thanks to all the above that offered suggestions and cures. As can be seen, I followed RWAday's suggestion using logmate, deleted some stuff and watched what it showed. I finally deleted the entire KUJU asset folder and reacquired it. Now everything is fine. Rwaday, you're the guy! Hope someone else can benefit from this thread.

[OldAlaskaGuy]

Thank you, glad to be of help.