Page 1 of 1

[BUG][1.2.11beta] Crash - Dinasty Egyptians / Double Moves

Posted: Fri Jul 09, 2010 6:54 pm
by cothyso
It happened repeatedly (but not everytime), while commanding a unit to make a double move closing to enemy's battle line:

Code: Select all

NullPointerException
1.2.11 2010 07 09
{}
gamelogic.s.PlayLogicImp.movePathValid o gamelogic.s.AncientsMovePathImp  o gamelogic.s.PlayLogicImp i4A1i4b
gamelogic.s.PlayLogicImp.GrowMovePath  o gamelogic.s.PlayLogicImp i4
gamelogic.s.PlayLogicImp.GrowPath  o gamelogic.s.PlayLogicImp i4i4i4
gamelogic.s.PlayLogicImp.GrowPath  o gamelogic.s.PlayLogicImp i4i4
uiplayer.s.PlayPhase.MouseMove  o uiplayer.s.PlayPhase i4i4i4b
uiplayer.UIImp.MouseMove  o uiplayer.UIImp i4i4i4b
uiplayer.htk.TMapImp.MouseMove  o uiplayer.htk.TMapImp i4i4
uiplayer.htk.TWindowImp.MouseMove  o uiplayer.htk.TWindowImp i4i4
uiplayer.htk.GraphicsArea.MouseMoveOrDrag  o uiplayer.htk.GraphicsArea i4i4i4 uiplayer.htk.GraphicsArea.MouseMoveType 
uiplayer.htk.GraphicsArea.Event MouseMove  o uiplayer.htk.GraphicsArea i4i4
Delegate.Invoke  
Application. CallFunctionWithExceptionHandling  o Application p
 Main
  main
PS: my game was against Dinasty Egyptians too, and the game was crashing when my double moved unit came close to their battle line, probably revealing some unit. Obviously the bug has to do with Dinasty Egyptians.

Posted: Sat Jul 10, 2010 6:15 am
by Hoplite1963
I have also had this in an newly set up IF DAG game when I try and do a double move for the 3rd to 5th time. The armies were 30th Dyn Egyptions (mine) verses Persionsb.

Posted: Sat Jul 10, 2010 7:24 am
by amenofi64
Hoplite1963 wrote:I have also had this in an newly set up IF DAG game when I try and do a double move for the 3rd to 5th time. The armies were 30th Dyn Egyptions (mine) verses Persionsb.
I too i've the same situation (armies: 30th Dyn Egyptions (IA) verses Late Romans (mine), at the 7th time.

Posted: Sat Jul 10, 2010 9:10 am
by keithmartinsmith
Looking at this and will NOT fixed as part of 1.2.12. keith

Posted: Mon Jul 12, 2010 10:10 am
by EricS
Thanks for reporting this bug, it will be fixed in version 1.2.14.