Relocate Bug With Long range weapons fire?

I had a UP treaty get allowed that automaticly retreats ships neutral area during a war declaration. Several times my ships would be relocated by the game upon attacking an enmey ship, but the weopons fire (mine and the enemy) would travel accoss a great distances to hit the enemp ship I had attacked. I can't remember all the details at this point. It even happens when attacking ships at planets. Has anyone else seen similar?

Another bug? All my ships qued to auto-attack the enemy took off to meet at some location in space where there was nothing, not even a meeting point. They just keep stacking-up there. If I moved a ship off that location, the move would be fine, then I'd hit the auto-attack key, but the ship would move back to that same spot and ignore a nearby enemy within range. I had to end all the auto-attacks and do it manually the rest of the game. It just wouldn't work.

Not a bug, but should the AI always be chasing protected freighter (I built the special that protectd my freighters) all the time in wars? They are wasting time, but such kept a lot enemy ships off my back, lol.

In trades, it is way too hard to dial-in values with the slider for "influence." The bar selects huge amounts with just a tiny move. AI should eb more willing to trade large amounts of influence (esp minors), because there is so much of to trade; esp for cures; yet, they'll only trade a tiny thousand for a cure to some nasty mega event; only trading just a litte in losing peace deal to avoid war, etc.

Is the cultural victory become impractical in DA? I think it is become way too time consuming to accomplish verses other methods to win. There needd to be a few ultra high-end tech influence goodies that can get constructed to speed things a long... just thinking aloud. Also: allies should get more irritated when another ally builds influences bases in their space: I get no AI gripes for doing so and flipping some of their planets.

The ship stack-group window thingy isn't updating well to reflect current created stacks in this up-date (this didn't used to happen before). I have to select off to something, then back to see the current stacks, then pick a stack to move.

The tech goody to let any ship investigate/expore things in space comes way too late to be useful. The space goodies are all gone by then...

Game engine speed seems greatly improved, including graphic up-dates. Well done.

I'm playing DA version 0.20.026 on windows 2000, high-end P4 PC.


2,351 views 3 replies
Reply #1 Top
I'm playing DA version 0.20.026 on windows 2000, high-end P4 PC.


Please make sure you put DA reports in the 'Beta Reports' forum rather than the 'Bug Reports' forum (which is for standard GC2) in the future.
Reply #2 Top
I've experienced the first bug you mentioned exactly as you described it, and something very similar to the second bug as well.

The first bug happens when an enemy planet is located within your sphere of influence when war is declared. The UP "Neutral Territory" event causes the ships on their planet to be transported outside of your territory so that they appear elsewhere on the map (because positioning your ships before a war is "cowardly"), but when you attack the planet they are still considered to be defending it. The result is that you fire across the map to hit the ship. I sent in a save game of this, only to discover that reloading the game rectified the problem, so I don't know whether the save game file helped them at all.

Regarding the second bug, sometimes when I reload all of my idle ships target a particular area on the map. In a recent game, all my ships began following around my original colony ship (which was still floating around on auto-explore because my starting position was too far from any colonizable planets for it to be of any use). This was actually an issue in DL as well. In past versions of the game I've had all my ships automatically travel to the first starbase I constructed (which was also the first starbase any race had constructed) after loading a saved game. Strange stuff. Haven't figured out what causes it.
Reply #3 Top
I've found the source of the first bug.  It has now been fixed.  Thanks for the details on how to reproduce it.  I saw it happen once, but wasn't sure what caused it.  You were right about it being the ships in orbit.  Thanks again.