RWDBFDup: a script for finding duplicate scenario GUIDs
Chacal
2015-08-22
UPDATED 2019-06-01
A simple script that will find any duplicates in a few seconds and print out the GUIDs and the names of the relevant scenarios and routes so you can remove unwanted ones.
Useful when you have the cryptic "Duplicate Scenario GUID in SerializeDatabase" message in Logmate.
RWDBFDup: a script for finding duplicate scenario GUIDs
Chacal
2015-08-22
Railworks (TS201x) keeps information about scenarios in your local scenario database,
which is a file named SDBCache.bin in the Railworks/Content folder.
Each scenario has a GUID (an ID number) looking like this: 180b376b-50d2-48b6-b77c-a4b18c75616c.
Scenario files are saved in a folder named with this GUID number.
Before TS2013, copying a scenario from one route to another was a simple matter of copying its folder.
Starting with TS2013, this is no longer possible because GUIDs now have to be unique in the database. If duplicate
GUIDs are found in the database, the game will, at worst, crash at startup and at best, complain with this unhelpful
message in Logmate: "Duplicate Scenario GUID in SerializeDatabase".
It is unhelpful because it doesn't say which scenario is duplicated, leaving you with the hopeless task of finding it
yourself.
Enter RWDBFDup, a simple script that will find any duplicates in a few seconds and print out the GUIDs and the names
of the relevant scenarios and routes so you can remove unwanted ones.
It is easy to use and harmless, since it makes no change to your scenario database.
We have 2433 guests and no members online