ainwood said:I certainly don't see those lines.
What OS are you running?
ainwood said:Well, I use snoopy's terrain at home as well (although I over-wrote the default terrain, rather than use it from the scenario folder), and it works fine.
ainwood said:As Methos suggests, you can export a screenshot.
City placements should stay from one turn to the next, but are not saved (if you shut-down CivAssist and start it again). Is there a big need to keep them?
General view settings? Like what?TruePurple said:Would you please add the ability to save such settings? (not just city placement but general view settings as well) It would be very much appreciated.
Its actually just allocated memory, not used memory. To demonstrate, have CivAssist running, and check the memory usage. Then minimise it, and watch the memory drop. This is something to do with how the .Net framework handles memory allocation, apparently. If other apps are using the memory, then apparently it doesn't allocate as much. I'm not really sure of the details, but I read a bit about it when I saw it consuming 120 MB of RAM! (Dropped to 5 MB by minimising it though).Niklas said:Really great tool! I only wish it wasn't so memory consuming, since Civ itself is already such a beast in that regard, but I will certainly use it none the less.
Good point - I'll change it to only show exact tech costs for ones that you can 'see', and show full-costs for ones you can't.Small bug report:
I don't know if this has been reported yet, but the Tech tab contains spoiler info as to how many of your rivals have a tech that you cannot research yet (and thus shouldn't be able to see). The spoiler comes about through the reported cost for researching the tech. The info can be used to gain an advantage in trading rounds, since you can correctly predict if someone will have "the next tech in line" as well.
ainwood said:General view settings? Like what?
ainwood said:Its actually just allocated memory, not used memory. To demonstrate, have CivAssist running, and check the memory usage. Then minimise it, and watch the memory drop. This is something to do with how the .Net framework handles memory allocation, apparently. If other apps are using the memory, then apparently it doesn't allocate as much. I'm not really sure of the details, but I read a bit about it when I saw it consuming 120 MB of RAM! (Dropped to 5 MB by minimising it though).
Are you using the archive? If so, is it lagging at the start of each turn? That might be the autosave compression kicking-in. It runs on a separate thread with lower priority, so it shouldn't cause too many problems (if so, try turning-off the achive for a while, and see if it makes a difference). Maybe we should make archive compression optional.Michelangelo said:Is it better then to first start CIV3 and when it's up and running start CA2? I find in game my cursor lagging sometimes. Now that I read this I think restarting CA2 makes it better. Not sure though, maybe wishfull thinking.