It looks like you are using version 1.02 of the high-resolution mod, which is for DA. LogicSquence has released version 2.0 of this mod for ToA. You might want to try upgrading to this version. You can get it over at I-Mod - http://www.i-mod-productions.com/downloads.php?do=file&id=78 Hope this helps.
TwoPence
Hmmm...Long time lurker wants to know.... :) edit -> Guess I havn't been lurking that long after all.
One advantage of linking the application with the LARGEADDRESSAWARE flag is under x64 OS's, WOW64 will give a 32-bit application a full 4GB of virtual user memory. This 4GB, under WOW64, is unshared memory. Another plus, there is no need mess around with RAM tuning, like the /3GB switch you need on the 32-bit OS's; the 4GB allocation is automatic under WOW64. It would allow GalCiv to scale with the OS, like it currently does with hardware.
The 32-bit 2GB memory limit is a pain, especially when trying to use any of the graphics mods. We're switching over to x64 OS's at work and I've been reading up on memory handling under different versions of Windows. Is GalCiv compatible with the LARGEMEMORYAWARE linker flag? That should give 4GB of virtual user address under WOW64 (or up to 3GB for folks who want to tune their 32-bit system's boot options) without impacting the application in a standard 32-bit environment. I'm sure yo
You can stop MCP SmartStart from loading at bootup. In Startdock Central, go to Options in the Tools menu and under General Settings, uncheck Enable MCP notification area support. Exit SD Central and reboot. Edit - Wrong setting listed in original post. E.
I get that too with the beta. Seems to happen with saved designs that are loaded in at startup. Can update fine initially, but once I continue from a save, I get the "too large" message. However, custom ship designs I create from scratch during the game can be updated after continuing from a save.