Jump to content

Weapons Group Fiasco


  • You cannot reply to this topic
29 replies to this topic

#21 Livewyr

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 6,733 posts
  • LocationWisconsin, USA

Posted 28 July 2014 - 04:14 AM

I never have this problem, ever.

(But then, I never use the Mechlab's grouping option... I do it in match.)

#22 DarthPeanut

    Member

  • PipPipPipPipPipPipPip
  • Liquid Metal
  • 861 posts

Posted 28 July 2014 - 05:59 AM

There is a conflict with some mechs when run they will reset another mechs weapons groups.

Trying to narrow down which one is reseting my D-DC.. think it is my Shawk-2K but I always forget to check immediately after running it to be sure.

#23 Y E O N N E

    Member

  • PipPipPipPipPipPipPipPipPipPipPipPip
  • The Nimble
  • The Nimble
  • 16,810 posts

Posted 28 July 2014 - 02:27 PM

View PostLivewyr, on 28 July 2014 - 04:14 AM, said:

I never have this problem, ever.

(But then, I never use the Mechlab's grouping option... I do it in match.)


It's not a MechLab thing. I always set my groups inside of a match as well.

The fact that multiple 'Mechs have the same ID code is the issue and it's utterly moronic that it's happening at all. Seriously, how do you screw up a simple database?

#24 Joseph Mallan

    ForumWarrior

  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • FP Veteran - Beta 1
  • FP Veteran - Beta 1
  • 35,216 posts
  • Google+: Link
  • Facebook: Link
  • LocationMallanhold, Furillo

Posted 28 July 2014 - 03:17 PM

View PostLivewyr, on 28 July 2014 - 04:14 AM, said:

I never have this problem, ever.

(But then, I never use the Mechlab's grouping option... I do it in match.)

I usually set it up in the Play Ground.

#25 terrycloth

    Member

  • PipPipPipPipPipPipPip
  • Little Helper
  • Little Helper
  • 769 posts

Posted 28 July 2014 - 04:19 PM

I have this problem all the time. I take a few seconds to fix it at the start of maybe every other match.

Except for my Raven which is always how I left it.

#26 Infine

    Member

  • PipPipPipPipPipPip
  • 354 posts

Posted 28 July 2014 - 10:41 PM

View PostDarthPeanut, on 28 July 2014 - 05:59 AM, said:

Trying to narrow down which one is reseting my D-DC.. think it is my Shawk-2K but I always forget to check immediately after running it to be sure.

You don't have to drop into the game. You can configure weapon grouping in mechlab and save it. That's when it resets the other mech grouping. So configure weapons on one mech and check the other - it will have its groups reset. And vice versa. No need to drop into a match.

View PostYeonne Greene, on 28 July 2014 - 02:27 PM, said:

The fact that multiple 'Mechs have the same ID code is the issue and it's utterly moronic that it's happening at all. Seriously, how do you screw up a simple database?

They don't appear to have the same ID. Here's the part from weapongroups.xml about affected mechs.

<Mech ID="42846593744911" CF="4">
  <Weapon itemID="1008" invID="42846593745074" compID="3" groups="1"/>
  <Weapon itemID="1008" invID="42846593745090" compID="4" groups="1"/>
  <Weapon itemID="1025" invID="42846593745092" compID="1" groups="2"/>
  <Weapon itemID="1025" invID="42846593745093" compID="1" groups="2"/>
  <Weapon itemID="1032" invID="42846593745054" compID="2" groups="4"/>
  <Weapon itemID="1032" invID="42846593745055" compID="2" groups="4"/>
  <Weapon itemID="1032" invID="42846593745147" compID="2" groups="4"/>
  <Weapon itemID="1014" invID="42846593745103" compID="3" groups="0"/>
</Mech>
...
<Mech ID="42846593744913" CF="4">
  <Weapon itemID="1010" invID="42846593744957" compID="4" groups="1"/>
  <Weapon itemID="1010" invID="42846593745083" compID="4" groups="1"/>
  <Weapon itemID="1001" invID="42846593744935" compID="2" groups="2"/>
  <Weapon itemID="1001" invID="42846593744936" compID="2" groups="2"/>
  <Weapon itemID="1001" invID="42846593744940" compID="2" groups="2"/>
</Mech>


The first one should be DDC and the second one shoud be TDR-9SE.

As you can see, mech IDs are different (in fact, they apparently go incremental per user unless trial and are not variant IDs, but actual chassis UIDs).
itemIDs are most likely weapon type IDs, and both mechs don't even have similar weapons on them.
invIDs are probably individual equipment UIDs, and they apparently also go incremental per user unless trial (in which case invID is 0).
compIDs look like weapon locations (3,4 are arms, 1 and 2 are STs, CT is 0).
groups are kinda self-explanatory in name, but apparently are actually bit masks (think POSIX file permissions).
CF in mech field is most likely the list of chainfired groups (also a bit mask).

There appear to be no overlapping mech or weapon IDs, and both groupings are actually saved in the file at the same time, but for some reason one of them resets in game (or, more likely, since they are both SAVED, it's not so much resetting, as fails to load).

Edited by Infine, 28 July 2014 - 10:44 PM.


#27 Budor

    Member

  • PipPipPipPipPipPipPipPipPip
  • 2,565 posts

Posted 28 July 2014 - 10:47 PM

Friend off me has this issue on his DDC.

#28 Y E O N N E

    Member

  • PipPipPipPipPipPipPipPipPipPipPipPip
  • The Nimble
  • The Nimble
  • 16,810 posts

Posted 29 July 2014 - 12:32 AM

View PostInfine, on 28 July 2014 - 10:41 PM, said:

You don't have to drop into the game. You can configure weapon grouping in mechlab and save it. That's when it resets the other mech grouping. So configure weapons on one mech and check the other - it will have its groups reset. And vice versa. No need to drop into a match.


They don't appear to have the same ID. Here's the part from weapongroups.xml about affected mechs.

<Mech ID="42846593744911" CF="4">
  <Weapon itemID="1008" invID="42846593745074" compID="3" groups="1"/>
  <Weapon itemID="1008" invID="42846593745090" compID="4" groups="1"/>
  <Weapon itemID="1025" invID="42846593745092" compID="1" groups="2"/>
  <Weapon itemID="1025" invID="42846593745093" compID="1" groups="2"/>
  <Weapon itemID="1032" invID="42846593745054" compID="2" groups="4"/>
  <Weapon itemID="1032" invID="42846593745055" compID="2" groups="4"/>
  <Weapon itemID="1032" invID="42846593745147" compID="2" groups="4"/>
  <Weapon itemID="1014" invID="42846593745103" compID="3" groups="0"/>
</Mech>
...
<Mech ID="42846593744913" CF="4">
  <Weapon itemID="1010" invID="42846593744957" compID="4" groups="1"/>
  <Weapon itemID="1010" invID="42846593745083" compID="4" groups="1"/>
  <Weapon itemID="1001" invID="42846593744935" compID="2" groups="2"/>
  <Weapon itemID="1001" invID="42846593744936" compID="2" groups="2"/>
  <Weapon itemID="1001" invID="42846593744940" compID="2" groups="2"/>
</Mech>


The first one should be DDC and the second one shoud be TDR-9SE.

As you can see, mech IDs are different (in fact, they apparently go incremental per user unless trial and are not variant IDs, but actual chassis UIDs).
itemIDs are most likely weapon type IDs, and both mechs don't even have similar weapons on them.
invIDs are probably individual equipment UIDs, and they apparently also go incremental per user unless trial (in which case invID is 0).
compIDs look like weapon locations (3,4 are arms, 1 and 2 are STs, CT is 0).
groups are kinda self-explanatory in name, but apparently are actually bit masks (think POSIX file permissions).
CF in mech field is most likely the list of chainfired groups (also a bit mask).

There appear to be no overlapping mech or weapon IDs, and both groupings are actually saved in the file at the same time, but for some reason one of them resets in game (or, more likely, since they are both SAVED, it's not so much resetting, as fails to load).


Interesting. Yours looks very different from mine, obvious differences in 'Mech Bays and weapon groups notwithstanding:

Spoiler


Through deduction, using the information you provided plus knowledge of my own 'Mechs and their past and present builds:

Mech Order (from top):
BJ-1DC
BJ-1X
BJ-A
CPLT-K2
CPLT-A1
CPLT-C4
LCT-3M
JM6-DD
Trial ON1-K(C)
FS9-E
LCT-3S
LCT-1V


Weapon IDs
Small Laser: 1003
Small Pulse Laser : 1012
Medium Laser: 1001
Medium Pulse Laser: 1011
Large Laser: 1008
Large Pulse Laser: 1010
ER-PPC: 1006

SRM6 + Artemis: 1040
SRM2 ID: 1030
SSRM2: 1032

Machine Gun: 1024
AC/2: 1018
AC/5: 1019
AC/10: 1020


There are more than a few anomalies in mine:
  • The CPLT-A1 (has 6 SRM6+A) has not been in my inventory for almost a month.
  • I didn't change the weapon groups for the ON1-K(C) and none of the other Trials show up...including the one I did change the groups on (BJ-1(C))
  • My two Dragons don't show up at all.
  • My LCT-1M doesn't show up at all.
  • The JM6-DD has UAC/5 on it now, not AC/5
Long story short: my Weapon Groups XML is inconsistent with being up to date.

Edited by Yeonne Greene, 29 July 2014 - 12:35 AM.


#29 Infine

    Member

  • PipPipPipPipPipPip
  • 354 posts

Posted 29 July 2014 - 01:07 AM

Actually I'm starting to think that weapongroups.xml is not the only place the game takes grouping info from.
Because I recently made a clean one (to see what's happening with my groups), and the new one does not have groups for my Jenner, even though it's grouped correctly ingame. It will probably appear, if I change groups, but for now it takes info for it from somewhere else.

PS: Yes, it does store info on sold chassis.

Edited by Infine, 29 July 2014 - 01:08 AM.


#30 Y E O N N E

    Member

  • PipPipPipPipPipPipPipPipPipPipPipPip
  • The Nimble
  • The Nimble
  • 16,810 posts

Posted 29 July 2014 - 01:17 AM

Wouldn't surprise me. That is more likely where the issue is. Perhaps the info gets corrupted somehow and the game resets it as a fail-safe.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users