Railworks America

I see they moved the Clear Cache function from the Utilities program back to the game program. The description of the clear cache function states "Forces a reset of installed DLC". Does this still mean that it only deletes blueprint.pak files or does it now also restore any "modded" files to default?

TIA

Samwolf wrote:I see they moved the Clear Cache function from the Utilities program back to the game program. The description of the clear cache function states "Forces a reset of installed DLC". Does this still mean that it only deletes blueprint.pak files or does it now also restore any "modded" files to default?

TIA

Deleting all blueprint.pak is in fact forcing a reset of all DLC that had a .pak before cleanning.
And not only they cause dump crashes but other unwanted effects in the game:
Take a look to my Big Boy a couple days ago. These two pictures were before and after cleaning the cache:

Oh my that's not good always,something with rsc dtg.

The blueprint cache is just a binary version of some of the DLC's blueprints. This is done for performance reasons.
If the cache files are corrupted, or if the original blueprint has changed, then you clear the cache and the game will rebuild it as needed.
This has nothing to do with resetting mods, unless this behaviour has recently changed.

Also I have always seen this function in the game, not in utilities. Perhaps I missed some change.

Samwolf wrote:I see they moved the Clear Cache function from the Utilities program back to the game program. The description of the clear cache function states "Forces a reset of installed DLC". Does this still mean that it only deletes blueprint.pak files or does it now also restore any "modded" files to default?
TIA

May I respectfully state that the clear cache function has never been in the Package Manager Utilities Programme, which is shown thus -



The clear cache button is in your ''Settings'' area of the game and is to kickstart anything that you have recently installed from the Workshop, or, an item of DLC from Steam, which will then show up in the game/or, RW Tools, as thus -



To delete blueprints regularly, may I suggest that you go into your search area of your computer where your game is after playing with it, type in Blueprints.pak and then delete whatever comes up, this will keep your game in tip top condition, new sets of Blueprints are created every time you play in the game, so, you need to delete these daily, or, after every play session.



Cheerz. ex-railwayman.

Thanks for the replies.
P.S. I believe back in TS2013 or TS2014 the clear cache function was in the utilities program.

It might have been but it's been in the settings for a couple of years.

Clearing the BluePrint.pak too often results in stuttery game play.
I only delete the BluePrint.pak for a particular DLC I'm modding leaving other stuff alone.
Or after a big update, I'll clear them in the whole game.

I have never cleared these out. What's the purpose of this clearing?

Sometimes changes won't take effect until the cache is cleared, as it keeps a shadow of the route's assets in a single file for faster loading - similar to OLE, but may also hold extra data. If you make a change to an existing asset (not add or remove one), there's a pretty good chance that you won't see those changes.

Case in point was a recent series of edits on the geometry of ScaleRail. I could figure out why my changes weren't showing up until I remembered to clear cache. That solved everything.

I have always just done a re-start from scratch and have never had this problem other than with numbers and I'm not sure if this would cure this. I have always had to delete the asset re-start and then put the asset back in to change numbers.

Clearing cache is not a cure all. I rarely use it myself, and only as a last result or before attempting a verify.

Changes to an asset's blueprint (engine blueprint, wagon blueprint, etc) usually won't be applied unless you delete the relevant cache file. This is not true for some (or maybe all?) secondary blueprints. For example, changes to an engine's camera blueprint show up immediately by just reloading in the game. I suppose they are not cached.