60 replies to this topic

[LadyZowy]

Lima now November, nope now Quebec.... It seems like the whole system reshuffles when targeting lock is lost. I always run the Target Info Gathering module. I'm not sure if it has something to do with that... But this is getting stupid. Fix this now!!!!!

FPS issues, DX11 issues, UI issues, bad bad bad.... Come on guys crush the bugs don't create new ones. Test this app before you launch.

[Bitslizer]

LordZowy, on 07 March 2014 - 06:41 AM, said:

Lima now November, nope now Quebec.... It seems like the whole system reshuffles when targeting lock is lost. I always run the Target Info Gathering module. I'm not sure if it has something to do with that... But this is getting stupid. Fix this now!!!!!

FPS issues, DX11 issues, UI issues, bad bad bad.... Come on guys crush the bugs don't create new ones. Test this app before you launch.

Targetting lock by whom? i've literally watch the target designation of a mech targeted by me change letters right before my eyes without losing target lock

[Big Tin Man]

I do have to say that getting into the latter half of the alphabet has made for some entertaining calls on the coms:

"Ok we're on... (P, P, P, uh...) the Atlas.... uh, Penis. Wait, no, it's Q now. Atlas Queen. Atlas Penis Queen."

Then we die of lulz.

[Scromboid]

Teamwork is OP.

This is intended to bring the PUGs up to a level playing field.

[Svidro]

Anyone else tried incrementing by toying with the turrets in assault?

[weevil]

I only play skirmish, and I see this regularly. It's definitely not limited to turrets, but turrets + UAV would be possible.

[Icebergdx]

I have watched the designation letters change in a skirmish match with no turrets, and no UAV. The explanation that Paul is giving is just another BS post to try and make it look like PGI is actually doing something, when they are really either standing around looking at each other going "I don't know why its happening" or they are standing around going "hahaha, listen to all those idiots complain, what else can we do to screw up the game."

At one time, I would have been more understand of the former. Now I totally think it is the later, and that Paul and crew really don't give a damn about trying to fix this buggy POS any more (if they ever did) because it has been months since the Beta tag came off, yet this game is STILL A FREAKING BETA!!!!!!!!!!

They fooled me twice, with Founder and Overlord, and I want Clan mechs, but I will not pay another dime until they actually FIX AND FINISH THE DAMN GAME!!!

Edited by Icebergdx, 08 March 2014 - 10:00 AM.

[Werewolf486 ScorpS]

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!

That's just too funny! You expect results or even aknowledgement in a timely manner from PGI (Bryan and Russ), that's just laughable!

[Bront]

I've been told it happens when a mech loses a target, changes their target, and then retargets the same mech. It may also be an error in the code that checks if a mech already has a letter. It was introduced when UI2.0 was introduced. This would explain while it seems to happen later in the match more often, and can happen when there's only 1 target.

Personally, I like the idea of randomly assigning A-L to each side rather than letting them be designated by first contact.

[Swiftsteel]

Icebergdx, on 08 March 2014 - 09:59 AM, said:

when they are really either standing around looking at each other going "I don't know why its happening"

Well, to be honest, a surprisingly large part of software development consists of the above.

"My code doesn't work... and I have no idea why" alternating with "My code works.. and I have no idea why".

[Threat Doc]

Again, folks, there are several ways to track targets apart from letter designators, such as relative range and bearing -like in the old days with MechWarrior II through IV-, by the type of 'Mech -less reliable, as there may be multiples of the same 'Mech-, by the name of the pilot targeted and, finally, by mini-grid reference and 'Mech type, as there may be several 'Mechs in the same grid you're referencing.

Paul has said they're tracking this, trying to fix it and, though I'm not trying to white knight, here, I'm saying let's give them eight more days to get this figured out. If not, get used to designating targets in a different way, because honestly this really is a very minor inconvenience.

[Mechteric]

This needs to be fixed ASAP. This is really affecting teamwork play because you can't even tell over chat "Take out target D" because seconds later its going to be "J" or some other random letter designation.

Edited by CapperDeluxe, 10 March 2014 - 05:03 AM.

[TinFoilHat]

No fix this week then? We hoping for something in next week's patch instead? Or is Launch Module more likely?

[Deathlike]

TinFoilHat, on 11 March 2014 - 11:53 AM, said:

No fix this week then? We hoping for something in next week's patch instead? Or is Launch Module more likely?

It'll be in the next patch (next week), at least if we believe Paul. No hotfix until then...

Launch Module is late April...

Edited by Deathlike, 11 March 2014 - 12:35 PM.

[Paul Inouye]

Good news everybody!



After getting a confirmed set of repro steps, the bug has been found. The fix has been put into a build and all things working out, you can expect the fix on the April 1st patch. (No this is not an April Fool's joke )

[Ironwithin]

Holy Moly... for a second there I feared we were getting
"Good news, everyone. Tomorrow, you'll all be making a delivery to Ebola 9, the virus planet."-good news.

You are an evil man, Sir.

[Deathlike]

It would have been greatly more appreciated had it been fast tracked to next week's patch (is it really worth extending this bug until April 1st?)

[Kyle Lewis]

Icebergdx, on 08 March 2014 - 09:59 AM, said:

I have watched the designation letters change in a skirmish match with no turrets, and no UAV. The explanation that Paul is giving is just another BS post to try and make it look like PGI is actually doing something, when they are really either standing around looking at each other going "I don't know why its happening" or they are standing around going "hahaha, listen to all those idiots complain, what else can we do to screw up the game."

At one time, I would have been more understand of the former. Now I totally think it is the later, and that Paul and crew really don't give a damn about trying to fix this buggy POS any more (if they ever did) because it has been months since the Beta tag came off, yet this game is STILL A FREAKING BETA!!!!!!!!!!

They fooled me twice, with Founder and Overlord, and I want Clan mechs, but I will not pay another dime until they actually FIX AND FINISH THE DAMN GAME!!!

guess no clans then for you, since the game will always be in development just like every other MMO out there.

[Ellen Ripley]

Paul Inouye, on 11 March 2014 - 03:38 PM, said:

Good news everybody!

After getting a confirmed set of repro steps, the bug has been found. The fix has been put into a build and all things working out, you can expect the fix on the April 1st patch. (No this is not an April Fool's joke )

The parts where you found it, fixed it and tested it are indeed great news! Thank you a ton for that.
The part where you write we'll have to live with this problem for another 3 weeks is completely incomprehensible to me.

Teamplay is being totally screwed by this bug having a great negative effect on focus fire etc..
Please reconsider your plan to hold back the fix until April 1st patch and bring it live with a hotfix as soon as possible.

I can assure you the thanks of everyone playing in a group (be it 2 to 4s or 12s) should you do that.

[TinFoilHat]

Thanks for the heads up Paul. Will stick it out a bit longer and see how the fix pans out. Hopefully will actually work this time