26 replies to this topic

[Unnatural Growth]

Like the title says...

PGI, I'm really getting sick of dropping into a mech only to find out that once again, you've scrambled the weapon groups I had preset on the mech. There seems to be no rhyme or reason to it, some patches don't affect them, and some patches wipe them out. These are owned mechs, not trials, and I don't have duplicate variants that are jacking with the group assignments.

Please fix this so weapon groups are persistent to each mech you own.

Thank you.

[Burktross]

Also, weapon groups are wonky when holding one group down and tapping others.

[Monkey Lover]

Really bad when you drop in charlie in an assault when lights are on your butt in 15 seconds

[TheCaptainJZ]

have you tried deleting the weapon group file and letting it rebuild? Possibly the entire user folder (make sure you know what keys you've remapped and written down all your settings first)? No idea if this helps, but it's easy enough that i think it's worth a shot.

[One of Little Harmony]

TheCaptainJZ, on 11 November 2014 - 08:54 PM, said:

have you tried deleting the weapon group file and letting it rebuild? Possibly the entire user folder (make sure you know what keys you've remapped and written down all your settings first)? No idea if this helps, but it's easy enough that i think it's worth a shot.

I've had this problem on a fresh install.

[Gauvan]

This would be my A-Number-One priority bug to fix. It's been around for a long time and players have provided constant information to PGI that should help them track down the cause.

On IS mechs it's just an irritation that can be fixed at the start of the match. On Clan mechs with a dozen hardpoints it can essentially cripple a build for that match. Take a Dire Wolf with the arm hardpoints full. The majority of players will have split the weapon groups by mech section, and will be firing the arms separately. You have no way to know which weapon is on which arm except experimentation and that should absolutely not be done in a match.

If I understand the cause (collision between mech ID numbers) then it even disproportionately hits long time loyal customers as the more mechs you have the more likely you are to experience the bug.

Please, please, fix this.

[Egomane]

Gauvan, on 12 November 2014 - 06:31 AM, said:

This would be my A-Number-One priority bug to fix. It's been around for a long time and players have provided constant information to PGI that should help them track down the cause.

No! The number one priority bugs should be the ones, that prevent people from playing completly.

This one is an annoying bug, but it one that affects comfort only. Probably because of that it isn't fixed already.

[Gauvan]

Egomane, on 12 November 2014 - 06:40 AM, said:

No! The number one priority bugs should be the ones, that prevent people from playing completly.

This one is an annoying bug, but it one that affects comfort only. Probably because of that it isn't fixed already.

I did say it was my number one priority.

I also think I presented a case why this bug is more than an inconvenience: I have mechs (Nova, DW) that when they have their weapons groups reset are crippled for the match unless I spend an inordinate amount of time at the start trying to sort out weapons groups. In matches that last 5-7 minutes, spending a minute at the spawn point can swing the match, and going in without means constant overheating or an inability to shoot around teammates.

[Skribs]

There are a lot of priority issues.

Maps clipping shots.
Weapon groups.
That weird bug where the red numbers are bigger than the blue numbers...

[Unnatural Growth]

Egomane, on 12 November 2014 - 06:40 AM, said:

No! The number one priority bugs should be the ones, that prevent people from playing completly.

This one is an annoying bug, but it one that affects comfort only. Probably because of that it isn't fixed already.

C'mon Ego,

"Low hanging fruit" as it were. This one can't possibly take a team of NSA specialists to crack. Ought to be an easy one, that can just be tossed in to a regular patch day and be done with it.

Take a few easy victories when you can get them (bug fixes, as it were).

EDIT-- Forgot to add...

"Oh, and thanks for moving my thread"

Edited by OldOrgandonor, 12 November 2014 - 04:54 PM.

[Alexander Garden]

Hey everyone,

Please be assured that the weapon group issues are currently high-priority in our QA database.

While we continue to work on a final fix, I should be able to manually resolve your individual issues if you e-mail a ticket to support@mwomercs.com with the heading "Weapon Group Repair" and attach the weapongroups.xml file from your \MechWarrior Online\USER\Profiles\<your username> folder.
I can then manually organize your XML to reflect the current 'Mech inventory listed in your account details.

If you do submit a ticket for that purpose, I'll try to get to it as soon as I can. It's a bit of a time-consuming process though, so the turnaround won't be immediate.

[Unnatural Growth]

Well shave my butt, paint it red, and drop me in an unarmed Locust.

(ok don't really)

Wow, is all I can say. Alex, are you wanting the XML file now, even though I have currently fixed (I think) all my mech's weapon groups again? Or is this for after the next weapon group scramble happens?

Oh, and Thank you Alex for the very fast offer of help. I appreciate it.

Edited by OldOrgandonor, 12 November 2014 - 07:06 PM.

[Unnatural Growth]

I sent in a support ticket with my weapon group xml file attached.

Thanks again Alex for posting in my thread and offering to help, that actually really impressed me.

[Smith Gibson]

The only problem is as soon as you make any changes at all to any of your 'mechs you run the risk of the problem coming back. I finally got the problem fixed after six months of aggravation, only to have it come back TWO FRICKING DAYS LATER!

Six Support tickets sent in, about 9 hours of rebuilding my weapongroup.xml file over and over again during those six months. Aand before I could even play 30 matches, i'm back to having a half dozen of my 'mechs being secret deathtraps if I played the wrong 'mech before it.

You'll forgive me if I call bullshit on any fix happening in the next year.

[Alexander Garden]

Give me a couple more days to confirm, but we might have a fix for this coming on the 18th.

[Unnatural Growth]

Got a reply email from Alex today, with my updated xml file enclosed.

Have to say, that is some fast, responsive, customer service.

[Troutmonkey]

Alexander Garden, on 13 November 2014 - 04:33 PM, said:

Give me a couple more days to confirm, but we might have a fix for this coming on the 18th.

Whatever they're paying you they should double it. Since you've come on board PGI's technical communications and bug fixes have improved significantly.

[Alexander Garden]

As for that blinking chat icon....

[Rhialto]

OldOrgandonor, on 13 November 2014 - 04:47 PM, said:

Got a reply email from Alex today, with my updated xml file enclosed.

Have to say, that is some fast, responsive, customer service.

wow, wth? I have a ticket (148569) open since novembre 8th (see this Russ tweet) about this problem which is still not solved... there is no priority queue with tickets!?

[Alexander Garden]

Hey Rhialto,

Sorry about that. I've been filtering these tickets with search terms and yours fell through the cracks.