No collision detection in M2tw.

[IceTorque]

I was just reading an interview with ken Turner lead programmer and Dan Toose designer in PC Powerplay

Do big battles coupled with individual unit textures and one-on-one fighting mean we'll need a massively powerful PC to run the game?

KT: Not at all. All the effects in the game use Shader Model 2.0 and while we've raised the minimum spec considerably, you should still get good performance from a pretty average PC. If you look closely, you'll see most of the fighting is what we call "Hollywood fighting". Weapons don't actually connect and soldiers don't actually touch. There's no collision detection at all which saves use hugely on CPU overhead. The combination of good art and clever camera angles means the game can look awesome and not choke your PC.

I thought I read somewhere that M2 soldiers would actually hit each other, not that I'm complaining as I love how smooth it runs on my old PC.
What excites me most about the no collision detection is that I was under the impression that the biggest obstacle to putting even larger armies on the battlefield was collision detection. Does this mean that the next TW game will maybe have much larger/realistic sized armies?

[alpaca]

Isn't there a 2d collision detection? Like, when two soldiers try to stand in the same place they can't?
Anyways, what would much larger units do for realism? If you play on huge, you already get very large armies and it doesn't change that much during a battle

[shaggy1973]

There is no need for collision detection as the game decides on hits from it defence vs attack stats engine. Collision detection is very resource hungry, imagine having to cheack 6000 soldiers for collision detection each cycle.

They may actually hit each other graphically, but "collision detection" is a graphics computing term and means something specific.

[Phalaxar]

Isn't there a 2d collision detection? Like, when two soldiers try to stand in the same place they can't?
Anyways, what would much larger units do for realism? If you play on huge, you already get very large armies and it doesn't change that much during a battle

Yes, I believe they do have a footprint (a 2D collision area on the ground). But seeing if corners overlap is much easier for small, simple (mathematically simple) 2D shapes than for 3D shapes with hundreds of verteces and a lot of weird angles.

I think it's great that CA are throwing thinking at this, rather than just brute computing power.

[Puzz3D]

Yes, I believe they do have a footprint (a 2D collision area on the ground). But seeing if corners overlap is much easier for small, simple (mathematically simple) 2D shapes than for 3D shapes with hundreds of verteces and a lot of weird angles.

I think it's great that CA are throwing thinking at this, rather than just brute computing power.

It's an octagon unless that's been simplified along with all the other simplifications made in the new battle engine. The thing I find strange is that in the M2TW demo it seems men are taking turns fighting. I see extra men who could be striking at an enemy waiting until the two men fighting finish. In the earlier games such as STW, extra men would crowd around a lone enemy, and they would all be striking at him within a single combat cycle.

[Censor]

I've seen that too, and it is frustrating seeing my guys get slaughtered one by one by King Francis when they could all bum rush him and take him down in a glorious melee.

[shifty157]

I see extra men who could be striking at an enemy waiting until the two men fighting finish. In the earlier games such as STW, extra men would crowd around a lone enemy, and they would all be striking at him within a single combat cycle.

Thats not good at all and should be fixed in a patch as soon as physically possible. Taking turns to fight in little duels completely removes any advantage numbers may have given.

[Puzz3D]

Thats not good at all and should be fixed in a patch as soon as physically possible. Taking turns to fight in little duels completely removes any advantage numbers may have given.

It does remove a lot of the advantage of having more men because the lone man can only strike at one of his attackers within a combat cycle, and with battlefield upgrades you can see how a man could become almost invincible as he kills one man after another if the other unit is of a weaker type. To be fair, I have seen double attacks by men, but my impression from watching a couple of encounters is that they are hesitant to do it. It seemed to me that unengaged men should be more aggressive about striking at an enemy man. I suppose it's possible this is one of the mechanisms that CA used to slow down combat resolution.

[screwtype]

Thats not good at all and should be fixed in a patch as soon as physically possible. Taking turns to fight in little duels completely removes any advantage numbers may have given.

Yes, I agree, this sounds like a very cheesy game mechanic. I hope it's not how the game actually works.

[IceTorque]

what would much larger units do for realism?

Realistic numbers = more realistic set piece battles and tactics with much greater game immersion, imo. In RTW in an attempt to immerse myself in the game, I imagined I was a lowly legion commander, albeit in charge of an under strength legion.

[Akka]

Isn't there a 2d collision detection? Like, when two soldiers try to stand in the same place they can't?

I'm pretty sure that, by "collision detection", they mean "weapon and target collision detection", like, in RTW, hoplite would actually aim and touch their ennemy with their spears, and the spear would connect.
As I understand it, in MTW2, there is simply one animation for "attack" for the attacker, one animation of "defense" for the defenser, and the weapon of the attacker isn't detected for collision (which means it can sometimes be a bit off-target).

If I guessed correctly, it's a minor graphical change of little impact that save a lot of computer power, and it totally unrelated with actual unit collision detection.