Better Hitboxes

[jit]

Is there any plan for the tremulous hitboxes to become more complex where bullets could go past alien legs or under their belly or under human legs? I did a search over hitboxes and read some, none of them were about tremulous having more complex hitboxes.

[Le Compilateur]

It would be nice if hitboxes didn't exist (you only hit if your shot hits the actual model), but that's not going to happen. Implementing this kind of precision would put more stress on the engine and bump the system requirements up a notch (correct me if I'm wrong).

[Divmax]

Per-polygon hit detection is very complex and would cause more stress on computers. And I have never heard of a Quake 3 modification having implemented per-polygon hit detection instead of hitboxes.

[_Equilibrium_]

Could we try giving aliens locational damage? I would like to see how it affects gameplay.

[Lakitu7]

Well, the thing with locational on aliens is that for most (all but the tyrant?) alien classes the head isn't any higher than the rest of the body. As a result, what do you make be the "head" region? The front? There's no easy way to do it like with humans, where the game just calls it a headshot if it's in the top (some number)% of the hitbox.

[Odin]

What happens here is that the server is actually the one calculating the hit, not the client. Think of the complexity of implementing per-poly hit checking when the server doesn't even currently use models for things. The hit box and the bounding box are all that the server tracks. If per-poly hit checking were implemented, it wouldn't slow down the client at all. It would just put a huge load on the server.

Return to Castle Wolfenstein was the first Q3 game(if I recall correctly) to implement separate hit boxes for the head and body, making the head harder to hit in multiplayer.

[+ OPTIMUS +]

Well, the thing with locational on aliens is that for most (all but the tyrant?) alien classes the head isn't any higher than the rest of the body. As a result, what do you make be the "head" region? The front? There's no easy way to do it like with humans, where the game just calls it a headshot if it's in the top (some number)% of the hitbox.

is it a big problem if the program calculates with horizontal percentage instead of vertical?
ofc i can imagine that rear-front is more subjective than top-leg as the model is turning.
or lol, i can imagine a "turnbot", what instantly flips the model for the time of being hit, so headshots would automatically go into the assholes of the aliens. asshole bot. groove :-) (would work as bots are using teleport at q3 at the moment of firing a lethal shot)
even without a bot, i could imagine a charging tyrant who - seeing the luci shot coming - is rapidly turning the ass to the damage to avoid the headshot.

"have you seen opti's perfect 'assturn' at the last game? man, that dude just owns! I wish to make assturns as neat as him!!!" bsdakgjadsjkhHAHHAHAHA

so logical features can turn funny, watch out :-)

[Bajsefar]

Stand your ground well, men!
Camp your turrets like you never did anything else!

For this is the

[Paradox]

Ummm.

[Le Compilateur]

Uh, what the hell...?

[+ OPTIMUS +]

highfivecopter.

owned. totally.

[Taiyo.uk]

Can you light their farts?

I think you should light their farts. They'd fly for miles.

[Lava Croft]

Per-polygon hit detection is very complex and would cause more stress on computers. And I have never heard of a Quake 3 modification having implemented per-polygon hit detection instead of hitboxes.

Soldier of Fortune 2 has per-poly hit detection.

[Paradox]

Halo3 has per poly hit detection.

Or at least thats what they said at the IT convention...

[Bajsefar]

But it WOULD cause more stress on computers, wouldn't it?

Is it needed?

I think the game is fun as it is-
Although the assturn definately sounded like a cool tactic. :p

[benmachine]

Locational damage by angle of hit (back, front etc.) is already implemented, I think.

[Bajsefar]

 
In what way? You mean the head-torso-leg thing, or is backstabbing possible? >.>

[Ivancool]

Soldier of Fortune 2 has per-poly hit detection.

Soldier of Fortune 1 (quake 2 engine) too. Furthermore, both SOF has the kickass Ghoul Technology but it's Closed source forever. I'm not sure  but i think that Doom 3 has per-poly hit detection and will be open source :-) but...

[jal]

Per-polygon hit detection is very complex and would cause more stress on computers. And I have never heard of a Quake 3 modification having implemented per-polygon hit detection instead of hitboxes.

Soldier of Fortune 2 has per-poly hit detection.

Q3 True combat too. Hacked in a mod.

Anyway, I wouldn't go for it.

[Lava Croft]

Soldier of Fortune 2 has per-poly hit detection.

Soldier of Fortune 1 (quake 2 engine) too. Furthermore, both SOF has the kickass Ghoul Technology but it's Closed source forever. I'm not sure  but i think that Doom 3 has per-poly hit detection and will be open source :-) but...

SoF1 has no per-poly hit detection. SoF1 uses what they call 'damage zones' or something. It's not per-poly hit detection as in SoF2 or DOOM3.

[Ivancool]

According to Kenn Hoekstra SoF has per-polygon detection and SoF2 has Per-pixel detection.

Kenn: The damage location system in Soldier of Fortune 2 is in there and is far more advanced than the system seen in the original game. In the original Soldier of Fortune, our hit-detection system worked on a per-polygon basis. That is, if you aimed your weapon at an enemy and fired, whichever polygon you hit on the enemy model would be destroyed, damage would appear, and the enemy would react accordingly. In Soldier of Fortune 2, the accuracy of the weapons has increased to exist on a per-pixel basis. More detailed skin pages and the GHOUL 2 rendering system allow us this increased accuracy. The original game had 26 damage zones on each enemy model. Soldier of Fortune 2 ups the ante to 36 damage and dismemberment zones per enemy.

Source:http://www.computerandvideogames.com/article.php?id=21627

[Lava Croft]

According to Kenn Hoekstra SoF has per-polygon detection and SoF2 has Per-pixel detection.

Kenn: The damage location system in Soldier of Fortune 2 is in there and is far more advanced than the system seen in the original game. In the original Soldier of Fortune, our hit-detection system worked on a per-polygon basis. That is, if you aimed your weapon at an enemy and fired, whichever polygon you hit on the enemy model would be destroyed, damage would appear, and the enemy would react accordingly. In Soldier of Fortune 2, the accuracy of the weapons has increased to exist on a per-pixel basis. More detailed skin pages and the GHOUL 2 rendering system allow us this increased accuracy. The original game had 26 damage zones on each enemy model. Soldier of Fortune 2 ups the ante to 36 damage and dismemberment zones per enemy.

Source:http://www.computerandvideogames.com/article.php?id=21627

In that case I have totally mixed up the names and I fail.

[techhead]

Halo 2 and Halo also had per-poly hit detection, but simplified collision models to conserve processor power, AFAIK.

[Paradox]

@techhead: facepalm, your right

[doomagent13]

This has come up before.  Let me see if I can remember anything...

The server should do all the hit/miss calculations, which it already does.  If possible, it might be best to get the server to do the related physics calculations with its GPU (Instant FPU!!!).  To actually check hit/miss, the server should have a set of low-poly models, maybe about 300 faces?  (I dont know that much about modeling...)  If something as complex as model-based hit/miss detection is going to be added, you might as well add a full-fledged physics engine...

[kevlarman]

most servers have a a gpu that makes your integrated intel look like a geforce 9800 (if they have one at all that is)