velshin velshin

Move and attack orders randomly cancel in 1.04

Move and attack orders randomly cancel in 1.04

    I've played 1.04 a bit now and seen movement and attack orders randomly canceled, the result of which is that a ship will go off and do something else. For example, if you tell your siege cap to attack a planet, it will do so for awhile, but then for no apparent reason (and without giving orders to that ship or even any other ship in the same grav well), the siege cap will turn around and attack a nearby enemy frigate. The siege cap wasn't part of a fleet, auto attack was off, and auto join fleet was turned on but there were no fleets in the grav well.

Another example, a set of ships (not in a fleet, no other fleet in the grav well) would be all told to attack an enemy heavy frigate, then some ships (not all) would switch targets to a different enemy frigate before the first was destroyed.

Both my friend and I have seen this behavior repeatedly with our own ships. Games are usually 2 players vs 3 hard AI (aggressor, fortifier, researcher).

Unrelated, seems like with all the botched updates (people complaining about 1.04 crashing etc.) that you guys should leave the previous update online in case people need to revert. You know, a little link at the bottom of Downloads "click here for previous versions" or somesuch.



10,803 views 31 replies
Reply #26 Top
My friend and I caught a long game this weekend and we didn't see these movement bugs at all. (Us vs 5 compys on hard.) I assume since the Ironclad guys haven't been able to reproduce it, and no one that has seen the bug has been able to consistently reproduce it, that this is going to be troublesome to get fixed.

If anyone sees this bug, please save the game and send it to [email protected] Thank you!!

Reply #27 Top
You should've been a beta tester velshin :P Can't speak for others, but I as a bug hunter appreciate you taking it seriously and trying to track it down - so many just post about a strange problem expecting a fix, not realizing that without any info or means of reproducing/observing it it's incredibly difficult to narrow down.

So, uh, thanks :P I still haven't seen it in any post 1.04 games I played :( Hopefully someone will be able to get a save.
Reply #28 Top
I'm a developer so I very much understand how frustrating it is to reproduce stuff like this. Cheers for the kudos. (Were those kudos with all the ptthppt =P ?)

I'd give Ironclad a repro case for the bug like I do for Derby et al if I could ;) Unfortunately my friend and I weren't savvy enough to save a game right when we were witnessing the bug and we couldn't find the auto save that matched.

Annatar11 are you @ Ironclad or just happily in love with Sins?


Reply #29 Top
I have a smiley face disorder where I usually end up putting tons of them in posts, but yeah that was a kudos! ;)

And no, I'm not with Ironclad, just an old beta tester who's still actively helping them track down bugs and issues :)