Battle Bug

This MUST be a bug.

A fleet of Altarian ships attack my fleet.  We are at war, so it was no surprise.  It said "defeat likely" (which is why I didn't attack them first), but since I knew it was going to be an EPIC battle even if I lost it, I watched it in the battle viewer.  I should have popped popcorn for this one!

Well, in the battle, I lost all of my ships except for the flagship/command ship.  And my commander WON!  I got the dialog screen saying "VICTORY!"

I knew it would be close, but I never expected that!  Whoohoo!

But...when returning to the main display, I see that an Altarian fleet of 5 ships remains, and my fleet is gone.

So maybe I lost that fight.  But then the cinematic battle should not have worked out that way.  I'm a bit upset, because I think the battle viewer and the main game display should always be in agreement as to the outcome of a battle.  Always, without deviation!

By the way, I had another fleet in orbit around Ciago III, which I had just taken from the Altarians.  My 2nd fleet, still fresh from wresting the planet from a small orbiting contingent, proceeded to pound the carp out of the Altarians, and from there I easily took the planet where the attacking fleet came from, Ciago II.

I lost a fleet but held one planet and took another, so it all worked out as I had expected.  Not my best moment in battle, but you do your best when you get attacked.

So I think there are a couple of bugs in the battle viewer:

1.  Results not the same as shown AFTER the battle.  It happened only this one time, and it happened when my fleet was was the defender.

2.  As some ships "go red" while they take on damage, sometimes the red will stop rising from the bottom of the ship icon, but the ship will go "grey", showing that it has been destroyed.  Not a critical thing, but kind of annoying.

3.  In the battle viewer, there is always a significant lag of several seconds (up to almost 10 seconds) between the battle log showing a ship is destroyed and the expected explosion of that ship.  I'd like to see the timing a little bit closer.

 

17,542 views 6 replies
Reply #1 Top

Has anybody else experienced this issue?

Reply #2 Top

Not me, but I didn't fight that many wars yet ...

Reply #3 Top

Yah sure minor lag when the ship is being destroyed. I have to disagree withe outcome recommendation. All i should know before a battle is probability not definates. I do agree the battle should agree with the outcome. I can see that being annoying watching your ships win only to find out they lost.

Reply #4 Top

Quoting admiralWillyWilber, reply 3

Yah sure minor lag when the ship is being destroyed. I have to disagree withe outcome recommendation. All i should know before a battle is probability not definates. I do agree the battle should agree with the outcome. I can see that being annoying watching your ships win only to find out they lost.
End of admiralWillyWilber's quote

In my experience the outcome doesn't always go like the beforehand prediction if it is close, but as I said I never saw a dfferent behaviour in battle viewer than the actual outcome. But admittedly I watch very few battles with the viewer.

Reply #5 Top

All the time leading to middle of GC3.

 

Has always been an issue.  I havn't had the defeat likely and then a win. Usually i have a Victory Certain + 10x the power the battleviewer shows me winning then the battle is over and i lost and barely look any enemy ships with me. I have noticed by saving before these battles and this happens you just reload and the fight goes more as planned.

 

 

Reply #6 Top

I do watch a lot of battles because that's when I can see how my fleet stacks up; for example, is the opposing fleet hitting me early with a lot of long range weapons with me not responding until midrange or close quarters?  Or is my fleet basically going quiet as we get into bad breath distances?

Sure, if I managed my research efforts and built my fleets correctly, I'll be shooting at all ranges.  But sometimes seeing is believing.

I'm already autosaving every 2 turns, plus the occasional manual save.  So if the bug appears again I'll try the reload thing.