Hi, im going thru the DA campaign right now and ive got a rather strange/annoying problem.
When i want my ships to travel some distance via the autopilot, say 15-20 squares, the ships doesnt want to move for some reason. When i see the amount of moves that i have left, it gives some weired number like 4/0 (4 being the moves left and 0 being the moves total the ships can make). but 4/0 doesnt make sense, it should have showed 1/4 or 0/4 after the moves being done.
I then have to take my ships and move them a shorter distance, usualy close to the maximum moves it can do this turn and it moves there. I didnt have this problem with the Dread Lord version of the game, only Dark Avatar somehow.
Gets a bit annoying because, whenever i need to do long distances, i have to make all the moves myself, time consuming.
Not all ships seems affected, builders for example are fine, colony ships also (but never tried to fleet them so maybe they could have the same problem if they were in a fleet?).
I read somewhere to update to latest version as older versions have this bug but i am at latest right now, stardock reports DA as version 1.80g.100 and no updates available.
Could use some help fixing this! Thanks in advance.
Stardock will report as 1.80g.100 even though you're playing 1.80e.100 or some such, it's another bug that just makes getting rid of the one you're having more annoying.
Basically, you need to actually start the game and see what version you are actually playing. I'm betting it's 1.80e.something. I'm not sure what the safe, recommended way to fix the problem is. Since I like playing with fire, I used regedit to find the appropriate key and changed the version listed from 1.80g.100 to 1.80e.100, at which point Stardock would update me to the real 1.80g.100. Messing with regedit is hideously unsafe, though, so I don't recommend doing it unless you're really comfortable doing stuff that could totally bork your computer if you do it wrong.
Possibly an uninstall/reinstall may be called for? As I said, I like playing with fire, so I never looked for a *SAFE* way to fix the problem.