AI Problem - Game Crashes When Enemy Jagger Target Is Out of Range

[DeletedUser]

The only common theme i've seen is that it's always when i use a Jaegar to attack another unit that has stealth capability but whom may not be in stealth/trees at that particular moment.

 

[Amy Steele]

It's not just in bonus areas or where Jaegers/Rangers/Units that hide in forest are attacking/being attacked... this was for the easternmost sector of Canturia and featured my HMA Fasts and Short Ranged, and EMA Long Ranged v the AI's HMA Heavy/Long combination. I was down to one Long and hit 'Surrender' - I'm certain I hit surrender not 'autocomplete'. The 'An internal error has occurred' came up, and before I could take a screenshot the AI's remaining Heavies had taken their turn and finished off my one remaining Long.

The battle result came up, obscuring the 'Internal Error' message. When I clicked 'OK' to dismiss the battle result, this happened...

Spoiler

The game then froze and I had to reload.

EDIT: When it happened before it was in Houndsmoor, this time was Fel Dranghyr. though I am pretty certain that on both occasions my units were in the upper left of the battle area, as with the OP, certainly that was the case on this last occasion.

 

[DeletedUser7719]

If you hit surrender before it was your turn.The outcome does make sense as the game finishes moving the AI before yours comes to actually surrender

 

[Amy Steele]

Thanks byeordie - I think I may have done that. The internal error still should not have happened though

 

[DeletedUser]

This still happening to people since the last update? Havent personally had a problem since.

 

[Amy Steele]

Yes, still happening since 1.03 - the above instance happened to me just today

 

[DeletedUser7719]

Is this the same bug?

Spoiler

 

[DeletedUser4906]

If you hit surrender before it was your turn.The outcome does make sense as the game finishes moving the AI before yours comes to actually surrender

I NEVER surrender, i'll take as many of the nefarious miscreants to the gate's of Hell if i'm gonna go.........

 

[DeletedUser]

Maybe i have observed another detail:

*I had happen "internal error" twice.
*Both times i moved a Jaeger to its maximum range, as indicated by the initial colored range.
*Both times i saw, that another additional field to move to was highlighted after i moved the jaeger.
*OK great, +1 range -> i am moving to that new hex.
*Crash, both times.

Third round of trying:
*I did NOT move to the additional hex, but stayed at the "old" max range.
*no crash, could fight and continue battle.

Uneducated guess: A bug with calculating/re-calculcating the move ranges between old and new maps. The unit moves to a hex, where it shouldn't be able to move to due to wrong range calculation.

 

[DeletedUser8813]

Maybe i have observed another detail:

*I had happen "internal error" twice.
*Both times i moved a Jaeger to its maximum range, as indicated by the initial colored range.
*Both times i saw, that another additional field to move to was highlighted after i moved the jaeger.
*OK great, +1 range -> i am moving to that new hex.
*Crash, both times.

Third round of trying:
*I did NOT move to the additional hex, but stayed at the "old" max range.
*no crash, could fight and continue battle.

Uneducated guess: A bug with calculating/re-calculcating the move ranges between old and new maps. The unit moves to a hex, where it shouldn't be able to move to due to wrong range calculation.

i can confirm this.... this has happened quite a bit yesterday,today i know not to try for that extra space it shows

 

[DeletedUser7719]

This has been reported in the zz server already, but I have yet to encounter this...

 

[DeletedUser]

Maybe i have observed another detail:

*I had happen "internal error" twice.
*Both times i moved a Jaeger to its maximum range, as indicated by the initial colored range.
*Both times i saw, that another additional field to move to was highlighted after i moved the jaeger.
*OK great, +1 range -> i am moving to that new hex.
*Crash, both times.

Third round of trying:
*I did NOT move to the additional hex, but stayed at the "old" max range.
*no crash, could fight and continue battle.

Uneducated guess: A bug with calculating/re-calculcating the move ranges between old and new maps. The unit moves to a hex, where it shouldn't be able to move to due to wrong range calculation.

Can confirm, happened with a Rapid Fire Cannon here.