people try and say its a glitch. just admit he is INSANE <3
aka flukeiMPaCT.uK wrote:
people try and say its a glitch. just admit he is INSANE <3
Ho-lee fuck. There was a full 5 seconds from when he fired to when he got the kill.
Ho-lee fuck.
Ho-lee fuck.
I don't understand, you placed a shot, and the film skips a few frames, and then it says you killed him.
Travel time I guess.
on dalian ive sniped someone i could barely see and it took 3+ seconds to show up.No/Yes wrote:
I don't understand, you placed a shot, and the film skips a few frames, and then it says you killed him.
Bullets go 1km (1000m) in bf2, i say you got a bug there
Heres a vid i made with a 955m kill in it, bullet travel time is quite long but yours is even longer, and the bullets only go another 45m on top of that so thats why im guessing its a bug.
Heres a vid i made with a 955m kill in it, bullet travel time is quite long but yours is even longer, and the bullets only go another 45m on top of that so thats why im guessing its a bug.
Last edited by dont_be_ss (2008-02-10 15:33:03)
nice shots
will you teach me to shoot hawk lolz
i spoke to him, it wasnt a bug he actually got hitdont_be_ss wrote:
Bullets go 1km (1000m) in bf2, i say you got a bug there
Heres a vid i made with a 955m kill in it, bullet travel time is quite long but yours is even longer, and the bullets only go another 45m on top of that so thats why im guessing its a bug.
So why was the kill delayed that much? It appears to be ~3 seconds or so. Which is a lot, even in the case of extreme lag.HaawwK wrote:
i spoke to him, it wasnt a bug he actually got hitdont_be_ss wrote:
Bullets go 1km (1000m) in bf2, i say you got a bug there
...
Heres a vid i made with a 955m kill in it, bullet travel time is quite long but yours is even longer, and the bullets only go another 45m on top of that so thats why im guessing its a bug.
Bullets travel at 1000 m/s, max range of 1000m, so 1 second is about the max delay you'll get.
Edit - Besides, you were shooting unscoped... which results in horrible deviation. It's pretty unlikely you'll hit someone at 500+m with that. Trust me, scoped 500-1000m shots are hard enough already.
Last edited by ScoutStrike (2008-02-10 17:21:24)
Because he hit a burning car imo.ScoutStrike wrote:
So why was the kill delayed that much? It appears to be ~3 seconds or so. Which is a lot, even in the case of extreme lag.
So did the guy say he was in a vehicle? Would be a pretty logical explanation. Unlikely still, but hey.TheAussieReaper wrote:
Because he hit a burning car imo.ScoutStrike wrote:
So why was the kill delayed that much? It appears to be ~3 seconds or so. Which is a lot, even in the case of extreme lag.
he said he was getting into the AA gunScoutStrike wrote:
So did the guy say he was in a vehicle? Would be a pretty logical explanation. Unlikely still, but hey.TheAussieReaper wrote:
Because he hit a burning car imo.ScoutStrike wrote:
So why was the kill delayed that much? It appears to be ~3 seconds or so. Which is a lot, even in the case of extreme lag.
How did you get such info on the range/speed of the BF2 bullets?ScoutStrike wrote:
So why was the kill delayed that much? It appears to be ~3 seconds or so. Which is a lot, even in the case of extreme lag.HaawwK wrote:
i spoke to him, it wasnt a bug he actually got hitdont_be_ss wrote:
Bullets go 1km (1000m) in bf2, i say you got a bug there
...
Heres a vid i made with a 955m kill in it, bullet travel time is quite long but yours is even longer, and the bullets only go another 45m on top of that so thats why im guessing its a bug.
Bullets travel at 1000 m/s, max range of 1000m, so 1 second is about the max delay you'll get.
Edit - Besides, you were shooting unscoped... which results in horrible deviation. It's pretty unlikely you'll hit someone at 500+m with that. Trust me, scoped 500-1000m shots are hard enough already.
Do these apply to both unscoped/scoped?
Also; if you fire a sniper rifle round enough times in a random direction, you'll end up with a hit. Out of the 100's of people that play every day, I'm guessing each person will fire off 100 bullets at random (I know my tally is quite close to 1000, I use the MG on the F35 at heights of 1000+ to pass the time) time that by the amount of people playing each day (Hangs around 7000 at any one time, so a rough guess of 25'000 people a day playing BF2)
So that's 2'500'000 random shots every day. I wouldn't be suprised if a shot like this is pulled off every day at least once.
But I thought the stationary AA gun has no critical/burn damage like a jeep does. So how did you get the delayed kill?HaawwK wrote:
he said he was getting into the AA gun
I know the info because I had to change it for my sniper mod. It's the same projectile, either scoped or unscoped, so that doesn't matter. But the firing cone is about 45 degrees unscoped, so at close range you can hit someones stomach while aiming for the head. I'm not saying it's impossible, it's just very unlikely. That AA site is about 700m from the carrier FYI.Hakei wrote:
How did you get such info on the range/speed of the BF2 bullets?
Do these apply to both unscoped/scoped?
Also; if you fire a sniper rifle round enough times in a random direction, you'll end up with a hit. Out of the 100's of people that play every day, I'm guessing each person will fire off 100 bullets at random (I know my tally is quite close to 1000, I use the MG on the F35 at heights of 1000+ to pass the time) time that by the amount of people playing each day (Hangs around 7000 at any one time, so a rough guess of 25'000 people a day playing BF2)
So that's 2'500'000 random shots every day. I wouldn't be suprised if a shot like this is pulled off every day at least once.
In any case, the kill bugs aren't that rare. I got a 'LADDER' kill a few days ago while I didn't even drop a claymore.
Ladder kill? I thought that didn't exist in the BF2 localization files, shows my limit of knowledge --.
Anyway, and yes, it's unlikely. But an unlikely event that has criteria met thousands of times on a daily basis, you just have to wait for someone to get fraps.
I've been on Wake and pulled off shots at the carrier from the north part with a tank, using attack markers.
The shot has been done multiple times whilst scoped, but I think unscoped makes it really quite special .
Anyway, and yes, it's unlikely. But an unlikely event that has criteria met thousands of times on a daily basis, you just have to wait for someone to get fraps.
I've been on Wake and pulled off shots at the carrier from the north part with a tank, using attack markers.
The shot has been done multiple times whilst scoped, but I think unscoped makes it really quite special .
I'd believe it if I saw the battlerecorder of it.
Are yous blind or what. How can you not see the ...[M24]... kill message. if he hit a burning car it would have said [killed] unless he hit the car when it was on about 0.5 bars of health, since for the [M24] message to show up the bullet would have had to destroy the car, not the fire.
anyone trying to prove it wrong is just jealous, even if it was a fluke, its by far the longest sniper kill ever recorded.
+1
also i remember something about sniper bullets in bf2 travelling between 500 - 1000 m/s. so its fair to assume, goin off the video, he hit someone along the eastern ridge of the island at north base i think it is (the NE flag) since that would make perfect sense for the delay in the kill message
anyone trying to prove it wrong is just jealous, even if it was a fluke, its by far the longest sniper kill ever recorded.
+1
also i remember something about sniper bullets in bf2 travelling between 500 - 1000 m/s. so its fair to assume, goin off the video, he hit someone along the eastern ridge of the island at north base i think it is (the NE flag) since that would make perfect sense for the delay in the kill message
Last edited by Djbrown (2008-02-12 05:25:20)
If it wasn't a burn kill then it was a bug, no bullet travels for 5 seconds. And no it isn't the longest sniper kill recorded.Djbrown wrote:
Are yous blind or what. How can you not see the ...[M24]... kill message. if he hit a burning car it would have said [killed] unless he hit the car when it was on about 0.5 bars of health, since for the [M24] message to show up the bullet would have had to destroy the car, not the fire.
anyone trying to prove it wrong is just jealous, even if it was a fluke, its by far the longest sniper kill ever recorded.
+1
also i remember something about sniper bullets in bf2 travelling between 500 - 1000 m/s. so its fair to assume, goin off the video, he hit someone along the eastern ridge of the island at north base i think it is (the NE flag) since that would make perfect sense for the delay in the kill message
i think somebody is a little bit jealous!ScoutStrike wrote:
If it wasn't a burn kill then it was a bug, no bullet travels for 5 seconds. And no it isn't the longest sniper kill recorded.Djbrown wrote:
Are yous blind or what. How can you not see the ...[M24]... kill message. if he hit a burning car it would have said [killed] unless he hit the car when it was on about 0.5 bars of health, since for the [M24] message to show up the bullet would have had to destroy the car, not the fire.
anyone trying to prove it wrong is just jealous, even if it was a fluke, its by far the longest sniper kill ever recorded.
+1
also i remember something about sniper bullets in bf2 travelling between 500 - 1000 m/s. so its fair to assume, goin off the video, he hit someone along the eastern ridge of the island at north base i think it is (the NE flag) since that would make perfect sense for the delay in the kill message
Or he's just trying to explain something. As you said, he was getting into the AA, which is indeed just over 700m. I'm not saying you didn't get a kill at long range, im merely suggesting it may have been a bug. Ive had kills credited after the fact, perhaps you hit him previously and he got some "world" damage via falling etc. Did you record any more of that video, or just that lucky shot?HaawwK wrote:
i think somebody is a little bit jealous!ScoutStrike wrote:
If it wasn't a burn kill then it was a bug, no bullet travels for 5 seconds. And no it isn't the longest sniper kill recorded.Djbrown wrote:
Are yous blind or what. How can you not see the ...[M24]... kill message. if he hit a burning car it would have said [killed] unless he hit the car when it was on about 0.5 bars of health, since for the [M24] message to show up the bullet would have had to destroy the car, not the fire.
anyone trying to prove it wrong is just jealous, even if it was a fluke, its by far the longest sniper kill ever recorded.
+1
also i remember something about sniper bullets in bf2 travelling between 500 - 1000 m/s. so its fair to assume, goin off the video, he hit someone along the eastern ridge of the island at north base i think it is (the NE flag) since that would make perfect sense for the delay in the kill message
Fateless.
Sometimes you can see you killed someone without shooting, but your kill don't count. But it doesn't happen very often.
i was just testing fraps, while flying a jet to see my FPS and then i got that shot.. iv deleted fraps now thoFateless wrote:
Or he's just trying to explain something. As you said, he was getting into the AA, which is indeed just over 700m. I'm not saying you didn't get a kill at long range, im merely suggesting it may have been a bug. Ive had kills credited after the fact, perhaps you hit him previously and he got some "world" damage via falling etc. Did you record any more of that video, or just that lucky shot?HaawwK wrote:
i think somebody is a little bit jealous!ScoutStrike wrote:
If it wasn't a burn kill then it was a bug, no bullet travels for 5 seconds. And no it isn't the longest sniper kill recorded.
Fateless.
Ok, it wasn't a "pure" shot hitting the guy itself. The travel time was close to 5.5 seconds (used stopwatch). The formula to calculate bullet travel time (in seconds) is: t = Distance (meters) / 1000. So, taking 5.5 seconds multiplied by 1000 you would get that the target is 5500 meters away, which as everyone knows, is further than any AA gun. I got the formula to calculate the distance from here:
I took the picture from here.
Alright, one explanation could be that the guy who got shot was driving a car at the AA and the car got hit by Haawwk's M24 bullet and exploded. This would explain the enormous interval between the shot and the kill and give an explanation why the killed player insisted he was trying to get into AA.
Just something I quickly came up with since that shot just didn't seem all that genuine, but still an insane shot indeed
I took the picture from here.
Alright, one explanation could be that the guy who got shot was driving a car at the AA and the car got hit by Haawwk's M24 bullet and exploded. This would explain the enormous interval between the shot and the kill and give an explanation why the killed player insisted he was trying to get into AA.
Just something I quickly came up with since that shot just didn't seem all that genuine, but still an insane shot indeed