You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well, it is a MegaMekLab issue, but since it is an equipment problem so I post it here as the other equipment problems does.
For normal Battlemechs, If you change the engine to the large engine, it does takes the latter two critical slots on the below of Center Torso, and that's fine, but if you put any equipments on there before raise its speed, MegaMekLab does not kicks the existing slots and there is no additional engine space in the Center Torso.
For Superheavy Battlemechs, its additional slot on the engine is weirdly applied. As above, Superheavy also have a problem that does not kicks existing equipment slot. I think that it is better to put the last Engine slot just below of the Superheavy Gyro. Because Superheavy mechs are not able to choose the other types of Gyro, it seems not bad to set the fixed location when the mech is superheavy.
The text was updated successfully, but these errors were encountered:
Environment
Ver 0.47.0
Description
Well, it is a MegaMekLab issue, but since it is an equipment problem so I post it here as the other equipment problems does.
For normal Battlemechs, If you change the engine to the large engine, it does takes the latter two critical slots on the below of Center Torso, and that's fine, but if you put any equipments on there before raise its speed, MegaMekLab does not kicks the existing slots and there is no additional engine space in the Center Torso.
For Superheavy Battlemechs, its additional slot on the engine is weirdly applied. As above, Superheavy also have a problem that does not kicks existing equipment slot. I think that it is better to put the last Engine slot just below of the Superheavy Gyro. Because Superheavy mechs are not able to choose the other types of Gyro, it seems not bad to set the fixed location when the mech is superheavy.
The text was updated successfully, but these errors were encountered: