Collisions

[Vermillion]

Hristo

I was making what is commonly called a SWAG   Or Scientific Wild bellybutton Guess  

Only Pyro or HT could tell you exactly what is going on.


------------------
Vermillion
WB's: (verm--), **MOL**, Men of Leisure,
"Real men fly Radials, Nancy Boys fly Spitfires "

[TT]

 In ver. .43 I have noticed a large increase in being rammed and attemped rams. This is especilly true, if you are in a 109. Dweebs in spits and other more agele planes know that they can pull out and you cant.

 IMHO if the last man standing rule was dropped. It would dicourge this.

[This message has been edited by TT (edited 01-01-2000).]

[Sorrow[S=A]]

I am sorry hristo but _I_ have to disagree with you.
Whether it's on your FE or mine does not matter, if there is a collision than both sides should be damaged. If there is a touch then both planes need to reflect that or collisions are just unfair. To this point I have NOT seen a collision I have had inflict damage on the other plane. When I accidently collide with a plane then dammit I want him to be having some issues too while I am wingless and in a spin.
 In all my touches I am pretty sure that the hit was on his FE or just because of the "bubble" effect you described. Therefore netlag is besides the point. If there is a collision then bygod let both planes see damage.

------------------
If your in range, so is the enemy.

[LLv34_Snefens]

Agree 100% Sorrow.
Both should get damaged if just one of them observes a collision.
The argument about not feeling the collision if you don't see it from your point of view and being unable to avoid the collision don't hold. Should bullet hits also be neglected just because they don't seem to hit and you didn't have a chance to avoid them either?

Having said this I agree that this discussion wouldn't occur if lag the size it is in AH. I often notice how long it takes from the collision or the massive amount of hits taken, before the effect is seen.
Often it feels like there is about a ½ to 1 sec delay. Just tonight I ran straight through a F4 in my 109. Clearly a collision, but it took about one second before parts started falling off me one by one in fast order.

A little tip I have learned is that the danger zone for the "invicible" collisions is right in front of the enemy's flight path. As he sees your plane "delayed" it can come to a collision in his view.
 
In short, let the collision model stay, and concentrate on the lag-issue.

------------------
LLv34 Snefens
RO, Lentolaivue 34

[Minotaur]

Hristo;

Thanks for the pictures, you illustrate your arguements very well. <S>

HTC;

Check out the last picture that Hristo posted.  The picture with the P-51 that has its wings missing.  

Now.....   Put the wings back on.  Change the color of the flames slightly, more whitish.  Reduce the flame size by 50%.  Add a little more transperent smoke trailing behind the flames.  Move the flames forward on the A/C so that it centers over the engine exhaust stacks.  Make 6 little defined puffs on each side of the fuseluge.  Transpose this modified picture and place it in the air over an air base.  Then send the completed picture to me, as a desktop wallpaper.    

  Thanks   in   advance  

Mino

[This message has been edited by Minotaur (edited 01-02-2000).]

[Hristo]

Minotaur and Snefens,

You did not convince me   Yes, I see your point and it would be valid indeed if we would not have netlag.

However, sometimes netlag causes great differences what players see. The greatest difference I saw is Spit hitting me at d12 on my FE. I asked him how far away he was on open channel, he said it was d8. That covers difference of 301-499 yards.

Now, what if we scissored ? If I saw him 400 yards away ? Collision wouldbe the last thing I would think of. Would it be fair for me to get damaged then, if he, due to his netlag and different situation on his FE, collides with me ?

Anyway, I just wanted to point out that collision detection code needs reexamination. As for collision politics  , I think it is fair.

[Westy]

 Bull. Collisions as fine just as they are. I do not want to get penalized because someone can't fly thier aircraft hits me or is out of ammo but 'just has to' get that kill no matter what so they purposely collide.
 
You collide? YOU go down. Not me.

-Westy

[eskimo]

I have yet to colide when I didn't expect it.  I have missed a few colisions that I thought were too close to call.  This collision code rules!
eskimo

[This message has been edited by eskimo (edited 01-07-2000).]

[Hristo]

In latest versions (0.44) I have goen through similar situations, very close, did not collide. Seems the collision detection has been imrproved, but I need time to make sure