[Naked Assassin (old)]

Quote

I agree with his feelings : Stating 3.7 hitcode is fine and justifying the unhit with 'bad servers and msn/irc can affect hits' is so silly...

Normally when someone is unhit yes, you are unhit too (server load/bandwidth issues) but some guys are reliabily unhit, I mean on almost every server, every day, etc etc so there must be something wrong with hitcode in relation to cvars or particular connection characteristics (pl/pt connections for example =))..

Not considering when you try to hit someone not moving from his side in the head...You can even fire everything you have and you won't hit If you dont aim at the neck. Please tell me this is a load or bandwidth issue, maybe I have a mouse eating my ADSL line

MSN has advertising which changes every so often contained in the program. It also sends usage stats and obviously has to tell the MSN network that you are online, and scan for 'buddies' to come online.  IRC is much the same, as is any program which uses the net connection when it is open. 

http://forum.mess.be...p?showtopic=721

If you can offer me an proper technical explanation about how these would not affect people playing online (especially those on low bandwidth connections) then I would love to see it.

[Woekele]

IRC takes really really really low bandwith, and has no spyware, like MSN So I wouldnt count IRC, but I would count MSN.

[mitsubishi]

even if you count nothing, the assumption a connection between any gamer and a server is always 'clean' if no other programs are running is wrong.

[Mobab (old)]

For me, it's not too much about the hit detection itself (except when people are climbing ladders...).  It seems more like their settings vs server vs your settings.

It's strange because occasionally the hit detection works so well that I go "holy shit, I'm hitting them"!  Then try to shoot the next guy 10 seconds later and every last shot misses him.  I could aim in front of him as he runs perpendicular to me and I'd see my bullets appear behind him.  Sometimes it appears where he's at, only after he moved away as if the server held my bullet, he moved, then did the trace to hit.

Don't tell me that it may be lag and i should turn on the lagometer because it's *always* on.  I see no point in turning it off except to clear up some areas.  BTW that's another reason why I like quake, you get a lagometer.

Anyways, after you play for a long time, you can start to notice when the hit detection is doing remarkably well, when it's just doing its job, and when it fails.

My credentials?
None, I'm a noob 

[FragginNewby (old)]

Quote

My credentials?
None, I'm a noob 

LOL... been so long since I've seen you, people might actually believe that.  For those that don't know, Mobab is one of those players I quietly cursed as a hacker whenever he owned my ass on a server.

BTW, I think there are some significant problems with the hit detection, whether simply internet related or multiple programmers modifying it and something getting lost in the translation... I'm glad to hear it's apparently been rewritten and hope it makes the game feel right.

[FS BladeKiller]

TwentySeven has explained all this in various posts on the forum. A search might find some of them. One thing to watch for is server overload seen as yellow triangles in the upper part of the lagometer/netgraph. Watch for your green section to be smooth and adjust ut_timenudge +10 for every pixel the green is off by up to 50. Ut_timenudge only affects the client. There is a bug in Q3's clock that requires the server be rebooted every few days.  Running high fps causes packet loss and lag but gamers insist on 200 fps. It is much better to lock max fps on 76. The hit detection (not the net code) is completely new due to the new models. The hit mesh matches the model's animations, too. There is so much more to this subject so search for TwentySeven's posts on it.

[Mobab (old)]

Quote

Quote

My credentials?
None, I'm a noob 

LOL... been so long since I've seen you, people might actually believe that.  For those that don't know, Mobab is one of those players I quietly cursed as a hacker whenever he owned my ass on a server.

BTW, I think there are some significant problems with the hit detection, whether simply internet related or multiple programmers modifying it and something getting lost in the translation... I'm glad to hear it's apparently been rewritten and hope it makes the game feel right.

I've been cursing at some people, myself lately.

I'll try bladekiller's guide.  It's weird that you start to figure out who you're shooting at just by the way you are hitting/not hitting the guy.  you don't even have to look at the name. 

[p4*xfact0r]

Quote

It's weird that you start to figure out who you're shooting at just by the way you are hitting/not hitting the guy.  you don't even have to look at the name. 

Yap, so much easier to pop the console and:
damn PT/PL f**c!!

[IonYz (old)]

I think hit detection, as it stands, is fine. I've had instances where I empty a whole PSG clip into a guys head at 75 meters and nothing. But I wasn't looking at my net connection so I can't just blame the hit code for it. Like it urks me when someone yells "camper!" or "lag!". Why should I care if your lagging? 

But all this 3.8 talk has my clan and I back into the game. Can't wait to play it.

[JKarmack (old)]

I've been hassling with hit detection problems for a long time. In LANs I have no problems. But on the Internet, don't laugh, the lower my ping (20-50) the worse the hit detection gets (I have a near perfect lagometer). When I play overseas (ping around 120-160)
I can hit so much better (even with SR8). I used to play with a fps fixed at 125 and it was impossible for me to play. Now set to
85 fps which is better but still have the above described problems. Go figure...