Wtf?

[AWwrgwy]

WTF is shratnal?

It's youtube and google's fault.
It actually gets search hits.


Eventually someone is going to have to post the "collision explanation" picture again.



wrongway

[stickpig]

Mustang may have had tracers off so that's why you don't think he fired.
He also may have been anticipating you to move, so with the speed he was carrying he might not have expected you to be there at that moment.

He might have figured he would blow you up, and his aim was so bad that once he committed himself to that course of action and you didn't blow up it was too late for him to move.

Doesn't sound intentional

[Cthulhu]

Eventually someone is going to have to post the "collision explanation" picture again.
wrongway

I recall Lusche having a great explanation, but he must be getting Damn Sick of doing it over and over and over...

[frank3]

Mustang may have had tracers off so that's why you don't think he fired.
He also may have been anticipating you to move, so with the speed he was carrying he might not have expected you to be there at that moment.

He might have figured he would blow you up, and his aim was so bad that once he committed himself to that course of action and you didn't blow up it was too late for him to move.

Doesn't sound intentional

Or he was out of ammo and knew exactly how the collision-modell works

[chewiex]

I Say

IF YOU COLLIDE YOU BOTH DIE

That should be the next collision model


 

+10 Agreed!

 Thats only fair. How many "real world" A/C collide and both don't go down? I'm sure there is a few, but seriously, if there is a collision, then BOTH should die. If one is firing at the time of collision, then give them the kill, but, kill them both. That might reduce the actual "ace pilots" as its put.

[Lusche]

+10 Agreed!

 Thats only fair. How many "real world" A/C collide and both don't go down? I'm sure there is a few, but seriously, if there is a collision, then BOTH should die. If one is firing at the time of collision, then give them the kill, but, kill them both. That might reduce the actual "ace pilots" as its put.

Actually it would have the opposite effect: Ramming would increase, as it

a) would work guaranteed all the time and
b) the rammed can't even dodge it - enemy would fly by at 100ft distance on your screen and suddenly you would go "boom" from a collision that never happened on your screen.

[Cthulhu]

+10 Agreed!

 Thats only fair. How many "real world" A/C collide and both don't go down? I'm sure there is a few, but seriously, if there is a collision, then BOTH should die. If one is firing at the time of collision, then give them the kill, but, kill them both. That might reduce the actual "ace pilots" as its put.

It's amazing how many people still don't have a clue what's actually going on in an AH collision. No wonder Lusche gets tired of explaining it.

[Lusche]

It's amazing how many people still don't have a clue what's actually going on in an AH collision. No wonder Lusche gets tired of explaining it.

I'm just thinking it's Bronk's turn this time... 

[The Fugitive]

I think HTC should make a new arena with "both go down in a collision" enabled. Then after a few times of these guys plane exploding for no reason they might start getting the idea. Imagine the out cry !!! "My plane blew up and the only contact was a pony 1k out ! "  LOL!!

[Cthulhu]

I think HTC should make a new arena with "both go down in a collision" enabled. Then after a few times of these guys plane exploding for no reason they might start getting the idea. Imagine the out cry !!! "My plane blew up and the only contact was a pony 1k out ! "  LOL!!

To be fair, let's turn it on for GV's as well. GV vs GV should be ok, but any plane that got within 1K of a GV would just explode! Think of the camping possibilities.

I can just see the system message now:

"dr7 was AFK for 4 days and landed 465 kills in a Panzer IV"

[Sincraft]

But if they fix the collision/prediction code, the spit16 will no longer be dweebish.  For those that do not understand this, wait to see the difference after they fix this lol...it will NOT be the same.

S

[Cajunn]

He SHOT you three times and collided as well.  You know you can lose non-vital parts in collisions?  Losing an elevator or rudder usually don't cause a plane to smoke.

I would guess that 92.4% of the time a "collision" results in a kill, they were shooting at you.

And, SPIKES, you collided with him, he didn't collide with you.   

I've had people collide with me, white message, and not get a kill before because they fell out of proxy range before they hit the ground.

Just out of curiosity SPIKES, I know you died, did he get the kill?


wrongway

Don't know who spikes is this is Cajunn, And it was a white message not the orange one, and he got all three kills on me.


Sorry thought you were talking to me

[Tec]

if there is a collision, then BOTH should die.   That might reduce the actual "ace pilots" as its put.

No, that would increase the ace pilots.

[Tr1gg22]

For the record: The only way to have no lag is not to be connected to the internet.

And how do you now he "purposedly" collided with you?

And last... You didn't feel like maneuvering yet you are complaining about going down? 

[Knite]

I never ceases to amaze me how something that's been explained over and over and over again, with visual aids even, still continues to baffle so many people.


Two computers did not see their planes collide.
Only one did.
And that one went down.


To give it math...
if a plane is going 200mph, it is moving at 293 feet per SECOND.
A lag of 50ms (still a very, very good internet connection), still means There's at least 14 feet difference between what you see, and where you actually are.
If the other person's lag is 100ms (still not a bad internet connection), they are 28 feet between what they see and where they actually are.
That's a 42 feet difference in where you two see where you are, and where your planes actually are.
When you're talking about aircraft who's length and wingspan are almost always under 40 feet... you're talking 1 entire plane away.
This is overly simplistic, and honestly, a "best case" scenario.

In other words, they did not collide with you. Period.
You did, however, collide with where your computer thought they were, a whole 40+ feet away from where they thought they were.