10367 replies to this topic

[ExoForce]

Mechwarrior 37, on 23 December 2018 - 08:50 AM, said:

Thanks, the only one I look at is the Gauss one.

Pro tip from somebody: map Gauss to all free weapon groups.
Now you have multiple weapon indicators for Gauss.

Edited by ExoForce, 01 January 2019 - 02:30 PM.

[Koniving]

Edit: Cleared double quote.

Mechwarrior 37, on 31 December 2018 - 06:11 AM, said:

Of the hero lights offered, if you have an ACH etc then go with the Grinner.

I have 3 KDK-3s, lol.

The only two I do not have is the Mauler and the Nightstar. I just do not see a good build with the NightStar. If anyone knows any, please let me know

If it was to me and my selection, the reason I didn't list it (though it otherwise qualified for the price range) is I already had the Grinner. (Its a must snag).

Mine uses ECM + Stealth armor...and is otherwise played like a Panther.
Why? Because its damn fun.
That's a Heavy PPC.

As for Nightstar, if you have tried these then: Think all the tanking advantages (and issues) of the 3F Stalker combined with the King Crab and the ability to actually use the arms (but with 2 fewer slots per arm to use).

So it tanks (and turns unfortunately) like a Stalker and walks and shoots like a King Crab.

I typically use a pair of ultra/5s or ultra/10s, some PPCs and some secondary weaponry for close in encounters when heat is a bit high.

Here's mine.

Top-left is my money maker.
Bottom left is my newest model.
Bottom right is boating Light PPCs to be chain fired.
Top right is ER medium lasers, Heavy PPC and twin RAC/5s. Heavy PPC's for the punch, RAC/5s for peppering enemies at 20+ damage/sec.
-------------------

ExoForce, on 01 January 2019 - 02:28 PM, said:

Pro tip from somebody: map Gauss to all free weapon groups.
Now you have multiple weapon indicators for Gauss.

That's actually pretty smart.

Edited by Koniving, 01 January 2019 - 03:23 PM.

[Mechwarrior 37]

OK, I'm trying to get a NightStar for my 2nd account now but the event page has not moved. I just did 1095 damage and 3 kills and no new loot bags. Thanks for the Nightstar builds.

I did the repair tool and I've had zero saving errors. However, my "loadout" bug is still there. I remember now I did delete and download a new version and it is still here. I've just learned to live with it.....


A good part of the time when I go to "loadout", that screen stays with me until I do this 3 step go thing to get rid of it.

[Tesunie]

Mechwarrior 37, on 02 January 2019 - 05:40 AM, said:

OK, I'm trying to get a NightStar for my 2nd account now but the event page has not moved. I just did 1095 damage and 3 kills and no new loot bags. Thanks for the Nightstar builds.

I did the repair tool and I've had zero saving errors. However, my "loadout" bug is still there. I remember now I did delete and download a new version and it is still here. I've just learned to live with it.....


A good part of the time when I go to "loadout", that screen stays with me until I do this 3 step go thing to get rid of it.

The event has ended, so you can now no longer earn any more loot bags. Thus, you can no longer earn the free mech.

As for the build error, it will remain until you correct whatever is causing the error. My best suggestion is to unequip everything from the mech, save and then rebuild your mech again completely. This should correct the build error, but also make sure that you don't have any extra armor nor consumables that you shouldn't be able to equip.

Q: Are you creating the build that is having the error code on it manually, or are you saving/loading your loadout? In this case, I'd do it manually... just to make sure it's good.


Only other suggestion I can say is to message PGI via E-mail through support (their E-mail addresses can be found by the Support tab in the forum header) and inform them of the issue. Let them know the build you are trying to save (screen shoot it), the error code it's producing, and what steps you've already tried to take to correct the problem. It might be something they need to fix on their end, or they might be able to guide you on what is going wrong and what you need to do to correct the issue.

[Reno Blade]

Tesunie, on 02 January 2019 - 07:18 AM, said:

The event has ended, so you can now no longer earn any more loot bags. Thus, you can no longer earn the free mech.

...

It seems the event page and the tournament page are different.
The tournament page shows 8h remaining today (as of now) for the stocking stuffer.

[Tesunie]

Reno Blade, on 02 January 2019 - 07:49 AM, said:

It seems the event page and the tournament page are different.
The tournament page shows 8h remaining today (as of now) for the stocking stuffer.

Yeah. I looked at the event page and saw it was "blank". I did think it was odd as I thought it ended today, but I also though "maybe it's from 12 AM (Midnight) 1/2/19"...

[Koniving]

Mechwarrior 37, on 02 January 2019 - 05:40 AM, said:

OK, I'm trying to get a NightStar for my 2nd account now but the event page has not moved. I just did 1095 damage and 3 kills and no new loot bags. Thanks for the Nightstar builds.

I did the repair tool and I've had zero saving errors. However, my "loadout" bug is still there. I remember now I did delete and download a new version and it is still here. I've just learned to live with it.....


A good part of the time when I go to "loadout", that screen stays with me until I do this 3 step go thing to get rid of it.

While I'm aware that there's a need for the resolution issue due to the computer and/or vision reasons, but one should at least run a wide screen 16:9 resolution if at all possible, I'm seeing a 4:3 resolution which is placing information on top of information on top of information, making it virtually impossible to see the actual loadout in the first place.

A resolution of 1280x720 will remove the user interface problems.

From there you should be able to actually see the loadout screen.
Though from making the same loadout, I have no issue. Check consumables, remake the loadout from a clean slate.

https://mwomercs.com...68#entry6205768
Stocking's back up.

[Mechwarrior 37]

Sorry, I used the word loadout when I meant weapons groupings or whatthefunkever.....THE FREAKING PICTURE!

Sorry, I'm in a lot of pain from my back atm....

[Mechwarrior 37]

I see a post that it is over, PGI just screwed up on telling the times.

It has been a hard holiday season for me...so just par for the course.....

[Tesunie]

Mechwarrior 37, on 02 January 2019 - 12:42 PM, said:

I see a post that it is over, PGI just screwed up on telling the times.

It has been a hard holiday season for me...so just par for the course.....

It's not over. Actually, they have now seemed to have given us another day to do it, probably because of the glitch. So you have even MORE time now to get that free mech. (PGI is normally good like that.)

[Mechwarrior 37]

The repair tool fixed my error problem. Does anyone really think I did not go over the builds 100's of times? It was not the loadout, it was a bug.


The weapons grouping bug is here to stay. I remember once deleting and reloading the game and same thing.

[Mechwarrior 37]

The error 52 is back. And it has to do with an Artillery Strike being loaded.

I have the empty slot and I can put an Airstrike, UAV or Cool shot there and save it.

If I try to put an Artillery Strike, the bug hits. It's not my load outs, it is a bug.

[Tesunie]

Mechwarrior 37, on 07 January 2019 - 08:00 AM, said:

The error 52 is back. And it has to do with an Artillery Strike being loaded.

I have the empty slot and I can put an Airstrike, UAV or Cool shot there and save it.

If I try to put an Artillery Strike, the bug hits. It's not my load outs, it is a bug.

Can you send me the build code, as well as the mech type/Chassis/variant? If I can, I'll see if I can replicate the issue on my side.

I will also need your current skill tree...

Edited by Tesunie, 07 January 2019 - 09:39 AM.

[Tesunie]

Mechwarrior 37, on 07 January 2019 - 08:00 AM, said:

The error 52 is back. And it has to do with an Artillery Strike being loaded.

I have the empty slot and I can put an Airstrike, UAV or Cool shot there and save it.

If I try to put an Artillery Strike, the bug hits. It's not my load outs, it is a bug.

Might be helpful: https://mwomercs.com...ode-52-on-save/

Striping the mech (and saving) and then manually rebuilding it seemed to fix the issue for many people. Another possible fix was placing a single component on (after striping the mech) and then saving after every change seemed to work for those that just stripping the mech didn't work for.

When if affected people who had the code toss up with consumables, it apparently happened to someone when the game thought they had 1 consumable in inventory, but they didn't actually have 1 in inventory to equip. They restarted their game, noticed it now say they owned 0 of said consumable, and then they paid for a new one (rather than trying to equip an owned one they didn't actually own). Problem was fixed for them.

Another possible fix someone else had was they removed one of the consumables in question (in their case a Coolshot) from another mech, and that cleared the code for the mech they were trying to place the consumable in the first place.

It appears that code 52 is an invalid inventory code. The game and your client/running program are in disagreement as to what you actually have in inventory. AKA: It's likely saying in your case that you "have" an strike in inventory, when you likely don't. Suggest removing the same consumable from another mech, and then go back to your problem mech and try again. It might fix the issue.

Another thread on the issue: https://mwomercs.com...-error-code-52/
This one addresses the issue with Consumables, but seems to say much of what was said in the previous thread (and what I summarized here).

Only other fix seemed to be to log out and then log back in... So you have some other possible things to try.

It is also presumed that the error might have to do with the Skill Tree, as another user experience the issue every time they took the nodes that granted the ability to hold more than a single type of consumable at a time. They fixed it by logging in and out...

[hordes1ayer2]

So I was a hardcore player a few years back but dropped off when my comp team fell apart and as Solaris came out I feel the game to be unejoyable. That there was too much going on and not enough players to be able to fill all that was offered. So I stopped playing and have started to come back to the idea of playing again. So I'm curious as to if this game is kinda dead. Is there still new players joined? Is the game worth going back to?

[Koniving]

hordes1ayer2, on 08 January 2019 - 01:19 AM, said:

So I was a hardcore player a few years back but dropped off when my comp team fell apart and as Solaris came out I feel the game to be unejoyable. That there was too much going on and not enough players to be able to fill all that was offered. So I stopped playing and have started to come back to the idea of playing again. So I'm curious as to if this game is kinda dead. Is there still new players joined? Is the game worth going back to?

New players are joining. We'll find out if they have any big plans in February when they start doing new road maps. This said most of their efforts after Solaris has been on MW5: Mercs. So, dunno what all will be going on here.

This said: Solaris is more or less dead; its got too many divisions making it hard to find players, and with so many events going back to back where the best way to get them is quickplay, quickplay and group queue are flooded, faction's kinda-there and Solaris is, well, dead-ish.

[Koniving]

MW5:Mercs is looking pretty good.
Some things that bug me which I'll quickly mod (PGI's "autocannon" Rifles instead of Battletech autocannons).
But this is more or less why development has stagnated on MWO for a bit.

[Mechwarrior 37]

Tesunie, on 07 January 2019 - 08:49 AM, said:

Can you send me the build code, as well as the mech type/Chassis/variant? If I can, I'll see if I can replicate the issue on my side.

I will also need your current skill tree...

Uh...how?

And also just time fixes it. I wait a few hours etc and just try again.

Edited by Mechwarrior 37, 08 January 2019 - 07:55 AM.

[Tesunie]

Mechwarrior 37, on 08 January 2019 - 07:54 AM, said:

Uh...how?

And also just time fixes it. I wait a few hours etc and just try again.

There would be two building codes I would need. In mechlab, select your mech (let me know what one it is, the code wont do that as easily). On the bottom right of your mechlab area (not the screen itself), you should see a series of blue buttons: Export, Import, Save and Load. Click Export and past that code here. It will look like a string of nonsense.

Then I would need your skill setup code. Same basic thing as with the loadout. Snag that Export button and paste that code for me.

With those codes, I'll be able to perfectly replicate your build and skill tree without any difference. I can then change out the strike as you've stated before and see if I have any issues. But, without those codes, I could create my version differently, which may "bypass" your problem, rather than having me see what the issue may be.

(I will make note, I am no PGI staff and I am only investigating this as far as a fellow normal player can. I can't say if I can replicate your problem, nor even if I can replicate it I can't say if I can offer any farther solutions.)

[Mechwarrior 37]

When and can you buy Clan Heros omnipods? As in the ShadowCat.