mobhack:
Quote:
I have never seen anything like that, and there is no AI code which "measures danger" like that.
|
Wow, that is fantastic, because it's happened on two totally different parts of the map. Both the exact situation, where I have a few platoons of the "very same" tank overlooking a valley. The tanks in both cases had absolutely nothing obstructing them, as I couldn't destroy them. It finally got to the point that I got frustrated and brought some help from other places, but one of them is still ongoing now. This is occuring over at least 3-4 (more like 6 or 7) turns, so it's not like they haven't had time to get re-directed and take another path. Naturally, I can only tell you what it is doing, not why. Now since this seesm to be unbelievable, I will be on watch for it in the future and do a save when I have clearcut evidence, but as my saves stand, only the PZ38 one has any semblance of showing this behavior, and at this point an unbeliever wouldn't be too convinced with what it looks like now, as I have made some "other" adjustments as I said.
Quote:
Again- they don't do that. However if your unit is now known about then they may be going somewhere else, or an objective nearby has flipped, or they have decided the hex entry cost is too much (with wrecks in it now) and have gone around another route. Or are simply hanging back as there is now a random choice if enemy is known, to close - the original SP 'tin lemming' code simply charged the objectives with anything that could move, regardless. Our AI code has a little subtlety built in.
|
They may not be doing that, but it looks an awfully lot like it learned from the first tank going down to both fires from those hills: "They destroyed us at the next hex, therefore we shall not approach more closely". I'm not kidding. It's like that engineer thing I mentioned. I haven't played the latest version of winspww2 very much but I have never seen anything like this before. See also the peculiar air strike I mentioned. There was absolutely no reason that should has happened, unless you think that the air strikes are willing to go after something at random, which I have certainly not ever seen, esecially since there was absolutely no way he spotted the units. The only thing I can figure is there's some very rare random code where they learn where a unit is or more likely just some glitch that exposed them but there wasn't any gamewise explanation for.
You will notice one key ingredient to my story of the tansk not going any further though...they both are facing hills with only one kind of tank on them. One hill has "nothing" but PZIVB's, while the other nothing but PZ38t's. So what may be happening, or at least it alwasy was in my prior games, I always had something of a mix on those hills. So while the gang could rely, in this case of the return fire being almost exactly the same, though at somewhat different distances, in the other example he could not, because they can't account for both the distance and the difference in tanks being a consistent pattern. the "only" way i have managed to break these things up at all, apart than some of the help I brought from other places in various forms, was to actually move some of the tanks closer. It's like they accounted for the original fire and it's distance, but when I uncharacteristically moved forward against heavy odds they didn't account for it, though they might fruitlessly return fire. Part of the key also, might be, that I only sent at most 2-3 of the total 10 or so tanks forward and kept all tanks firing. To leave some of them further back firing as well, though fruitless pretty much, might had kept him from accounting for the forward moving fire. Yes, I know, you say that doesn't happen, they don't re-calculate and "know" when that AP will start firing, or that it's effect, in the case of the PZ38's, will climb one more point in damage, therefore endangering them, but it's screwy nonetheless. Certainly nothing I have ever seen before.
Good to see the stories about the filtering as well.