Ages ago, I made a post about some pretty significant AI -issues, and was eventually - late in the conversation - suggested to move the thread to this section, which I now finally have.
I'm not going to bother with repeating everything I said, so please refer to said post itself. It was just about as informative as I could possibly make it without writing a 4000 -word essay no-one would be able to get themselves to read through, anyways.
http://forums.introversion.co.uk/multiw ... php?t=2137
To get right to the point, I thought it would be more helpful if I could provide a few screenshots and a more detailed, (But short!), description of a particular example.
In order to reproduce one of the biggest bugs in question, I played a Blitzkrieg -match against the AI, (Hard, I mean to recall.), on the first map on the list; "Confrontation Point". In this particular battle, the AI picked the red teamcolour. No settings were changed from the default as far as I can remember on the spot, other than the time limit - I increased it for the purpose of the example.
|--------------------------------|
As the match starts, the gate spews out the first batch of Multiwinians. Most pile into the waiting Armour. The Armour, for some reason, drives halfway up the hill leading down from the gate, and just sits there.
Once a second Armour is aquired, it drives up to its immeasurably retarded colleague on the hill, and stays in place, occationally bumping into it.
Multiwinians fill up the two Amours, who just stand there. It seems the AI wants to move them somewhere, as their engines seem to be running; the two vehicles almost appearing to be stuck. The other Multiwinians who spawn either move out to seize the control points or bunch up right next to the (now full?) Armours, inexplicably.
...And that's pretty much what they do for the entire match. They sometimes manage to get something done with some of the availiable Multiwinians at hand, and whenever the Armours are obliterated, they are finally "free" to actually go out and do something, until the Armours respawn, and they're back to normal. And I'm stuck with an entire map left unplayable.
|--------------------------------|
I'm really wondering what seems to be causing this seemingly utterly broken behaviour. And is it possible that the devs or bugtesters or whatever missed this? It's kind of hard to miss, in my opinnion - all you have to do is start a single match on Confrontation Point, and the bug is right in your face after about five seconds. Or can it possibly be that I'm the only one getting these problems? Please, someone start a match on Confrontation Point against an AI and see for yourselves. It ought to be immediately visible. Is it the AI code being fundamentally flawed? Is it simply a pathfinding/waypoint problem on certain maps and in certain situaions?
Any reply to shed light upon the issue would be most welcome. I can only hope the devs themselves catch a whiff of this.
*EDIT* Whooo! Images are working, now!
