Speaking of "enhancements"

[AKWarp]

Ok, since everyone seems to want something, I'll post my "I want" list...

It's pretty simple, and not very long:

1.  FIX THE GV'S!!  - There is definitely something awry with the hit/kill/damage thing with GV's.  I consistently have to hit, say another panzer with AP from my panzer 8, 10, 12 or more times to get a kill.  I get popped once or twice and it's over.  

I think it is a connection related issue (and NOT a "where you hit them" issue as HT told me in the past).  I have, on very rare occasion, managed one hit kills on other tanks, and I have noticed that when I do, I can get one hit kills on that same person the rest of the evening (if I should run into them again).  Unfortunately, this is quite the exception and not the rule.

Also, the tiger tanks have some real issues as well.  I rarely drive the thing anymore because panzers kill me with 1-2 hits.  Tiger vs tiger I lose nearly every time because, although I hit the other guy 5-6 times, he hits me 1-2 times and I die.  This is consistent.

GV's need some work for sure.

2.  Collision modeling - I know this one rears its head from time to time, but seriously, a collision is a collision.  In a pair of aircraft with a combined closure rate over 500MPH, both should go down in a collision...period.  I know, I know, only one FE registers a collision, I know because it's 99.99% of the time MY FE that registers it.  Again, is this a connection issue?  If one FE registers a collision, the other one should be signalled and both planes should go down.  Yes, it might suck for the guy that supposedly "didn't see it on his end", but the bottom line is, this will certainly affect how some people dogfight and/or HO others.  Close is one thing, rampant "bumper cars" is another.  

I have some issues with the speeds and abilities of some planes, but I don't suspect those are gonna change much, so will just learn to deal with them.  Won't even touch the bomb sight thing, I just don't bomb anymore, problem solved.

[whels]

Originally posted by AKWarp
Ok, since everyone seems to want something, I'll post my "I want" list...

2.  Collision modeling - I know this one rears its head from time to time, but seriously, a collision is a collision.  In a pair of aircraft with a combined closure rate over 500MPH, both should go down in a collision...period.  I know, I know, only one FE registers a collision, I know because it's 99.99% of the time MY FE that registers it.  Again, is this a connection issue?  If one FE registers a collision, the other one should be signalled and both planes should go down.  Yes, it might suck for the guy that supposedly "didn't see it on his end", but the bottom line is, this will certainly affect how some people dogfight and/or HO others.  Close is one thing, rampant "bumper cars" is another.  

 

ive never understood why we can shoot at a enemy where we see them on our FE and hit them and do damage to them, but same situation, u  fly through them, u will get damage and die, but they can fly off un hurt.

now either they are really where i see them (they are for guns) or they arent( collision).

collisions need to be, check both FEs  1 yes 1 no = no collision both unhurt,  2yes = collision and both get damage/die.

whels

[AKWarp]

Whels, I like that idea a lot, but I have never personally witnessed a mutual collision death in AH.  Not saying it has never or doesn't happen, just never seen it.

I point this out because I suspect that if it is set up as you suggest, we may never, or very, very rarely ever see a collision death (assuming that a mutual collision is recognized).  

The downside here is that it will take all of about 30 seconds for everyone in AH to realize that collision deaths are very rare and the odds are in your favor to play HO/RAM guy because chances are good you're gonna get away with it.

Either way, I'm willing to try SOMETHING along this line, if for nothing more than to see how it all plays out online.  

Even if we tried the 1 FE sees collision, both die, it'll still pan out I think because it still requires a pretty darn close proximity for a collision to register.  Folks would just have to learn to be a little more in control or suffer collision deaths.

[Stang]

The collision model is something that gets to me too.  The worst is when a guy collides w/ me from my 6... he can hit me w/ his guns, yet somehow manages to fly into my 6.  The result is I die, he flies off unscathed.  And I have filmed this many times and watched it, most times the guys isn't even firing when it happens so I know it is a collision.  But he flies into me, yet I die.  Somehow that just doesn't make sense w/ the way collsions seem to work in here.  I agree Whels, if one hits they both hit and should go down.

[Flittt]

Stand, in your instance, when you see him hit you he is still 300 to 400 away from you in his view.
"things in the mirror are closer then they apeer"

[Stang]

Flitt in that reasoning he would already be past me by that distance, not behind me.

[Pongo]

Vehicles are truely porked.
3 or 4 hits on the rear of a Panver IV from my panzer iv from under 100 yards and he slowly traverses and kills me with one hit.
I had time to hit the turrent and the hull mulitple times.
This kind of thing seems routine

[Stang]

Yeah I agree Pongo the damage model on gv's is totally inconsistent, and lately I have been shooting through people from point blank.  That's one I haven't seen before.

[Tilt]

Re collisions

I think the Mutual Assured Destruction principle is the best fix.

It may drastically reduce collisions actually occurring at all thru error (eg two curving tragectories will rarely show collision on both FE's)

Re differential hardness in GV's.............. it seems to me that if two FE's report hits in the same place upon their targets then the only way one target can survive better than another is thru a connectivity error.

The interesting point here is one raised by Urchin.....

You fire a HE round or drop a bomb which lands adjacent to, but not hitting, a vehicle.  

The location of the hit point is an exact co ordinate which is reported from your FE via server to everyone elses FE.

With this (I think) comes an incremental damage report on the GV local to the impact point which is taken by the GV's FE and added to his damage tally.

However the location of the GV is not an exact co ordinate.... it varies thru lag when the vehicle is moving. So other FE's will see the GV at varying distances from the impact point at the time of apparant impact.


Having said that its obviously possible that there can be spots of vulnerability (as per the MkIV Cupula bug now fixed) but this will be on both GV's.

I think the biggest incongruity I find with MKIV's are their vulnerability to 20mm airborne cannon fire. Its clear that should some how several shells pound the same sq inch then eventually some penetrative damage will be incurred. However I would argue that from airborne fire this is very unlikely........... yet we see after several passes that the cupula and its main gun can often be disabled by 20mm if not 12mm on some occasions.

[BenDover]

Does anyone else seem to see tigers' turrets and track to keep getting taken out by m16s?

[Tilt]

Originally posted by Stang
Flitt in that reasoning he would already be past me by that distance, not behind me.

true...... (on his FE) he passed by you micro seconds before (on your FE) you  collided .

Hence, in real time the FE showing the collision is always the one that interfered with another flight path that has already occurred elswhere.

However I must say that I have never........ ever survived flying thru a bomber from any where near the rear........... even at massive differential speeds

I have (once accidentally) successfully flown across the nose of a fighter to have him incurr a collision that never showed to my FE.

[MANDOBLE]

AKWarp. I agree with you, and I'm sure both problems are connection related issues. Some time ago we did several tests, the most representative were these:
1 - 199ms ping cnx plane against the same model with 500ms cnx. The result was that the first plane outran easily the second one, but BOTH read the same speed at instruments.
2 - a 800 ping cnx with LOTS of spikes in netstatus against a 199 ping, flat net status plane. The result was the first plane doing 400 mph, but the second one overpassing it at 200mph and looping several times around him.

[cantrell]

What does "FE" mean?

[BenDover]

Front End, Client, YOU

[fffreeze220]

The points u dpeaking about are comparable the "shot in the toe and get a kill" in counter strike.
Some things will never change.
And since i accpeted the AH is an arcade shooter i am feeling better.
I am pretty sure we wont see any updates before AH2 hit market.
GV modelling is a joke in AH and i really cant see why people drive the randomizer machines. U have more luck in Las Vegas.