Dignan, sounds like a classic case of mod soup, with a tip of the hat to the man who invented that term. It happens to everyone with a normal appetite for trying something new in Silent Hunter. Bits of mods get left in the code that conflict with each other, typically a command to plot a ship that isn't part of your present configuration.
Here's what I do. First of all, I maintain a pristine, write protected installation in its own directory, for instance \Wolves of the Pacific Pristine. I don't play that at all. It has no mods.
Then I have my playing directory \Wolves of the Pacific. When I find myself with mod soup, and it either has happened or will happen to everyone, I can restore the stock setup simply by uninstalling all my mods, then copying all the files from my pristine directory into my game directory. Reinstall the mods and carry on as if nothing bad had ever happened! You should never have to do a complete reinstall again.
Since both my directories and files in the pristine installation are write protected, I have to make sure that I write enable everything I copy into my playing directory. Ah, where's xcopy these days of the uberGUI?
|