60 replies to this topic

[Bront]

I think they think it's the UAV bug, and it's something else that got introduced.

It does make coms interesting though. "Targeting... Steve."

[Caervyn]

This isn't on PGI's radar because only 1% drop 12s and actually call targets..

We got to "U" in our last match vs BSK: Wardens....

[Bront]

Caervyn, on 06 March 2014 - 07:17 AM, said:

This isn't on PGI's radar because only 1% drop 12s and actually call targets..

We got to "U" in our last match vs BSK: Wardens....

I had a Z in one match, and then we couldn't target anything, on a non-turret match.

[Dracol]

It's been fun coming up with random designations for the latter letters. Some though have caused the unnecessary deaths of fellow pilots.

"New Target Victor"

response: "I know he hit you with a laser at the start of the match, but do we really need to team kill?"

For the sake of all the Victors out there, please fix this bug.

[Paul Inouye]

The issue was in a bug that was found where the target designator incrementation was pulling in both UAV and turret targets and placing them incorrectly in the display queue. The fix is apparently in the March 18th patch. I will be back later today to confirm this or not.

[TygerLily]

PRO TIP: Use names and chassis...

...but not first names...it's Sgt. Lily. I didn't spend 9 years in the Army not to be called Sgt...

[Bront]

Paul Inouye, on 06 March 2014 - 10:31 AM, said:

[color=cyan]
The issue was in a bug that was found where the target designator incrementation was pulling in both UAV and turret targets and placing them incorrectly in the display queue. The fix is apparently in the March 18th patch. I will be back later today to confirm this or not.
[/color]

But it was happening on maps with no turrets nor any UAV launched (IE, every match I ever played).

[TinFoilHat]

Paul Inouye, on 06 March 2014 - 10:31 AM, said:

[color=cyan]
The issue was in a bug that was found where the target designator incrementation was pulling in both UAV and turret targets and placing them incorrectly in the display queue. The fix is apparently in the March 18th patch. I will be back later today to confirm this or not.
[/color]

Would this still explain how a mech jumps from say, E to F or even G whilst I still have him targetted? Or how the same mech increments its designation when I power up after an overheat shutdown? Or as with Bront's case, when we're on Skirmish or Conquest and there's no UAV deployed?

[CoffiNail]

Paul Inouye, on 06 March 2014 - 10:31 AM, said:

The issue was in a bug that was found where the target designator incrementation was pulling in both UAV and turret targets and placing them incorrectly in the display queue. The fix is apparently in the March 18th patch. I will be back later today to confirm this or not.

Thanks for the info, please let us know if this should get fixed on the 18th. Though we all know this is working as intended, and it was your devious plan to get a few kicks while observing 12 mans... admit it Paul, I am on to you.

[Grendel408]

(NATO) Phonetic Alphabet: Alpha, Bravo, Charlie, Delta, Echo, Foxtrot, Golf, Hotel, India, Juliette, Kilo, Lima, Mike, November, Oscar, Papa, Quebec, Romeo, Sierra, Tango, Uniform, Victor, Whiskey, Xray, Yankee, Zulu. But, yes... please fix in the upcoming patch Devs

Edited by Grendel408, 06 March 2014 - 03:52 PM.

[Paul Inouye]

Ok... back. We've been back-tracking the "fix" that went in. We were able to reproduce the bug a couple times on our internal builds. Testers and dev support are trying to trackdown 100% repro steps so the engineers can identify the exact cause.

Our internal repro steps included targeting an enemy turret. Destroying it. Then having another enemy turret destroy a friendly Mech... then bam, it happened, all enemy Mech designators changed. We tried the same steps again and it didn't happen. We will continue to track this bug and I'll update here as soon as we get any traction on it.

So again, apologies.. we're on it actively and will update/fix asap. Meanwhile if anyone gets a set of detailed steps on how to repro this 100%, please let me know. Thanks for the help.

-Paul

[Bitslizer]

Paul Inouye, on 06 March 2014 - 06:33 PM, said:

Ok... back. We've been back-tracking the "fix" that went in. We were able to reproduce the bug a couple times on our internal builds. Testers and dev support are trying to trackdown 100% repro steps so the engineers can identify the exact cause.

Our internal repro steps included targeting an enemy turret. Destroying it. Then having another enemy turret destroy a friendly Mech... then bam, it happened, all enemy Mech designators changed. We tried the same steps again and it didn't happen. We will continue to track this bug and I'll update here as soon as we get any traction on it.

So again, apologies.. we're on it actively and will update/fix asap. Meanwhile if anyone gets a set of detailed steps on how to repro this 100%, please let me know. Thanks for the help.

-Paul

Why not just randomly "pre-assign" a target designation to all mech, regardless of order they were targeted.

[Buso Senshi Zelazny]

Paul Inouye, on 06 March 2014 - 06:33 PM, said:

Ok... back. We've been back-tracking the "fix" that went in. We were able to reproduce the bug a couple times on our internal builds. Testers and dev support are trying to trackdown 100% repro steps so the engineers can identify the exact cause.

Our internal repro steps included targeting an enemy turret. Destroying it. Then having another enemy turret destroy a friendly Mech... then bam, it happened, all enemy Mech designators changed. We tried the same steps again and it didn't happen. We will continue to track this bug and I'll update here as soon as we get any traction on it.

So again, apologies.. we're on it actively and will update/fix asap. Meanwhile if anyone gets a set of detailed steps on how to repro this 100%, please let me know. Thanks for the help.

-Paul

It doesn't surprise me that you failed to reproduce the issue, since it seems to be occurring just as often on maps with no turrets as those that don't. I've had drops on Skirmish, where I have a mech targeted (say, D), my friend calls out the designation of a mech to focus (say, E), and then starts shooting the mech that I see as D, but he sees it as E.

Another instance, my group is focusing a mech with designation F, and we all start shooting the same mech (miraculously). Mech F is destroyed move on to next target, which is also desginated F. Start focus F version 2.0, and then a friend on comms says "Wait F is not dead", referring to F version 1. I'm thinking ok, he just got confused because he switched to the next target and it was the same chassis with the same loadout as F version 1.Then a few seconds later he says that F is down, while on my screen F version 2 is still fighting....

I think the issue might be that different clients may be incrementing the target designations at different times under different conditions, since different users seem to be able to see the same mech with different desiginations.

[RamsoPanzer]

Paul Inouye, on 06 March 2014 - 06:33 PM, said:

Ok... back. We've been back-tracking the "fix" that went in. We were able to reproduce the bug a couple times on our internal builds. Testers and dev support are trying to trackdown 100% repro steps so the engineers can identify the exact cause.

Our internal repro steps included targeting an enemy turret. Destroying it. Then having another enemy turret destroy a friendly Mech... then bam, it happened, all enemy Mech designators changed. We tried the same steps again and it didn't happen. We will continue to track this bug and I'll update here as soon as we get any traction on it.

So again, apologies.. we're on it actively and will update/fix asap. Meanwhile if anyone gets a set of detailed steps on how to repro this 100%, please let me know. Thanks for the help.

-Paul

Paul, it cant have much to do with turrets, because it happens in every match, no matter the gamemode, and no matter if you use uav or not. The bug first appeared when you introduced the turrets for the first time, yes, but looks like has nothing to do with them. And the steps to reproduce it... just play any match, it happens constantly, i cant really link it to any particular action. Surprising that you werent aware of this?

Edited by RamsoPanzer, 06 March 2014 - 10:12 PM.

[The Cloak]

Pretty sure the bug is triggered by mechs overheating or dying

[Steelgrave]

RamsoPanzer, on 04 March 2014 - 01:14 PM, said:

So how come that after one whole month the targeting bug is still not fixed and there is no mention about it? The letter designation for each mech keep changing during the match and it is so hard to call mechs.

An explanation from PGI would be nice!

And the micro-lock, and client closing freeze, and...

Around here, the bugs are the residents.

[Svidro]

Glad to know there are some testers on it. I'd agree with simply pre-assigning letters to both teams though, if that would fix the issue for now. Make it a low priority to bring back dynamic labeling in the future.

[Svidro]

Have you tried having enemy mechs shut down and power back up repeatedly (and targeting them before and after) and/or walking into and out of range of the turrets so they go dormant/lose target.

Yeah, hard to confirm, but I was able to get the lettering up to Q last game while weaving in and out of the base defense's activation range. Not that that helps for when there are no turrets. Maybe for UAVs it's when things move in and out of the UAV detection?

Edited by Svidro, 06 March 2014 - 11:40 PM.

[Psikez]

Drop into a 12v12 with a team and listen to their comms, issue reproduced... ALPHA..NOW ITS OSCAR...Q?? NOW ITS U I DONT KNOW

[Evil Ed]

Zombie Atlas now have a new meaning, once in a 12-man we killed Foxtrot Atlas not twice but three times... Just pre-assign and be done with it.