Posts made by maudlin27

v161 Update
Happy Christmas (almost!) everyone! 12 changes in this update, including:

• Introduced new T2 bomber snipe logic - sometimes M28 should decide to just go for a T2 bomber snipe in place of its normal approach to the game (i.e. even if the enemy ACU is on full health)
• Fixed a significant bug that could break M28's asf logic introduced in v160
• Various adjustments to M28's snipe logic, so it shoudl be less likely to suicide gunships into a damaged ACU with significant anti-air defences
• Bombers should no longer immediately charge at a vulnerable ACU to damage it, but instead should build up their force and either abandon the attack if the enemy ACU gets in a safe position (e.g. under a shield), or attack in one go.
• Fixed a bug relating to the TML targeting logic
• 1 MOD specific change (reverting overcharge change made in v160 as the issue it was addressing should hopefully be resolved now)

Acknowledgements

• Radde replay from a few versions ago that prompted me to revisit M28's snipe logic (which then prompted me to introduce T2 bomber snipe logic)

v160 Update
16 changes, including:

• Tweaks to TML fatboy targeting to make the TMLs get built quicker during a mass or power stall, and making them more likely to target in certain cases
• M28's land units should be more cautious if they only slightly outrange the enemy (vs before where they'd be suicidal on the assumption they could kite)
• Fixed some occasional issues that could happen with air staging points being on water
• Air scouts should no longer be targeted near the enemy base even if M28 has air control.
• 2 workarounds for a LOUD mod for an issue with overcharge and an issue with bomber weapon range categories

Acknowledgements
Replays from the following:

• Tazor
• Lohkrim
• c04spoon
• Vortex
  (also had some from Radde which I hope to work through in the next release)

v159 Update
Continuing the recent trend of smaller but quicker updates, this one features 10 changes, including:

• Longer ranged naval units should be more likely to engage enemy surface threats even if there are nearby subs
• Added new logic for land untis deciding whether to attack a nearby enemy unit that is in the water, so they should factor in their likely range if they reach the water, and (if they cant go in water) if they can reach the enemy from land
• Units should be less likely to suicide to protect an aval base if that base has been destroyed
• ACU should cancel its upgrade if faced with a dangerous nearby threat

Acknowledgements:

• Relent0r - Identifying a typo with M28's hook of a TML missile callback that was causing compatibility issues with RNG
• Vortex, Lohkrim and c04spoon - Replays highlighting various issues that prompted most of this update's changes

v158 Update
8 changes, including:

• More aggressive gunships where they identify enemies in a zone that have moved away from nearby ground AA
• Greater use of TMLs outside the core base
• Arti drops should consider dropping the enemy base if it appears poorly defended
• ACUs should be more aggressive if they outrange the enemy ACU, but also less likely to suicide into multiple T2 PD

Acknowledgements

• Radde - Providing various replays which prompted most of these changes
• Various others who have provided replays in the last few days - I'm still working through a backlog of v155 replay based changes but hope to move onto more recent ones soon.

v157 Update
11 Changes, including:

• New fatboy TML snipe logic
• Naval MAA units should run from nearby enemy land units
• More generally made it more likely that nearby enemy units in an adjacent zone are taken into account when deciding if a unit needs to run (to hopefully reduce instances of naval units moving into enemy range and dying)
• Asfs should hopefully try and avoid enemy nukes
• Fixed a bug with FA Mission 6 if shared armies mode was used

Acknowledgements

• art-wiedzmin - highlighting shared armies bug in campaign
• Radde - Various replays
• Wes Maggs - Replay where M28 rallied its asfs on an island even as a nuke missile could be seen about to hit it

@art-wiedzmin Thanks, this will be fixed in the next release

Thanks for the feedback. I'd need a replay to investigate most of the poitns further, but many of them are working as intended/due to limitations in how the AI is structured:

1. ASFs should stay relatively close to gunships and/or experimental bombers, but on a large map with multiple such units I could see them getting out of position
2. Gunships should factor in enemy ground AA threat not just if it has air superiority, so will depend on the circumstances
3. They should strike locations without any nearby anti-air units if they have air control, otherwise they should only engage if confident of winning
4. I expect they're running from enemy AA (significant ground or air) - assuming we're talking about 15 czars/soulrippers then I presume there were hundreds of asfs and/or 40+ SAMs levels of anti-air
5. It should build a mix of units (frigates, destroyers, battleships) and engage with the shorter ranged units when it thinks it can win, so I'd need a replay if it is just suiciding destroyers into battleships (assuming we're not talking about it trying to defend an attack on its naval base)
6. Replay would be needed as it should intercept strat snipe attempts; however it's only really capable of surviving against 1 mavor, not 2 (and I cant see that changing given FAF balance)
7. I'd need a replay to understand this, as I would've expected an SACU teleport to be a 1-way trip
8. Replay with time stamp and building where this happens would help with investigating

Another point to check is you're using the latest versions of the mods in case there was an error that's been fixed (e.g. checking the log, the version of M28 used was v142- so a decent chance the errors relating to M28 were resolved in a more recent update, although I'll add a couple of redundancies in the upcoming release for the specific error message).

FAF's already incorporated adjustments to allow more momory, but my understanding (from others who understand things like this better than me) is that the garbage collector used by FA.exe can temporarily require very large amounts of memory, meaning if the game goes over 2GB there is a significant risk of it crashing due to this.
As such, while FAF doesnt immediately crash when 2gb is hit, it may crash soon after.

Memory can be reduced by reducing mods, player counts (e.g. in the case of AI games), unit counts, unit variety (e.g. playing with everyone as the same faction uses less memory than having all factions in play), smaller maps.

@goblinsly2 Not currently, no

A decent chance it is, as repeated errors seem to have a significant correlation with crashes. I can look into/try and fix the error messages for the next M28 release, and even if it's not the cause of the crash it should at least make it a bit easier to diagnose the crash cause if it reoccurs.

@Sainse said in Add high unit cap lobby options:

@Sprouto said in Add high unit cap lobby options:

The game simply doesn't have the memory to support games that size - even if the performance could handle it.

First time I'm hearing this. What size exactly?

If the game goes over 2GB memory the game becomes unstable and prone to crashing. The number of units in-game appears to impact on memory usage, amongst various other factors (including mods)

v156 Update
14 changes, including:

• A few different build orders and early game approaches added to try and make M28 a bit more unpredictable (for now whether it rushes a bomber; gets no bomber at all; gets LABs or no LABs, although long term I'm hoping to add some further variation)
• Adjusted how short range units support longer ranged units where they're having their retreat cut off
• A team with a mix of different factions should prioritise ahwassas if they decide to build an air experimental

Acknowledgements

• Jorne - 1v1 vs M28 Easy
• Radde - Lots of teamgame replays vs M28

While I'm not sure on the answer to your question, I'd note that if you do find a solution it won't impact M28AI (or M27AI) as they use custom threat assessments, so the threat values in the blueprint have no impact on them.
Blueprint threat values are relevant to AIs that use the built in "IMAP" threat system - at a high level, this divides the map into squares, and calculates the threat of units in that square with a few different threat types. The threat then decays gradually over time when the units leave that square.

@MrPhalanx Just to check, is the chat bug something that happens in the latest version v155 (as there was a bug with this in a previous version)

v155 Update
Another mini update:

• Fixed a typo relating to a niche scenario where considering whether to get a novax to help with enemy naval threats
• Reworked ASF support logic so they should try and stay even closer to a friendly experimental air unit than before
• Fixed a bug with working out if a table is empty (that I presume has been around in both M28 and M27 for 3-4 years!)
• Asfs should be more likely to engage enemies attacking restorers and czars (by including the restorer/czar anti-air capabilities when deciding whether the fight can be won)
• Fixed an issue with M28's chat messages not working in LOUD (introduced in v152)

Acknowledgements

• Radde - several more replays
• C04spoon - Mentioning that M28's chat messages had stopped working in LOUD

v154 Update

• Fixed a bug that meant M28 logic relating to units damaging others wasn't triggering (e.g. relevant for determining if units aren't blocked from hitting enemies) and expanded to add a redundancy for gunships to make sure they retreat when damaged.
• Island drops should no longer try and drop on islands with enemy PD
• Fixed several occasional issues with M28's late-game arti template (building T3 pgens in the designated place for T3 arti; engineers owned by an M28 teammate blocking construction)
• When an experimental dies, most of hte time M28 should assign an engineer from a nearby base to reclaim the wreck (in additino to its normal reclaim logic)
• Fixed a rare bug that could mean a unit on attack-move being given a move order would stay attacking.

v152 and v153 updates
21 changes, including:

• Fixing a bug where M28 wouldnt build mass storage if player 1 was an M28 teammate who died
• Fixed several issues relating to shared armies (message should only display to the person clicking the button; air staging should release M28 controlled units even if they haven't been toggled to have control; non-M28 controlled friendly units shouldnt be reclaimed for mass)
• Land experimentals that cant kite should be less likely to retreat from an enemy experimental
• Fixed a bug where M28 would incorrectly consider the enemy to have no naval threat
• Torpedo launchers should no longer be built in response to an enemy engineer
• Transports should be more likely to be built, and introduced 'engineer support' transport logic so if a plateau wants an SMD and has no t3 engineers one should be airlifted over

Acknowledgements

• Radde – Various replays (which were the basis for the majority of changes)
• Marlo – Highlighting issue on fort Clarke assault where some of the M28 ACUs would suicide into T1 PD
• Cleo – describing some issues with shared armies mode where M28 would reclaim friendly units.

v151 Update
Smaller hotfix update with 7 changes:

• Short ranged units should be less likely to attack enemies and should try and group closer together
• Units whose shots are blocked should be slightly more likely to move than before.
• Fixed a bug that would break all M28 ACUs for the rest of the game if M28 thought an enemy ACU could be killed. Also added in a redundancy so in future it should only temporarily break the logic if such a bug was to reoccur.
• Experimentals should be slightly more likely to suicide into an enemy experimental instead of retreating (although this will need further refinement).

Acknowledgements

• Radde - A number of replays
• Vortex - several LOUD replays

v150 Update
12 more changes, including:

• Sub consolidation logic to try and group subs together when fighting more often
• Gunships should retreat to heal up sooner if they're having a habit of dying to ground defences
• Made adjustemnts to ACU aggression to only factor in friendly direct fire units
• Several adjustments for dodging missiles (to make it less likely units try to dodge)
• 2 MOD specific changes, including improving M28's assessment of whether it will win an air fight in LOUD when inties are involved.

Acknowledgements

• Radde – Several more replays (on v148)
• C04spoon – LOUD replay
• Vortex – LOUD replay