Log in

View Full Version : Movement bug

Kuritza
October 24th, 2007, 09:56 AM
Look at the two pictures. Before.jpg is before host, turn 16, After.jpg is after host, turn 17.

http://www.ljplus.ru/img4/s/h/shudoyama/before.JPG
http://www.ljplus.ru/img4/s/h/shudoyama/after.JPG

Selected armies simply dont move. We tried rehosting it - unsuccesfully, they stand still. As you can see, there is also no fighting going on in either starting or targeted province, which sometimes causes armies to stop, so we have no logical explaination other than 'bug'
NTJedi
October 24th, 2007, 12:18 PM
I can confirm I've also encountered this bug and it's painful.
Kuritza... can you provide Edi with the saved game files and map files so the bug can be added into the bug thread.
Sombre
October 24th, 2007, 12:23 PM
I got this again and again in one game. If it happens to you, don't keep issuing the same order over and over, because usually the bug just occurs every turn. You have to move them into a different province, split up armies etc, then try again.

I never had this before 3.10, but that's probably a coincidence.
Edi
October 24th, 2007, 01:01 PM
If you have the save files somewhere, attaching them to this thread would be a good thing. Then I can just link it to the shortlist entry.
Kuritza
October 25th, 2007, 07:31 AM
I'm affraid it was a MP game, so my 2h alone wouldnt help much. In the end, we did some rehostings and my opponent was able to attack me instead - we were moving towards each other, as it turned out. So there was a battle, albeit on my therritory, which suited me.
NTJedi
October 25th, 2007, 11:29 AM
Kuritza said:
I'm affraid it was a MP game, so my 2h alone wouldnt help much. In the end, we did some rehostings and my opponent was able to attack me instead - we were moving towards each other, as it turned out. So there was a battle, albeit on my therritory, which suited me.



This means one way provinces are already possible, if only the GUI also displayed the arrow as one way and if only we knew exactly how to reproduce the issue.
lch
October 25th, 2007, 03:00 PM
This bug isn't new in 3.10, it has happened across versions. I believe that it's some rare bug in the movement logic that has been in there from the beginning.
ioticus
October 25th, 2007, 04:26 PM
I've had the same thing happen in Dominions 2.