8 replies to this topic

[MrMadguy]

Really. I was ok about it in the past, but now I have 17 mechs and...I wanted to play the game for about an hour today, but all this time was wasted while remembering, fixing and testing all messed weapon groups. Do you understand, that user data corruption - is very bad thing in terms of online game development? Could you find the way not to mess up weapon groups (and sometimes loadouts) with patches?

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

[Raimir]

I agree with you. It's mind blowing

[Kaosity]

They have to do this each time they add/delete a mech from the game because they have to add/delete the mech info from your user profile weapongroups.xml file (local on your machine). Easiest way for them is to start with a new file. If you look at this directory after a patch but before loading the game you will notice that all the other XMS files were updated, but not weapongroups.xml. After your first game load you will have a new file. Try saving the old one and then comparing it with the new one and you will see what I mean... new info at the bottom of the new file when they add a mech.

[ollo]

WhenReaperComes, on 02 April 2014 - 10:28 AM, said:

They have to do this each time they add/delete a mech from the game because they have to add/delete the mech info from your user profile weapongroups.xml file (local on your machine). Easiest way for them is to start with a new file. If you look at this directory after a patch but before loading the game you will notice that all the other XMS files were updated, but not weapongroups.xml. After your first game load you will have a new file. Try saving the old one and then comparing it with the new one and you will see what I mean... new info at the bottom of the new file when they add a mech.

Wait, you say that this file is NOT updated by the patcher, but instead they chose to leave it untouched at first, then load the information and afterwards scrap it just to add some dummy weapongroups? So the program designed to actually use and update the stored data WILLINGLY DESTROYS IT?

On second thought, yeah, sounds exactly like the style of logic we know from this shiny pillar of software engineering called PGI.

[MrMadguy]

Nice. Weapon groups on 3-4 mechs (my favorite ones of course), I've fixed first yesterday, now being reseted after every match. Why PGI have, and always had, so bad UI design? Remember this terrible mechlab UI in previous MW games? Don't you think, that it's time to fire your UI/system designer and hire new one?

I don't think, that it's connected with addition of new mechs, cuz new mechs are being added very often and this thing happens much less often. Another thing, that I've noticed, is that loadouts (i.e. order of weapons) is being messed up with this patches too. I guess, it's somehow connected with some bugged server-side script, that updates mechs' loadouts after applying some changes to mechs. As I already said, this script messes up weapons' order (noticed this on my JMG-DD) which leads to the situation, where weapon order no longer matches order, saved in weapon groups. And of course instead of fixing this terrible bug, that corrupts user data, PGI choses to simply reset weapon groups every time it happens. Yea... What can we demand from them, if they still can't even implement game mode user choice saving? Lol...

[MrMadguy]

Great. When I'm fixing messed weapon groups on one mech - they messing up on some another. Game unplayable, so I'll better quit it to save my nerves, till this terrible bug won't be fixed. I don't want to waste an hour fixing this data every time PGI decides to corrupt it. I just can't understand, why can't they save all this settings on server side? Anyway, UI 2.0 design is terrible, cuz I have to use web-mechlab in order to design my loadouts. Cuz game's mechlab is far too uninformative.

[rolly]

HEAR HEAR. My mech list is getting up there and lo and behold this patch messed up all of them. The USER config settings are in a different folder, I see no reason why to mess it up again and again. Unless they're planning to monetize that too...

MrMadguy, on 03 April 2014 - 09:12 AM, said:

Great. When I'm fixing messed weapon groups on one mech - they messing up on some another. Game unplayable, so I'll better quit it to save my nerves, till this terrible bug won't be fixed. I don't want to waste an hour fixing this data every time PGI decides to corrupt it. I just can't understand, why can't they save all this settings on server side? Anyway, UI 2.0 design is terrible, cuz I have to use web-mechlab in order to design my loadouts. Cuz game's mechlab is far too uninformative.

But don't worry, the CEO say's the UI 2.0 is fine. So it MUST be fine. Same goes with the mechlab. Nevermind the fact that its ergonomically defunct and woefully inadequate for conveying essential information.

[MrMadguy]

Yea, I don't know, how to explain it, but this is how it works:
1) When I'm fixing weapon groups on my Jester and Pretty Baby (relog after this and check groups - they are saved properly) - weapon groups on AWS-8Q and AWS-8R are being messed up.
2) When I'm fixing weapon groups on AWS-8Q and AWS-8R - weapon groups on Jester and Pretty Baby are becoming messed again.
All other mechs seem to be ok.

[MrMadguy]

Hey. Is anybody going to fix this bug? I've done even further researches and have found, that my Jester "shares" his weapon groups with AWS-8Q and my Pretty Baby "shares" his weapon groups with AWS-8R. "Shares" means, that as soon as I change weapon groups on one of them - they're messed up on another. So, I guess, there is something wrong with mechs' IDs. IDs are messed up and some of my mechs has shared IDs now?

P.S. I've wasted another hour of my time to totally recreate all weapon groups (i.e. deleted weapongroups.xml and configured all groups from scratch) - it haven't helped.