4 replies to this topic

[TASADAR101]

Ok, so this is from my own experience and thus if any one else has a idea as to the couse of this error than please post it here.

!st, this is to help explain a possible cause for the red error that appears.

2nd! this is for the solutions that have worked up until this point. (again from my experience )


1st, Possible causes:

1: Shader error ( An issue where as the shader file is currupt and some how messes with the loudout UI )

Fix: Download the MWO Repair Tool and run it.

Repair tool Link : http://mwomercs.com/...public-release/


2nd: overlapping slots : An issue with the UI where as the engine some how over writes slot space that is filled.

Fix: stripping mech of all equipment ( This one has not happened to myself but was suggested )


3rd: Engine purchases: The most commen for myself, the error appears after the purchase of a engine and some times after double heat sinks, stripping the mech doesnt work here, the issue is unknown and its fix is unknown thus there is something causing this error to happen after a purchase and install of said engine.



If any one else knows more possible causes of this error and or a fix to it or #3 please comment.

[Koniving]

Ammendment to #2.
Game combines elements from previous and new loadout. For example a random single heatsink sitting in a build upgraded to double heatsinks. A mech with both a standard and XL engine mounted in. A mech with 3 energy weapons in a body part that can only hold 2. A weapon that somehow mistakenly appeared somewhere.
Artemis and non-Artemis missile launchers mixed into the same build.

Problem #2 is typically caused when saving the loadout is followed immediately by further customization to the same mech. The result is a combination of new and old data when the game refreshes the old data and gets confused.

It can also be caused when the game itself does not correctly communicate the loadout changes due to whatever reason (usually related to wireless connections).

Another ammendment to #2.
A missing actuator is re-added after a fix or patch. For example the new Battlemasters variants were missing several actuators that got re-added, invalidating some builds.

See previous post for fix.

Edited by Koniving, 26 June 2014 - 03:12 PM.

[TASADAR101]

New Fix I found today for #3, Launch the repair Tool, run it, then after the Error's are fixed log back in stip the mech.

after stripping the mech attatch the engine,wepons and Ammunition.

checkout.

then add Heat sinks in and you should be good. worked for me and no items dissapeared.

[TheCaptainJZ]

#2 happened for me when using the strip button, then rebuilding the mech, but not saving inbetween. When I went to save the new loadout, it put some items back on that I had taken off from the original loadout. It was pretty easy to spot when you have a -1 ballistic or -1 energy. Simply dragging the extra item off and saving again worked. I think they may have fixed this bug with the strip command, but I'm not sure.

#3 sounds like the issue you might get when you do upgrades like endo steel and double heat sinks. If you are low on cbills, you can get into a situation like you have endo steel installed and you drop it for standard structure so you can add an xl engine and then put on double heat sinks. Then change your mind and try to switch back to endo steel structure but it says you don't have the cbills for it, even though that's what you originally had on it so instead of trying to buy it back, it should just drop the charge for switching to standard structure. All of this without saving. If this occurs, just back out of the mechlab, cancelling changes and go through one step at a time.

[Bigbacon]

modules might also be an issue. I had problems with a build yesterday, it would never save no nmatter what I tried. even stripping it down wouldn't fix it.

noticed I had advanced zoom on it, took off the module, and bam...i was able to save it now.