Issue with Upgrading Ship Designs.
Mainly an issue with overwriting older designs, and overwriting designs yet to be discovered.
from 
GalCiv2 Forums
GalCiv2 Forums
First off I use the "No Hull" Mod because I like making my ships look exactly how I like 
So each game I set up a few hulls that I will upgrade (And rename) to get the actual ships I use.
Now as my designs get upgraded over time I don't change the name, I don't build out of date designs so it gets rid of the clutter.
Also I don't keep the older/initial designs because since each game I operate a little differently, I will always have to redesign the ships anyways.
In a single game this works fine, and in the next game I end up changing the names a bit so it wasn't a problem.
However then I started the campaign. Each time I end up wanting the same name and an issue cropped up.
I get a CTD when I overwrite a design that i haven't discovered yet, and also when saving ship designs I get crashes at seemingly random times, but I think its just because I overwrote a name I forgot about.
Also if that is rather convoluted, I can describe a step by step way to recreate this issue. I think anyways.
So each game I set up a few hulls that I will upgrade (And rename) to get the actual ships I use.
Now as my designs get upgraded over time I don't change the name, I don't build out of date designs so it gets rid of the clutter.
Also I don't keep the older/initial designs because since each game I operate a little differently, I will always have to redesign the ships anyways.
In a single game this works fine, and in the next game I end up changing the names a bit so it wasn't a problem.
However then I started the campaign. Each time I end up wanting the same name and an issue cropped up.
I get a CTD when I overwrite a design that i haven't discovered yet, and also when saving ship designs I get crashes at seemingly random times, but I think its just because I overwrote a name I forgot about.
Also if that is rather convoluted, I can describe a step by step way to recreate this issue. I think anyways.