Inability to assign destinations to ships

I have the same problem in DA but only with fleets. Individual ships will autopilot like normal but fleets will only autopilot if the destination is only one move more than the fleet's max moves.

I get around this in an awkward way by disbanding fleets, shift-click dragging a selection box over the ship and then assigning a destination. Just remember to re-assemble the ships into a fleet once they reach teh destination.

There's gotta be a better way though...

I have the same issue as IsAlreadyInUse. No problem with individual ships, but fleets don't go where you want them to-- they just sit in the same place, round after round unless you move them manually a short distance (one day's travel) at a time. Very annoying.

I didn't have this issue until I upgraded to Dark Avatar, so I'm thinking something got goofed up in the expansion pack. I have the latest version of both.

Hope this gets fixed soon. Annoying to micro-manage fleets.

Thought I should add:

This is Dark Avatar with 1.80g.100

Maybe it is just fleets. But I have been playing DA for quite some time on my old XP rig and never had this problem, with fleets or individual ships.

I might add that I tried to set a waypoint and make my ships go there also--no luck. And it does appear that the max distance I can right click on and have an autopilot response is just about the distance a fleet or ship can travel in one turn.

This is a bug that makes gameplay unmanageable, because you just cant micromanage your ships and fleets like this each turn.

See this

mrakomo:

Yes this post seems to be the exact same bug...reported WAY BACK IN NOVEMBER. Why then, does the latest DA build not address this problem,(devs)? Did the latest version of DA fix this problem for the rest of you guys? I only see one other post about what seems to be a pretty severe bug.

I figured out that despite the update from SDC, my computer still reads the game as version 1.8e instead of 1.8 q. Thus, the fixed pathfinding error still exists. I also reinstalled it, the same thing happened. Then I read on another post that I have to ALTER MY REGISTRY to fix it such that the computer will recognize the update.

Bad. I will not mess with my registry--to me, thats like messing with the DNA of my body.

I love you folks at Stardock, but this need s to be a fix from SDC, not a tweak by me to my registry.

I recently installed DA on my laptop, it was reporting the version as 1.80g100 - a fresh full install. I was getting the destination problem. What I did was go into the registry and change the DA version to 1.70 and update the game via SDC, and after rebooting I was happily pummeling the Korx into submission again. Seems to me some file may have been corrupted or the fresh installation from SDC is somehow broken.

Steps taken to fix:

1. Change registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Stardock\Drengin.net\GalCiv2\DarkAvatar
Change 1.80g100 to 1.70

2. Updated DA via SDC

3. Reboot

Hope this helps.

Naz

Thanks for the tip. I Took the plunge and did the registry fix and all is well.

hello everyone. This is my first post, and i have been experienceing the same problem.
I also can not find the registry on my computer. I have looked everywhere, but no luck.
wondering if anyone else know where it would be,
Steps taken to fix:

1. Change registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Stardock\Drengin.net\GalCiv2\DarkAvatar
Change 1.80g100 to 1.70

2. Updated DA via SDC

3. Reboot
does not work, as they is no software folder, or drengin.net, anywhere on my harddrive.

The registry does not exist like normal files do.

Start-->Run: Type "regedit" (without quotes). Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Stardock\Drengin.net\GalCiv2\DarkAvatar. Modify Version to 1.7. Then run SDC and update DA.

Rebooting is actually not necessary, but can be done if you'd like.

Alternatively, http://files.filefront.com/Keyreg/;9530968;/fileinfo.html will do the job for you on any Windows version 98 or newer. While I haven't verified that it works with Vista, I can't find any reason that it shouldn't. Feel free to run it through a virus scanner and/or open it in notepad; it's clean.

Your other option would be to uninstall and reinstall.

Thanks. I have now fixed the problem, and gone back to killing species.

It happened also to me after updating to the latest version at some moment in December. In my opinion the problem came included in a revision of the game. I also experienced stealth ships attacking my rear lines since them. None of this issues are comfortable and seriously affect the playability of the game. Furthermore I started having ramdom crashes when I never have this before, and this is far more serious.

Two weeks ago I had to format my computer and reinstall everything again, including the latest version displayed at Stardock. The three problems mentioned are still there and by now I am getting disappointed at the way Stardock is handling this. Somehow I was totally sure that an official correction would be posted somewhere after few weeks of having the people complaining about this. To my knowledge there are at least four posts raising this issue.

I will try the solution proposed by Sole Soul for lack of other alternative. Thanks for that Sole!

This I did and the problem was solved. Very easy to do for people that, like me, do not know much about computers. Thanks a lot Sole. I am very happy now.