I just purchased the game yesterday, but have played about a half-dozen skirmish battles so far. And I am noticing that the AI player (1v1) QUITE OFTEN gets stuck at 54 score, and doesn't go beyond that. It's like it can't figure out what to do because (something unforseen by coders?) happened too early, perhaps. I am playing with neutral defenders guarding expansions, so maybe AI engineer is getting killed from one of those neutral groups. It's frustrating, and I do hope you guys fix it ASAP. It does not seem to be limited to any single map, as I have been playing the 2 player maps only, and it seems to happen regardless of map.
What AI difficulty setting are you playing with?
Normal difficulty and below, only. I haven't tried anything higher than that yet.
I have never had issues with normal or higher (until now have not tried lower).
I have just started a game on beginner, and after 3 min the AI is still at fluctuating between 28-53 (I am going to call that DOA). Probably an issue with low difficulty settings.
Edit: After about 12 minutes it had crept up to around 400.
Have you had this issue when playing against normal AI?
I would recommend verifying your steam cache.
You may want to submit a support ticket (instructions at bottom of general troubleshooting page):
https://esupport.stardock.com/index.php?/default_import/Knowledgebase/Article/View/530/175/general-ashes-troubleshooting
Did you have the neutral defenders option turned on? I am not sure what causes it. I have always played AI skirmish with those defender points defended by neutral player, to limit expansion speed. The AI build bug does not always happen. And it may be because I play it on slow and slower speed as well, and adjust the game speed back and forth a lot. I gave the best description I could. The AI gets to the mid 50s in score, and doesn't appear to know what to do after. And I can go in there with an army of any size I want, and he'll be there with his size 54 base, and it's just not much fun. I don't know if playing it on a faster speed or harder difficulty changes it, because it is an intermittant bug. The programmers who understand the AI behavior should have an idea of what it's SUPPOSED to be doing at the 54 score point. And that should hopefully help them isolate this bug. And FTR, it's an 8-core AMD FX-8350 @ 4GHz/core with an R9 290 ATI video card and 16 GB of DDR3 RAM w/Win7.
I always play with neutral defenders on.
I will run some tests with slow/slower game speeds to see if I can replicate the issue.
On a totally separate note, running on slower doesn't appear to slow down the node capture time, which makes capturing nodes relatively much quicker. Dodgy.
The game feels completely broken at slower game speeds, I would suspect this is the cause of the problem.
The time factors have a lot of dodgy things going on effecting game balance, I was able to capture 2 nodes with an engineer that I had built from the seed before the creeps began to spawn. It isn't just the node capture time though, regen rates, combat, it all seems out of whack when playing on Slower speed settings.
Playing against Beginner AI on Slower, the AI stayed at 28 until around the 30 minute mark, dropped to 4, then at the 45 minute mark I put it out of its misery, it had done nothing.
Playing against Normal AI on Slower, the AI took about 20 minutes to exceed the 54 score bottleneck (this score would represent 2 engineers, building a base, not building an army). After about 40 minutes it had crawled its way up to a score of 400, and had captured 4 nodes around the seed although the AI was easily wiped out.
Edit: Two comparison clips below demonstrating the relative difference in game speed.
Normal Speed - 2 Nodes captured before creeps spawn:
Slower Speed - 5 Nodes easily captured before creeps spawn:
There are many great features available to you once you register, including:
Sign in or Create Account
