We all know what a pain-in-the-hole it is when stuff is installed via STEAM or otherwise and you’re not exactly sure what files have been affected. So I have written a System-Snapshots Manager that allows you to take a snapshot of the complete RailWorks folder and then identify differences to the current system. Plus of course, it can be used to monitor your own ongoing modifications. Still WIP, but a damn sight better than anything else I’m aware of. Note that files are NOT themselves physically snapshotted (i.e. copied somewhere) but the file last-modified dates are recorded, which then be compared with a current system so a detailed list of which files have been affected (Created, Deleted or Modified) and saved to a CSV file if req. The above example is from about a year ago when I was updating AP stuff and my snapshots were interesting. Note that the compression mechanism has been updated since, so that the saved snapshot files are now only about 10% of the size on disk. The example detailed listing above was generated by taking a new Snapshot then running TSC, amending the Profile audio volume (playerprofiles.bin), then serzing a few stock files (note that the AP\WeatherEP updates are the AP Weather mods kicking in on TSC start) then comparing the saved Snapshot to the current system. You get the idea. FastLeg