Yes i have noticed this also, not a whole lot but it has happen to me before too.

Happens all the time D:

Can you test this with cl_autoreload 0 to see if thats part of the problem

confirmed this bug but need to find cause... need to remember to try autoreload 0

i always thought since i died instantly by a sniper it just felt longer to respawn. lol

nah, happened when i got killed point blank with a shotgun yesterday ;/

Before now I just kinda accepted that I didn't always spawn straight away. Didn't even consider it a bug - wierd.

I've noticed this too and yeah just kinda passed it off as general annoyance. But thinking on it it would make since that it's a bug lol. I guess we'll all just have to try and pay attn to when this is happening and what your doing moments before.

yeah. well its only now it's in the forefront of my mind that I'll start realising what does it.. just like grenade spam issue making you drop the conc (which should be fixed too)

I think this one, that one ^^ and the SG nail bug ones are actually quite important ones to sort out but probably the hardest to find the cause out :p

Is this issue still being looked into or has been fixed?

Hmm. I remember doing lots of experiments with someone about this very bug...

I'm sure I noted it on a forum post somewhere and I don't know if it was fixed. It was to do with prediction or something like that. It only happened when being killed by weapons that were predicted (or not predicted - I forget).

It still happens frequently in current FF.

Happens to me maybe once a day. Was just about to say something. Also you mentioned something about concs dropping in an unrelated bug. That happens to me. and it really should because I have double tap grenades, and pretty fresh keys that don't stick. You related it to grenade spam but it usually happens to my spawn concs.

A guess at the spawn gren problem would be:

-> You die and press grenade button and fire button at the same time
-> Client sees grenade button then fire. Assumes you are not allowed to prime a grenade since you are dead.
-> Packets from your client saying what you pressed are sent to the server.
-> Packets from the client take different routes across the network and arrive in the wrong order
-> Server sees you pressing fire first, THEN pressing grenade
-> Client incorrectly predicts that the grenade is not primed, server primes your grenade.

This is assuming that packets aren't timestamped or framestamped, or maybe pressing fire and grenade in the same frame causes issues.. I'm unsure exactly how source engine handles this.

This is now the most annoying non-class specific bug in the game, fyi. :D

I'd like to help squash this bug. What can I do to test it further? Yesterday I was playing and got killed by a super shotgun blast. It took a good 5 seconds for me to respawn. D:

I've been chasing this one for a while to be honest. out of curiousity, anyone have a short demo where it happens?

I do not, but I'll record something tonight and see if I can replicate it.

Seems like it happens only with hitscan weapons. If killed with an RPG or grenade, it spawns me instantly.

I'm sure I tracked this already and found it was lag predicted stuff.

Here's a demo of it anyway: mildsclan.com/FF/demoooo.dem

I got it to replicate near the end of the video after the guy who helped test went pyro and killed me with flamethrower.

If it is based on lag predicted stuff, is there a way to fix it going forward?

doh, ok!

not easily, that stuff is terribly complex. i tried to revamp the nade stuff and it was a nightmare