M28AI Devlog (v97)

@AdAstraNoob Thanks I didn't know that. So one less Mod to care ^^

@maudlin27 Thank you for that information, we allways testing the Mods for compatibilty so no one gets random desync, game freeze or game crashes (looks like that Hive Enginnering Station Mod is making some random desyncs on some maps). Do you know a Mod or an ingame setting to reduce significant the RAM usage? I will try to do what u said in some posts above, but in larger games with units Mods its very difficult to not go over 2gb RAM usage.

@cyberdyne_skynet Graphic settings might impact things but Ive not tested to confirm.

However most benefits are likely to be a game setting thing - eg use 1-3 factions, fewer AI players, have a sub-1k unit cap, use a sub-20km sized map, play on a map with no water

I doubt you’d need to do all of these but just some of them may help

Hello Maudlin, your blog about the M28 is great. However, you should consider promoting the AI ​​feature in COOP missions more. Unfortunately, I have to admit that I only read the point this week and I suspect that many people don't know about this great option in the Mission. Maybe. This information should be sent to the FAF news area. sorry for my worst English

@saver I'm planning to request a news post once I've finished testing M28 as a hostile campaign AI on the rest of the Supcom campaign, since then I can highlight all the campaign features in one go and it's less likely to break the missions. For now it's mentioned in the mod description and on the wiki (re being an AI buddy), but I suspect not many people read them.

Here is a test of the first mission FA with your AI with three people. Unfortunately the game leaked a lot https://replay.faforever.com/21362409

In addition, construction took place again in the non-playable area. But otherwise it was a nice change

@saver said in M28AI Devlog (v58):

21362409

What do you mean by leaked a lot? did it slow down to -1 or worse game speed?

The game speed has fallen from 0 to -6 in the game. Unfortunately I don't know if it can be seen in the replay.

Mainly in cases where air battles started

I didnt notice when I was watching the replay but I stopped after 41m as I had enough points to look at by then, do you know roughly the timestamp where it went to -6? It makes sense that it would be slower in a big air battle although I wouldn't have expected -6 (assuming everyone has average to good cpus) so it could be an indication of something gone wrong with the code. It's also possible it's a result of some of the additional checks that have to be run in campaign maps that will add to the overhead (although again I wouldn't have expected such a big impact)

The game suddenly freezes completely after a certain time. Without error message and without replay. Whether with 2 or 4 players against an M28AI. You then have to end the game via the Task Manager. However, this only happens when you have reached the maximum of 1000 units (i.e. when you go on the attack). And it happens in every game. I have also noticed that the speed sometimes drops to -6.

We play with the following mods:

  • All Faction Quantum Gate
  • M28AI
  • Nuclear Repulsor Shields
  • Total Mayhem
  • Total Mayhem Lite
  • 5x Build Range

Are you aware of any incompatibility with any of these mods?

@klecks Not individually (some like Quantum gate, total mayhem and build range I've seen work fine, theo thers I've not specifically tested), but issues are much more likely to occur with multiple mods, either due to an incompatibility with a particular combination of mods; a bug with the mod that M28's logic highlights, or memory issues (which are more likely with more mods), in addition to the potential for a bug with M28.

If it happens with just one of those mods enabled then I can take a look to figure out. The other thing you could do is see if there's a log file (even if there's no replay - although I'd have normally expected a replay to be available for games played in FAF even if the game crashes part-way through).

For example logs are saved for me at the following location:
C:\Users[username]\AppData\Roaming\Forged Alliance Forever\logs

Have you always had these issues or has it only been since the latest release (last 24 hours)?

Also enable more detailed logging in the settins in the client, which increases the chance that the cause of the crash can be identified from the log:
1f94b479-7759-4038-a0e8-4378a9f50d12-image.png

v59 Update
A mix of campaign, replay and vs AI based changes with this update:

  • Fighting M27 - 9 changes; interestingly M28 beat M27 on 4 different 5km and 10km maps that M27 had been tested on extensively (theta passage, polar depression, twin rivers, and eye of the storm), making me think M28 had finally reached the point of convincingly dethroning M28. However, M28 lost on 2 20km maps (setons and burial mounds), contrary to what I'd have expected. The main change added was improving M28's ability to handle an early strat if it has asfs.
  • 8 changes based on replay comparisons from Radde between M28 and M27 on Xander, including making land experimentals more likely to move towards an enemy instead of attack-move, and fixed some issues with hos mongoose and MAA would retreat from units (the former being too cautious in some cases due to a bug, the latter ignoring nearby tanks due to a bug in some cases)
  • 5 changes from 2 mapgens where Radde and Mhad beat 1.5 resource M28s, mainly trying to make M28 slightly more resistant to air snipes
  • 9 changes from an M28 vs 1.2 RNG game on twin rivers (normally something M28 won but this time it lost after an epic 2 hour game due to poor fatboy usage) - the main change is making M28 retreat fatboys much sooner so they're less likely to be caught up to and killed, and increasing the extent to which M28 will eco when behind on eco.
  • 11 changes for Saver's FA mission 1 of the campaign to make M28 more aggressive with navy, have a better unit mix, send GCs at the enemy start position (instead of keeping them on patrol), and being more likely to build T3 arti/similar
  • 4 changes from a replay by Bart on gap of rohan, mainly fixing issues with overbuilding T2 arti and SAMs

Trophy awards

  • Radde trophy - Awarded to Radde and Mhad for beating 1.5 resource M28 on both a mixed land+navy mapgen, and a navy mapgen
  • Sladow trophy - Current holder is triangleleaf for beating v57 M28

Acknowledgements

  • Radde - sending various replays including a comparison of M27 and M28 to help me identify significant differences in their approaches that make M27 seem tougher for a human player
  • Saver - Replay against M28 as a hostile AI in campaign which highlighted a number of campaign specific issues
  • Bart - Replay in a norush gap of rohan high eco game which highlighted some flaws with M28's arti and SAM logic

@klecks said in M28AI Devlog (v59):

The game suddenly freezes completely after a certain time. Without error message and without replay. Whether with 2 or 4 players against an M28AI. You then have to end the game via the Task Manager. However, this only happens when you have reached the maximum of 1000 units (i.e. when you go on the attack). And it happens in every game. I have also noticed that the speed sometimes drops to -6.

We play with the following mods:

  • All Faction Quantum Gate
  • M28AI
  • Nuclear Repulsor Shields
  • Total Mayhem
  • Total Mayhem Lite
  • 5x Build Range

Are you aware of any incompatibility with any of these mods?

What you're talking about is probably related to memory. Maybe next time you can take a look at the memory usage for high unit quantities (via task manager).

@zhanghm18 We all have 32GB of RAM, so I don't think that's the reason for this

@klecks FAF is prone to crashing if you reach over 2GB of memory usage; i.e. if you have taskmanager open and you see it approaching 2gb, then it's much more likely to crash.

The memory usage is increased significantly by unit mods (along with various other factors), and has been known to crash with AI (including but not limited to M28) since AI also use up more memory.

@maudlin27 said in M28AI Devlog (v58):

AF is prone to crashing if you reach over 2GB of memory usage; i.e. if you have taskmanager open and you see it approaching 2gb, then it's much more likely to crash.
The memory usage is increased significantly by unit mods (along with various other factors), and has been known to crash with AI (including but not limited to M28) since AI also use up more memory.

2023-12-09_135140.jpg 2023-12-09_134742.jpg

OK, I understand. This is a screenshot from Task Manager when the game was frozen (two AI und only me). So the prolem with memory depends on the 32bit game 😞

@maudlin27
Hello 🙂 unfortunately I didn't write down any timestamps. I can only make the following statements about the PC used, the three of us use similar components: processor i7-8700 3.19GHz, 16 - 32GB RAM, Geforce 1080GTX and higher. I will also look at the replay to provide possible timestamps. Thank you again for your great work.

@maudlin27 Replay timestamp https://replay.faforever.com/21362409
min 43: -3, min 44: -4, min 45.20: -4, 45.40: -4, min 46.50: -5. Unfortunately I couldn't find -6. However, I only watched the end of the first section. I hope the data can be of some help to you.