No kill credit after/during despawn.

[Tigger6]

It seems that there is yet another kill credit bug around.

What was reported by squadmates is that they have died in a head-on ram where both sides plinked each other and both sides blew up, but they did not get a kill credit scored against them.

This is probably a issue with the other player despawning a split second earlier. I had similar experience two days ago.

I forced conqueri to ditch (after doing considerable damage to him, I was there alone). And I lawndarted just by him and blew up. No kill awarded.

Note that my game died upon pressing the despawn button. Here are the missions: http://csr.wwiionline.com/scripts/services/persona/sortie.jsp?sid=2556535&pid=336602&page=1

http://csr.wwiionline.com/scripts/services/persona/sortie.jsp?sid=2550057&pid=657153&page=1

I suppose the issue is with the "new" kills not being awarded properly if the enemy is no longer spawned in, as the "old" kills are. If this is a feature rather than a bug, I would propose it gets re-evaluated.

Edited October 22, 2010 by Tigger6

[Tigger6]

Seems this is actually a "kill not awarded for ditched EA" bug report. Similar case today, but this time I lived, EA ditched. Missions in question:

http://csr.wwiionline.com/scripts/services/persona/sortie.jsp?sid=2663407&pid=657153

http://csr.wwiionline.com/scripts/services/persona/sortie.jsp?sid=2668483&pid=674543

[Tigger6]

http://csr.wwiionline.com/scripts/services/persona/sortie.jsp?sid=2720104&pid=657153&page=1

Plinked, ditched, despawned. (all in less than 30s) No killer.

[bersi]

http://csr.wwiionline.com/scripts/services/persona/sortie.jsp?sid=2720104&pid=657153&page=1

Plinked, ditched, despawned. (all in less than 30s) No killer.

stats are locked

[Tigger6]

stats are locked

Rats can read them. I'll unlock them when they implement not showing up on top100.

[swoop]

since 1.31 my screen freezes sometimes as i despawn on the ground or bail out, i then ctd then mission results pending bug, then shows an rtb?, my plane has been damaged critically tail missing or engine out aswell. commiserations to the guys whove been robbed this way.

[Tigger6]

since 1.31 my screen freezes sometimes as i despawn on the ground or bail out' date=' i then ctd then mission results pending bug, then shows an rtb?, my plane has been damaged critically tail missing or engine out aswell. commiserations to the guys whove been robbed this way.[/quote']

Interesting. This goes along with what I saw earlier:

Shot at a 109, he bailed (even before I hit him), airplane disappeared 1 second later.

[GOPHUR]

This is really hard for me to test today especially since I am so behind so I want you to validate that this is what you are seeing.

• attacker and target are both planes
  
• attacker plinks target
  
• target suffers no critical damage
  
• attacker crashes first
  
• target crashes secons
  
• attacker sees what in his AAR?
  
• does this match attackers CSR?
  

Expected functionality:

• target awards kill on despawn so...
  
• attacker will not see aq kill on his AAR until after the target despawns
  
• But you're saying it never appears in CSR?
  

[Tigger6]

This is really hard for me to test today especially since I am so behind so I want you to validate that this is what you are seeing.

• attacker and target are both planes

• attacker plinks target

• target suffers no critical damage

• attacker crashes first

• target crashes secons

• attacker sees what in his AAR?

• does this match attackers CSR?

Expected functionality:

• target awards kill on despawn so...

• attacker will not see aq kill on his AAR until after the target despawns

• But you're saying it never appears in CSR?

It is more general than that. This was my first bug report, I thought it was caused by me crashing (and the game crashing upon hitting escape) before the enemy spawned out. (He was already crashed though).

However, subsequent encounters showed 2 cases:

A)

• attacker and target are both planes

• attacker plinks target

• target suffers no critical damage

• target ditches and despawns within seconds of receiving damage

• no kill in AAR of attacker

• no kill in AAR despawned

• MIA/RES in AAR despawned

• CSR matches this

• attacker and target are both planes

• attacker destroys target

• target suffers critical damage

• target bails or despawns within seconds of receiving damage

• no kill in AAR of attacker

• no kill in AAR despawned

• (often) RTB in AAR despawned

• CSR matches this

[GOPHUR]

A)

• attacker and target are both planes
  
• attacker plinks target
  
• target suffers no critical damage
  
• target ditches and despawns within seconds of receiving damage
  
• no kill in AAR of attacker
  
• no kill in AAR despawned
  
• MIA/RES in AAR despawned
  
• CSR matches this
  

Expected functionality:

• attacker should get kill
  

By ditching you mean landed not crashed yes? This is a known issue. Ticketed.

• attacker and target are both planes
  
• attacker destroys target
  
• target suffers critical damage
  
• target bails or despawns within seconds of receiving damage
  
• no kill in AAR of attacker
  
• no kill in AAR despawned
  
• (often) RTB in AAR despawned
  
• CSR matches this
  

I have not seen reports of this. I'll try and test this... BRB...

What does attacker DESTROYS target mean?

Whay would the target (despawned) be looking for a kill?

Here's what I did:

• target spawns as plane (Bell14)
  
• attacker spawns as Tiger
  
• Tiger repeatedly shoots target with HE at point blank
  
• target recieves massive critical damage (vis dam, fire, etc.)
  
• Target gets KIA
  
• Attacker get kill award
  
• CORRECT
  

is this something to do with the one shot blow up thing?

[Tigger6]

• attacker should get kill

By ditching you mean landed not crashed yes? This is a known issue. Ticketed.

Yes, by ditching I mean not blow up, pilot survives, etc.

• attacker and target are both planes

• attacker destroys target

• target suffers critical damage

• target bails or despawns within seconds of receiving damage

• no kill in AAR of attacker

• no kill in AAR despawned

• (often) RTB in AAR despawned

• CSR matches this

I have not seen reports of this. I'll try and test this... BRB...

What does attacker DESTROYS target mean?

Whay would the target (despawned) be looking for a kill?

Here's what I did:

• target spawns as plane (Bell14)

• attacker spawns as Tiger

• Tiger repeatedly shoots target with HE at point blank

• target recieves massive critical damage (vis dam, fire, etc.)

• Target gets KIA

• Attacker get kill award

• CORRECT

is this something to do with the one shot blow up thing?

Yes, it seems to be similar to one shot blow up, however it has manifested in other situations too. For instance wing shot off, fire.

This is a rather rare even, unlike A). I would guess it happens 1 out of 30 times.

[Ogg]

GOPHUR,

I've had it happen and show up in CSR 2 days later.

Since I don't fly 3000 sorties a week like some I have a better ability to review mine.

Point in case Oct 26 20:51 mission I K.O.d the Hurricane and crashed as I pulled out from the attack.

I was plinked by a Spit earlier in the mission. That showed on my CSR but not the kill. I had a CTHL when I crashed and had to log back in to the game.

The kill was not there that night or on Oct. 27 1900est. It took until Oct.28 0700est (when I checked again) before the kill showed up on my CSR report.

Sometimes they just show up late.

Edited November 2, 2010 by Ogg

[DOC]

CS&R is webside reporting from the database, and has many causes for delay in that delivery. Most of these have zero to do with incorrect client functionality.

AAR in game UI is not the same thing, and has different parameters driving it's delivery to the UI than the webside stuff reporting in CS&R on the webpage does.

Quite often, getting them to be the exact same thing at the exact same time (instantly after a sortie) defeats us, because they aren't the same thing even though it would be great if they were. Naturally since "a kill is a kill" it is expected that they are the same thing, but I am talking about how they are derived and reported/leveraged for reporting not what they mean to the player. In terms of code they can be different even if a players perception indicates that they are the same.

So while they are not the same thing (in code) they have to of course be looked at as being different when reporting a bug; since a bug in one does not point to a bug in the other, except sometimes when they are derived from the same problem in code (not often but is possible, occassionally)

See why you can go crazy trying to satisfy all of this ?

[calven]

I saw something similar to this during intermission with the kill notifications.

Scenario was:

1. Landed hits on a previously undamaged plane

2. Pilot of said plane bailed

3. Plane then went on a ballistic arc into the ground where it was destroyed

4. No further hits on the plane between bail and destruction.

No kill credit was seen in chat window at time of bail or plane destruction and no kill was shown on the AAR.

I've asked the hangar if this is normal functionality (Intermission confirming bail is alt-f4 thread) and someone suggested I post the issue here.

I know for certain that my hits on the plane were within 30sec. of the bailout. Cannot confirm if they were for the plane impacting the ground.

[GOPHUR]

I saw something similar to this during intermission with the kill notifications.

Scenario was:

1. Landed hits on a previously undamaged plane

2. Pilot of said plane bailed

3. Plane then went on a ballistic arc into the ground where it was destroyed

4. No further hits on the plane between bail and destruction.

No kill credit was seen in chat window at time of bail or plane destruction and no kill was shown on the AAR.

I've asked the hangar if this is normal functionality (Intermission confirming bail is alt-f4 thread) and someone suggested I post the issue here.

I know for certain that my hits on the plane were within 30sec. of the bailout. Cannot confirm if they were for the plane impacting the ground.

They need to be within 60 seconds of the crash I believe.

I've been running through a lot of beta tests of this with permutations of plinks where:

• before and after 60 seconds

• target rtb

• target crash

• target ditch

The only bug in beta at present I can find is when a target ditches more than 60 seconds after the plink the kill is still being awarded. This may point to issues with syncing CSR and the AAR. We know there are issue here.

What will serve us best (asks the coders) is if you can post a screenie of your AAR (with sortie number) and a link to the CSR page that does not match it.

The coders can use this to find where the problems are. We are sure there is a problem but don;t know what it is other than sometimes slow updates to CSR.