In my experience, the C4 is the same as every other weapon in every other FPS to date. It takes time to switch to it, and it takes time to switch to it's secondary function.
Just like using the default assault gun and switching to the grenade-launching function, it's not instantaneous. It's realistic. You can't expect your spec ops guy to reach into his little belt, undo the velcro strap, make sure he's far enough away, all in the heat of battle, in under a second.
"Why's he throw another one then?" you ask. Well I think if it were me, I'd fumble the ball in that situation too.
Tbh though, I've never had him "drop another C4", or "drop a fake one". But then, that's because I've considered that "glitch" to simply be the game carrying out the current weapon's function before it has fully switched to the secondary function.
Again, I don't know anything about this "fake C4" issue. But just like most other games if you give it commands while it's not listening (i.e. during the switching process) something's bound to go wrong. You just have to get the timing down.
I don't know if this applies here too much, but the best example I can think of is in Valve's source games, and even their previous games, when you run, or especially when you go prone, the game doesn't let you use your gun until you are settled on the ground. It takes practice and a skillful operator to learn the timings and know when to fire to get the quickest possible accurate response. If you can't do it right, then 1) get killed, or 2) don't do it.
Last edited by Roachy (2006-01-29 15:41:37)