shooting and no death

[imded]

1. Sorry couldnt put this in the bug report section. Keeps coming up not logged in. <<

2. Yesterday, I am britt and using SMG. Shot ei that had a rifle. Saw blood spatter

and all. He did not die (he was busy killing someone else at the time).

So, I reloaded and emptied another clip into him. He finally died.

This has happened to many of my squad mates too.

Major problem here. If it requires many rounds to kill, which gives and unfair

advantage to the enemy as they can turn and kill you with a single shot. Which has happened.

Some of my squadies I can hear them shoot at ei and have to rinse and

repeat many times with a rifle to accomplish the task at hand. Each round

was a hit btw. Blood spatter and all.

[xohorvath]

This annoying. I expect it to happen.

I remember a couple years ago one of the "pros" suggested the best way to play was to shoot your target and move on immediately. The problem is, one can shoot their target and move on, only to have them shoot you in the back. =)

So, having played this for years I assume it will happen and take it into account. Yesterday though, the 17th, I experienced more than I ever have. I had one sortie alone where four were shot, blood splattering, but they kept walking. I simply moved on.

What can you do?

I know the powers to be know about this, they have to. Thus, I trust they are working on it.

[snappled]

Seen this bug several times now ... best security (until fixed) is just as in the real world; Fire until the threat is gone.

S!

[Lob12]

Yeah this is happening to me too.

Shooting EIs and not seeing them drop before a long 5 seconds.

Server in general has been *****y. Lots of off set bugs and falling-through-stairs

Edited November 18, 2014 by Lob12

[company0]

Oh this is nothing.

Bout two days back, I had my tank flamed, dinking and gunner killed. But the tank didn't proceed to blow up. Instead, it was invulnerable and I was able to drive around, using the commander as a sighter since the driver was blinded by the flames.

Some weird stuff going on in-game.

[skers]

I've been seeing similar things in game. Had an ei enter a CP I was guarding Saturday night. The first 5 to 7 rounds hit him but just registered as white puffs...like I was hitting a wall. I kept firing and eventually I saw blood splatter and he went down. It took most of the magazine.

Engagement range was about 5 meters.

I've seen some tanks that got sapped recently that displayed the brewing up/burning animation BUT the main gun and coax MG were still functioning just fine. The tank was able to operate like that for a few minutes and then it blew up.

I'm getting more and more engagements where it takes 2, 3 or 4 rifle rounds to drop an ei. I see blood splatters on each hit but that ei continues to move about like nothing happened. The most common action I am seeing is the two shot rifle kill. First shot draws blood and the ei continues to move. Second shot draws blood and the ei continues to move and then suddenly drops/dies. The thing I noticed in the majority of the instances where this happens is that I was not given a kill credit. Just a damage credit.

Edited November 18, 2014 by skers

[MikeAZ]

1. Sorry couldnt put this in the bug report section. Keeps coming up not logged in. <<

2. Yesterday, I am britt and using SMG. Shot ei that had a rifle. Saw blood spatter

and all. He did not die (he was busy killing someone else at the time).

So, I reloaded and emptied another clip into him. He finally died.

This has happened to many of my squad mates too.

Major problem here. If it requires many rounds to kill, which gives and unfair

advantage to the enemy as they can turn and kill you with a single shot. Which has happened.

Some of my squadies I can hear them shoot at ei and have to rinse and

repeat many times with a rifle to accomplish the task at hand. Each round

was a hit btw. Blood spatter and all.

you don't live in ferguson,mo do you?

[frogdeth]

This has been a day-one problem.

Problem is, in reality, a lack of queue-kill coding in the game itself. I've pointed this out many times to no avail. That and a combination of client-side damage acknowledgement opens up a world of exploits that, to the surprise of no one, many players have embraced like a religion.

Because of this lack of proper programming, these people have found numerous ways to exploit lag to their advantage, and what you're seeing is one of them. If someone can drop their bandwidth enough then they will have plenty of time to get revenge on someone who has already killed them because they've forced their machine to not accept the "you're dead" message.

[wockawocka]

Seen many games that allow a player with dropped internet packets to get an advantage... Hate it. And at the same time BGE is not entirely a lost cause. Because often when I shoot, and do not get kill, I still get the kill in the stats. Meaning somewhere my kill was registered, so somewhere in the BGE-system it works.

Another problem is (and this is visible last campaigns) that kill ratio is over 1.0 if you merge both sides. And I do not think this is due to people running around with satchels...

Network code should check for lost packages, and "punish" the ones showing it. Many good games have rules that slow players up, that show lost packages, preventing warping, and where kills from lagging player is ignored.

In the case of BGE, code from the servers must be able to override what the clients are reporting. This would still cause a "delay" in a lagged players death, but rather that a player finally dies, that not at all.

Not saying this is an easy fix, but would be nice to see this "principle" of making punishing code for laggers in BGE. More and more people are using wireless networks when playing, and maybe nothing has changed in code, but this. So time to deal with it.

[GOPHUR]

1. Sorry couldnt put this in the bug report section. Keeps coming up not logged in. <<

2. Yesterday, I am britt and using SMG. Shot ei that had a rifle. Saw blood spatter

and all. He did not die (he was busy killing someone else at the time).

So, I reloaded and emptied another clip into him. He finally died.

This has happened to many of my squad mates too.

Major problem here. If it requires many rounds to kill, which gives and unfair

advantage to the enemy as they can turn and kill you with a single shot. Which has happened.

Some of my squadies I can hear them shoot at ei and have to rinse and

repeat many times with a rifle to accomplish the task at hand. Each round

was a hit btw. Blood spatter and all.

What was your ping at the time? One of you was having a poor connection I would bet. The game will kick you if responses get too long in the tooth sounds like one or both of you were on the edge. Who was it do you know?

[snappled]

I have some pics .. in the Tienen CP in Leuven during C103 I believe. German rifle laying on the ground aiming at the top of the stairs ... he is at my feet with blood spattering up out of his back as one, then a second, third, and fourth full french SMG clip are emptied into him.

It was with the help of three other Allies and one more full clip that he finally took his last breath.

110FPS. 80(83-85)ms shows in all frames.

It may be possible that he was bleeding because he fell off of his bicycle before running into the CP, and that all 150 rounds I fired actually missed. It is possible.

S!

[snappled]

Edited November 19, 2014 by snappled

[MikeAZ]

me and another guy unloaded4 clips into a anti tank rifleman point blank range no kill.altho it did register as a hit.

[GOPHUR]

I have some pics .. in the Tienen CP in Leuven during C103 I believe. German rifle laying on the ground aiming at the top of the stairs ... he is at my feet with blood spattering up out of his back as one, then a second, third, and fourth full french SMG clip are emptied into him.

It was with the help of three other Allies and one more full clip that he finally took his last breath.

110FPS. 80(83-85)ms shows in all frames.

It may be possible that he was bleeding because he fell off of his bicycle before running into the CP, and that all 150 rounds I fired actually missed. It is possible.

S!

Blood means your client detected a hit or someone told you about a hit it doesn;t mean that that information made it to the target.

[Merlin51]

on the flip side, the other guy sees this

Oooh EI BAM BAM yea got him

walks away

POOF

wtf? im dead?

mind you he was dead 800ms ago, he just didnt know it

hard to do an MMO that is real time FPS mechanics

quake, your ping sucks, you simply die a lot and you find a lower latency server, not so in an MMO

same thing happens with all units but infantry are the quickest and most twitchy and so readily noticeable

[GOPHUR]

That's what i suspect too Merlin.