ModuleManager gets confused by CKAN-created symlinks

[hpax]

On Linux (at least), when creating a new game instance in CKAN, it creates a symlink to the KSP_Data directory of the previous instance. However, this causes ModuleManager to fail to be able to recreate the PartDatabase.cfg file, and the game silently crashes, appearing to keep loading forever.

The problem is that ModuleManager uses the filename

/KSP_Data/../PartDatabase.cfg

... whereas the game seems to want ...

<game_dir>/PartDatabase.cfg

Because KSP_Data is a symbolic link, these two paths do not point to the same location, and the game crashes.

[hpax]

What is interesting is that ModuleManager deletes the file in <game_dir>, but doesn't create a file in that location.

[hpax]

For anyone who sees this and has experienced the same problem, I have been running this shell script on my CKAN-created game instances as a workaround:

kspfix.sh