I've gotten rather frustrated with the dodgy programming of the database functions. Frankly, it just doesn't seem to work very well and it does weird things that apparently cannot be resolved - or no one wants to bother resolving them.
Have you previously reported any such issues? If not, how do you know if they can be resolved or if we "want to bother" resolving them?
One of the most irritating things is how the game has seemingly picked random database entries and declared that once an image is assigned to it, that image is there forever more. Literally.
For instance, I've been slowly getting rid of the secondary images in the database - images that have a "t" in their names. I just find that half of them do not display correctly (I just get the square with the X inside it) or it wrecks the aesthetics of it, often causing the layout to be asymmetrical - which really triggers the OCD in me and, I'm sure, many others.
Thing is ... they cannot be deleted under any circumstances. Deleting them doesn't work. Emptying the recycle bin doesn't work. Even physically removing the image file from the folder altogether doesn't work. No matter what, when you click on the unit entry, the image magically pops right back into the folder. In fact, not only can you not delete the secondary image, the main image can't be deleted either. The files just pop back into the database folder as if by magic. I have no idea where the game is even getting these files if they've been removed from the folder and deleted. It's as if the game has a secret folder somewhere that is inaccessible by the players where a copy of all the image files are stored - and if one is deleted, the game simply makes a copy of the deleted file and puts it right back where it was regqrdless of what the player wants.
For instance, the entry for the 2009 version of the Da La Penne destroyer cannot be deleted whatsoever. Ship_1839 cannot be deleted. Ship_1839_t5 cannot be deleted. I've checked persmissions and all of that nonsense. But it seems to only happen with different random entries. Some database entries work just fine and files delete as per normal. Then you have these immortal files that cannot be deleted no matter what. Is this the fault of shoddy coding that will probably never be resolved? Or is there a fix? Thanks in advance.
As we have previously explained, CMO dynamically downloads DB images when the related platform/system is selected, or when a scenario containing said item is loaded. I would guess that this is why images re-appear after you delete them.
We are currently testing an optional setting for NOT fetching these images on-demand and instead leaving it up to the player to manually download & apply the image pack. This will take some time to appear in the public release branch. In the meantime, as a workaround, you could add a firewall/proxy rule that blocks the downloading of the images. You could either block the program as a whole (this would, however, also block the on-demand downloading of map tiles) or alternatively block the specific remote URL for the DB images ( http://warfaresims.slitherine.com/DBImages/ ).