I've not been able to reproduce from saved games but runtime error for type-aa is occasionally occuring. see screen shot

I'll continue to try for a reproducable saved game, it seems more likely to occur in larger rather than smaller scenarios.

This is happening in AirAttacker meaning aircraft attacking anything else.  AirAttacker isn't able to figure out what kind of unit it is attacking (which is very strange) so the type does not get set, hence the uninitialized variable.  More to come, probably in the form of additional logging to narrow down the root problem.

 

On 8/23/2022 at 11:24 PM, TonyE said:

This is happening in AirAttacker meaning aircraft attacking anything else.  AirAttacker isn't able to figure out what kind of unit it is attacking (which is very strange) so the type does not get set, hence the uninitialized variable.  More to come, probably in the form of additional logging to narrow down the root problem.

 

Thats a good clue as to what to look for, I assume it applies to both sides?

4 hours ago, donaldseadog said:

Thats a good clue as to what to look for, I assume it applies to both sides?

Correct, we haven't narrowed it down much so given what we currently know, it applies to both sides.

To help troubleshoot, please run 2022.013 with ac_ai logging turned on.  If the troublesome code is triggered, you will get an assertion error.  At that point, grab your ge.log, zip and upload it for analysis (a saved game from that game second or the one before would help too).  

Example command line (activates ac_ai supplemental logging to ge.log and autosaves every game second rolling over after 255 saves): Winharp32.exe -l ac_ai -S000010255 

The log entries of interest will look something like:

100232 Combat5.c:1580 - G TCR:AirAttacker: BOm.. AirTargetType =  
100232 Combat5.c:1602 - G BOm:target_type = 109, range=1325, bearing=208
100232 Combat5.c:1658 - WR.attack_type=6, auto_flag=1
100232 Combat5.c:1696 - after case, gflag=0, wrange=0, WR.weapon_range=0, attack type (type_aa)=4

use db hcdb150929 GE 2022.013, BS westpac

the screen shot in the zip shows the game time at error, the saved game comes in one second before. If you start the saved game at zero time compression then advance to 1:1 you should get the error.

The group ATA had orders at a course point to attack a group that has now disappeared

Log file shows

130500 Combat5.c:1580 - G ATA:AirAttacker: ZWH.. AirTargetType =  

a dozen or so lines before the end, in the last second of game.

ge-type-aa.zip

Edited August 30, 20223 yr by donaldseadog
added extra observation

Excellent example with which to recreate the situation, it triggers every time for me :).

Digging in...

  The target group is ZWH as indicated in your ge.log.  That target group still exists and has an AS.565 Panther helicopter in the air.  However, you/the player no longer detects any units of group ZWH so it is and should be difficult for your group ATA to execute an attack.  

   The lack of detected units of ZWH causes the get_group_type() call from GetTargetType to return the default value of 'R' which means Reference Point/REF.  GetTargetType returns that value of REF to AirAttacker.

I've added code to abandon the attack in this case.

Fix coded and deployed as part of 2022.014

confirm problem fixed 2022.014

Air group goes to loiter, no error message received, game proceeds correctly