10 replies to this topic

[BraveInsanity]

So I've been having this problem for over a month now. I typed in Error 53 in the forum search and it came up with nothing so I thought I would enquire. Is there any fix or workaround for this? Has anyone else had this problem? Every time I go to load out some of my mechs it simply won't save, and throws me Error 53. This is frustrating as I have several builds saved and ready to use but I cannot get them to stick. All it says is please contact support if the problem persists. Some mechs it's not an issue, further adding to the mystery of the error. If anyone has any advice or workaround for this, I'd love to hear it. Thank you in advance.

*The only thing I've found on the forums tells you to restart your game, or relog. This does not work, and it has nothing to do with consumables.

Edited by BraveInsanity, 08 July 2022 - 04:25 AM.

[Skyler Enola]

I am having the same issue with the RGH-1C mech loadout too. just this one mech loadout has this error 53 issue.

[Tarl Cabot]

Strip the mech via STRIP button,, hit SAVE then add everything back in. At one point that specific mech you are having issues with, a desync occurred between the client and the server. Relogging rarely fixes the issue. Sometimes it is armor points, other times consumables and/or components, thus it is simpler to strip the entire mech with the STRIP option (this route ensures all items are stripped, not just what you are able to see) then make sure to hit SAVE button. Now add things back.

Edited by Tarl Cabot, 10 July 2022 - 07:07 AM.

[Relikk]

I'm having the same issue. I've reloaded.. relogged... stripped. saved. rebuild... smashed keyboard.

Error code 53. Anyone find any alternative workarounds?

[CadetCrayon]

Tarl Cabot, on 10 July 2022 - 07:05 AM, said:

Strip the mech via STRIP button,, hit SAVE then add everything back in. At one point that specific mech you are having issues with, a desync occurred between the client and the server. Relogging rarely fixes the issue. Sometimes it is armor points, other times consumables and/or components, thus it is simpler to strip the entire mech with the STRIP option (this route ensures all items are stripped, not just what you are able to see) then make sure to hit SAVE button. Now add things back.

This worked for me, Thanks a Bunch!

I had the Error 53 with my Raven, and stripping the mech of all armor and equipment - Note: I had no Camo or cockpit items on it.. Worked instantly!

[DragonVerity]

Tarl Cabot, on 10 July 2022 - 07:05 AM, said:

Strip the mech via STRIP button,, hit SAVE then add everything back in. At one point that specific mech you are having issues with, a desync occurred between the client and the server. Relogging rarely fixes the issue. Sometimes it is armor points, other times consumables and/or components, thus it is simpler to strip the entire mech with the STRIP option (this route ensures all items are stripped, not just what you are able to see) then make sure to hit SAVE button. Now add things back.

This worked for me thank you.

[HardDrive]

Tarl Cabot, on 10 July 2022 - 07:05 AM, said:

Strip the mech via STRIP button,, hit SAVE then add everything back in. At one point that specific mech you are having issues with, a desync occurred between the client and the server. Relogging rarely fixes the issue. Sometimes it is armor points, other times consumables and/or components, thus it is simpler to strip the entire mech with the STRIP option (this route ensures all items are stripped, not just what you are able to see) then make sure to hit SAVE button. Now add things back.

This worked for me as well. I exported the loadout I was trying to save, hit "Strip" And selected everything! Clicked Save, Then just simply imported what i was doing before and BOOM Saved without a issue.

Thank you!

[Jace Lancer]

Tarl Cabot, on 10 July 2022 - 07:05 AM, said:

Strip the mech via STRIP button,, hit SAVE then add everything back in. At one point that specific mech you are having issues with, a desync occurred between the client and the server. Relogging rarely fixes the issue. Sometimes it is armor points, other times consumables and/or components, thus it is simpler to strip the entire mech with the STRIP option (this route ensures all items are stripped, not just what you are able to see) then make sure to hit SAVE button. Now add things back.

stripping and saving worked for me, thanks.

[vtrickzv]

Had the same problem with my Mad Cat Mk 2 I got in an event, stripping entirely and saving worked for me though. Thanks so much!

[Ztrahd]

Tarl Cabot, on 10 July 2022 - 07:05 AM, said:

Strip the mech via STRIP button,, hit SAVE then add everything back in. At one point that specific mech you are having issues with, a desync occurred between the client and the server. Relogging rarely fixes the issue. Sometimes it is armor points, other times consumables and/or components, thus it is simpler to strip the entire mech with the STRIP option (this route ensures all items are stripped, not just what you are able to see) then make sure to hit SAVE button. Now add things back.

I know this is an old post but just wanted to say thanks, I was having this problem and this fixed it!

[Tarl Cabot]

Glad to be of assistance. This post may be old but it is still relevant at providing a resolution to that error 53!! There are older and newer posts but most of those do not have the Error 53 listed in the subject line or were posted in other subforums.