5 replies to this topic

[ollo]

Well, since someone jettisoned my thread to oblivion, i'll try again here - or doesn't PGI want bug reports because they make the game look bad? Maybe we'll be able to pin something down as this seems to be a persistent problem for many players. (Note: this has nothing to do with resetting groups due to patches, this is about groups that reset or change ingame for unknown reasons)

Original post:

I've just had a game on caustic where i died in < 1 min because i had to configure the weapon groups ONCE AGAIN while the enemy spotters where already swarming around us - needless to say it's quite difficult to make the necessary changes while all you hear is "warning, incoming missiles" and are searching for a safe spot to park the mech. Didin't even finish assigning the groups correctly.

#PGIPLZWITHSUGARONTOP: this has to be one of the most moronic and easy to fix while most rage-inducing bugs in the whole game and it has been around for how long? How difficult can it be to save one fricking config file for one mech that must have an exclusive ID anyway???

Investigation #1:

I'm trying now deleting the weapongroups and seeing what it does. As i was ingame, it saved only the mech i was playing (TDR-9SE). This is the new XML:

<Mech ID="1163510935453730" CF="0">
  <Weapon itemID="1010" invID="1163510935453980" compID="4" groups="1"/>
  <Weapon itemID="1010" invID="1163510935454423" compID="4" groups="1"/>
  <Weapon itemID="1001" invID="1163510935454197" compID="2" groups="2"/>
  <Weapon itemID="1001" invID="1163510935454420" compID="2" groups="2"/>
  <Weapon itemID="1001" invID="1163510935454421" compID="2" groups="2"/>
</Mech>

Interestingly, when i search for this mech ID in the old file, it gives me this config:

<Mech ID="1163510935453730" CF="0">
  <Weapon itemID="1008" invID="1163510935454251" compID="4" groups="1"/>
  <Weapon itemID="1008" invID="1163510935454392" compID="4" groups="1"/>
  <Weapon itemID="1001" invID="1163510935454420" compID="2" groups="2"/>
  <Weapon itemID="1001" invID="1163510935454421" compID="2" groups="2"/>
  <Weapon itemID="1001" invID="1163510935454422" compID="2" groups="2"/>
  <Weapon itemID="1028" invID="1163510935454289" compID="2" groups="4"/>
</Mech>

So there was a completely different loadout saved with weapons that don't exist on the mech, which explains why the groups were complete BS i have never assigned when i jumped in. But some weapons are the same - maybe it didn't save weapon groups after i changed the loadout in mechlab? But i'm sure i played this mech and assigned WG ingame after i changed the loadout, so maybe there was one of the mysterious mech overlaps. Will continue to investigate...

Edited by Catalina Steiner, 16 November 2014 - 06:06 AM.

[ollo]

Ok, next try, SHD-2HP. Newly save WG (everything was reset to WG1 when i started):

<Mech ID="1163510935453725" CF="4">
  <Weapon itemID="1008" invID="1163510935453805" compID="4" groups="1"/>
  <Weapon itemID="1024" invID="1163510935454313" compID="2" groups="2"/>
  <Weapon itemID="1024" invID="1163510935454314" compID="2" groups="2"/>
  <Weapon itemID="1024" invID="1163510935454315" compID="2" groups="2"/>
  <Weapon itemID="1026" invID="1163510935454480" compID="7" groups="12"/>
  <Weapon itemID="1027" invID="1163510935453755" compID="1" groups="12"/>
  <Weapon itemID="1027" invID="1163510935453756" compID="1" groups="12"/>
</Mech>

I don't know what compID is supposed to be, it seems a bit off that one of the LRMs has another and i wonder why groups is 12 and not 3, but it seems overall OK. The config from the old file:

<Mech ID="1163510935453725" CF="4">
  <Weapon itemID="1023" invID="1163510935453960" compID="4" groups="1"/>
  <Weapon itemID="1001" invID="1163510935453958" compID="0" groups="2"/>
  <Weapon itemID="1001" invID="1163510935454167" compID="0" groups="2"/>
  <Weapon itemID="1014" invID="1163510935454321" compID="1" groups="0"/>
</Mech>

Well, WTF? Completely different weapons although i didn't change the loadout for ages. How can this be?

Edited by ollo, 16 November 2014 - 05:40 AM.

[Ironwithin]

http://mwomercs.com/...-weapon-groups/

[ollo]

Now the CPLT-C1F, oddly enough when i launched the WG were not all reset to 1, a laser or so was WG 2. New XML:

<Mech ID="1163510935453698" CF="0">
  <Weapon itemID="1043" invID="1163510935453856" compID="3" groups="12"/>
  <Weapon itemID="1043" invID="1163510935453714" compID="4" groups="12"/>
  <Weapon itemID="1001" invID="1163510935453740" compID="2" groups="1"/>
  <Weapon itemID="1001" invID="1163510935453741" compID="1" groups="2"/>
  <Weapon itemID="1011" invID="1163510935453882" compID="0" groups="1"/>
  <Weapon itemID="1011" invID="1163510935453883" compID="0" groups="2"/>
  <Weapon itemID="1014" invID="1163510935453963" compID="1" groups="0"/>
</Mech>

Seems ok, the old:

<Mech ID="1163510935453698" CF="8">
  <Weapon itemID="1043" invID="1163510935453856" compID="3" groups="12"/>
  <Weapon itemID="1043" invID="1163510935453714" compID="4" groups="12"/>
  <Weapon itemID="1001" invID="1163510935453740" compID="2" groups="1"/>
  <Weapon itemID="1001" invID="1163510935453741" compID="1" groups="2"/>
  <Weapon itemID="1011" invID="1163510935453882" compID="0" groups="1"/>
  <Weapon itemID="1011" invID="1163510935453883" compID="0" groups="2"/>
  <Weapon itemID="1014" invID="1163510935453963" compID="1" groups="0"/>
</Mech>

This seems fine, but it was also the last mech that i played before deleting the xml. Will switch to update on weird stuff only.

[Catalina Steiner]

Thread title changed. If you want to help, it's really appreciated. But watch your language as from now. It's not necessary to create such thread names. It's also inappropriate for the search function of this forum. Nevertheless thank you for your support.

[ollo]

Affirmative. I knew it would be translated to stars so i thought it would be up to the dirty reader's imagination anyways. plus it was a ragepost as explained in 1st post...

Also, thx iron for the link to the other thread, i wasn't aware that they pinned down the issue (or so it seems), so i'll hope on a fix next patchday.