Presenting the CornCobMod or the CornCobMan's FunMod (I'm really creative and original with names you see).

Forum Thread
  Posts  
Fatal AI error - AI execution paused caused by Tau AI and Orks AI (Games : Dawn of War : Mods : CornCobMan's Fun Mod for Soulstorm : Forum : Feedback and bug reporting : Fatal AI error - AI execution paused caused by Tau AI and Orks AI) Locked
Thread Options
Sep 26 2018 Anchor

The issue, already present in v1.80.5 and caused only (or mainly and undoubtedly) by Tau, now (v1.81) is being caused by Orks as well.
I've put those races to a test by making a Tau only and Ork only matches. Done it once and here are the results:

All 7 of Ork AIs died within 10-15 minutes of gameplay (one after another) without crashing the game
3 Tau AI died after which the game crashed to crash report screen

Game rules used during the test:
Exterminate
Fast Abilities
Fortress
Heroes
Double Range Abilities

Oct 13 2018 Anchor

The Ork error should be fixed for the next patch. The Tau AI crash is getting looked at but I don't have a solution currently.

EDIT: The Tau crash has been identified (I think). Turns out it didn't really have anything to do with the AI at all. The Photon Grenade ability is actually bugged. It doesn't explode and lingers in the world indefinitely, potentially leading to a hard crash the more the ability is used.

Edited by: corncobman

Nov 13 2018 Anchor

As of 1.83, it seems that Ork AI no longer causes the issue or at least it doesn't occur when it usually used to occur (somewhat soon after producing Wartrukk). Haven't ran into the AI issue with Orks at all so far. The issue however, does still persist within Tau AI player (and it still is the "AI execution paused" error) and does not occur before Tau reaches high tech level (with Etheral being present on the battlefield) and during my testing of 4 Tau races vs 4 Ork races, only one Tau suffered that issue. It also happened second time when I picked random teams in a 2v2 game.

Nov 13 2018 Anchor

I did find a mistake with the Ethereal code that I thought was fixed for v1.83. I'll have another look at it later.

Reply to thread
click to sign in and post

Only registered members can share their thoughts. So come on! Join the community today (totally free - or sign in with your social account on the right) and join in the conversation.