5 replies to this topic

[Frantic 0]

Confirmed working so far. You will have to redo your weapon groups, but only once instead of at random intervals. Thanks to Cest7 :

If none of your groups save try deleting:

MechWarrior Online\USER\Profiles\USERNAME\weapongroups.xml

This will delete all your saved group and start a fresh file, useful if it somehow gets corrupt

[MrMadguy]

Stop posting this solution in every thread. I've tried this solution - it isn't working. It's just waste of time. While experimenting I've found out, that this problem is caused by shared mech IDs. I.e. two mechs having exact the same ID. What does ID mean? If you'll open weapongroups.xml, you'll see something like that (my Pretty Baby's weapon groups):

<Mech ID="685884802334735" CF="0">
  <Weapon itemID="1004" invID="685884802334951" compID="3" groups="4"/>
  <Weapon itemID="1004" invID="685884802334962" compID="3" groups="4"/>
  <Weapon itemID="1008" invID="685884802334950" compID="4" groups="2"/>
  <Weapon itemID="1001" invID="685884802334949" compID="7" groups="1"/>
  <Weapon itemID="1010" invID="685884802334977" compID="2" groups="2"/>
  <Weapon itemID="1031" invID="685884802334963" compID="1" groups="4"/>
</Mech>

You can see, that mech tag have ID attribute. Let's count, how many groups my weapongroups.xml have: yea, 15 groups. And how many it should have? Yea. 17. Looks like two are missing. Why? I'll explain.

So, now I'll take a look on my AWS-8R weapon groups in game - it's messed up and all reseted to mouse left. Ok. What will happen, if I'll fix them? First of all let's check weapon groups for my Pretty Baby (i.e. with ID 685884802334735) again:

<Mech ID="685884802334735" CF="0">
  <Weapon itemID="1001" invID="685884802335010" compID="4" groups="1"/>
  <Weapon itemID="1001" invID="685884802335011" compID="4" groups="1"/>
  <Weapon itemID="1001" invID="685884802335005" compID="7" groups="1"/>
  <Weapon itemID="1028" invID="685884802335004" compID="2" groups="2"/>
  <Weapon itemID="1028" invID="685884802335013" compID="2" groups="4"/>
  <Weapon itemID="1028" invID="685884802335003" compID="1" groups="2"/>
  <Weapon itemID="1028" invID="685884802335012" compID="1" groups="4"/>
</Mech>

Whaaaaaat? It's changed and now looks like it's AWS-8R groups! Let's confirm this theory via checking Pretty Baby's groups in game. Yup. It's messed up now.

So. You can see, that my Pretty Baby and AWS-8R have shared mech IDs, which causes their weapon groups to be saved into exact the same place in weapongroups.xml. And of course, when you change weapon groups on one mech, groups on another being messed up, cuz this mech may have other weapons equipped. Also I have found out, that my Jester and AWS-8Q also have their weapon groups shared. And it's the reason, why 2 weapon groups are missing in weapongroups.xml - because 2 are shared.

From where this mech IDs came from? I guess, that from server. So, it means, that mech IDs on server are corrupted. So it's server-side error and you can't fix it via any client-side solutions. So just should avoid playing mechs with shared IDs at the same time, till this bug won't be fixed.

Edited by MrMadguy, 05 April 2014 - 09:51 PM.

[Ironwithin]

If it works for SOME people, what is the danger of linking to it when a "my groups are messed up!"-thread pops up ?
It's not like you can damage anything by deleting that file. The worst that can happen is that you have to re-do your weapongroups, wich is why the thread was made in the first place.

[MrMadguy]

I just don't understand, how deletion of this file can help to solve this problem, cuz in fact client doesn't add into or modify something in this file - it just completely overwrites it every time, you're changing your weapon groups anyway. And, I guess, client have admin rights, so there should not be any problems with write permissions. So, this file just can't be corrupted in any way.

Edited by MrMadguy, 05 April 2014 - 10:28 PM.

[warner2]

This is an easy fix if that's the cause. Generate the ID, check it exists, if it does, generate another one, until it's unique. Pretty basic bug and damn annoying having to redo weapon groups at the start of drops.

[Cest7]

MrMadguy, on 05 April 2014 - 09:41 PM, said:

this problem is caused by shared mech IDs. I.e. two mechs having exact the same ID.

Have you submitted your findings in a support ticket? Deleting the weapons XML is a mickey mouse fix for changing IDs after patches, If the server is sending duplicate IDs then deleting the file will do nothing as you've said.