12 replies to this topic

[oldradagast]

This problem started showing up after the previous patch that reset weapon groups, though it continues today.

For some reason, I just cannot get the game to save custom weapon groups on two of my mechs (a Hunchback 4H and a Jager-DD.)

Insanely, I get can the game to save a custom weapon grouping on ONE of them, but not both. As soon as I change the weapon group settings on the 2nd of these two "corrupted" mechs, the 1st has its weapon group settings reverted back to defaults (everything being on the "1" trigger.)

I have no idea why this is happening, but these two mechs seem to be inter-linked in some corrupted way.

Anyway, I just figured I'd report this.

[Giant Bob]

Thank you my friend, this is exactly the problem I'm having. I meticulously went through re-assigning my weapon groupings again, after the patch. I did this in testing grounds for each mech. Not all had been reset to default. Logged out of game and closed program, then re-opened and verified changes were still showing. Played in real matches several hours without issue. Logged out and quit for night. Just logged in to find my current main's groupings set back to default.

[oldradagast]

This nutty bug seems to show up regardless of how I reset the weapons, either in a game / testing ground or in the Mechlab. It is rather annoying, but it only seems to be affecting those two mechs.

[Ironwithin]

Sadly there is a bug that makes some 'mechs share their IDs and therefore their weapongroups override each other when changed. Submit a support ticket and let PGI know it's still an issue.

[BladeXXL]

delete your weapongroups.xml stored in you mwo profile folder.
all your groupings are gone after that and the file will be recreated once you change weapongroups.
this way you also delete all the previous stored "old" weapon and mech IDs which probably caused your issue.

[Daekar]

This happens intermittently on different mechs of different chassis regardless of whether or not I have made changes. Sometimes when I change them back it sticks and sometimes it doesn't.

[A banana in the tailpipe]

I hate when this happens as it will completely throw my game off

[MrMadguy]

Big Daddy Alpha, on 22 April 2014 - 08:17 AM, said:

Hey guys,

We're looking into this issue and if everyone having this issue could submit a ticket with their weapongroups.xml so we can narrow down a repro rate on our end that would be much appreciated. You can find this in the C:\Program Files (x86)\Piranha Games\MechWarrior Online\USER\Profiles for users on a 64bit client of windows

Thanks,
BDA

We told you, what is the cause of this problem several times already: it's the same ID being assigned to two mechs. You should do simple thing now - track the whole IDs' path from WeaponGroups.xml (or in-memory storage of weapon groups) to their origin (server database for example) and check it for things, that may mess IDs up (broken ID generator for example). I don't think, that collecting Omicron.txt and WeaponGroups.xml files from players for several weeks already - is effective way to solve this problem.

[Ironwithin]

So...instead of being a pain in the behind, why not simply do what the man trying TO HELP YOU is asking you to do ?

[Kinski Orlawisch]

It is affecting my DDCs...i have 3. ..The other mechs are mainly uneffected.

[Troutmonkey]

This guy seems to have a pretty good explanation of it:
http://mwomercs.com/...haring-problem/

Also this problem seems pretty widespread. I'm experiencing it too
http://mwomercs.com/...eapon-grouping/
http://mwomercs.com/...oups-resetting/
http://mwomercs.com/...-up-hbk-4p-4sp/
http://mwomercs.com/...apon-groupings/

[ImperialKnight]

BladeXXL, on 17 April 2014 - 12:19 AM, said:

delete your weapongroups.xml stored in you mwo profile folder.
all your groupings are gone after that and the file will be recreated once you change weapongroups.
this way you also delete all the previous stored "old" weapon and mech IDs which probably caused your issue.

tried it, doesn't solve the problem. the new .xml file gets corrupted as well

[MrMadguy]

Yea, I've noticed, that only recently bought mechs are affected. Cuz AWS-8R and AWS-8Q are two mechs, I've bought recently. And now I've found out, that two new mechs, I've bought/received just a week ago are affected by this problem too - it's CTF-3D and TDR-9S. CTF-3D has it's weapon groups shared with CPLT-K2 and TDR-9S - with AS7-RS. So, I guess, the real cause of the problem - is ID generator messed up since the last patch.

Edited by MrMadguy, 26 April 2014 - 04:55 AM.