Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems with cargo weights for combat vehicles under Transport section of Structure/Armor #492

Closed
assaultdoor opened this issue Feb 23, 2020 · 0 comments · Fixed by MegaMek/megamek#1726

Comments

@assaultdoor
Copy link

Using MML 0.47.4 on OS X with Java build 1.8.0_51-b16, there are a couple of issues with cargo weights set through the Transport panel of the Structure/Armor tab.

First, the tooltips of the various kinds of cargo (liquid, insulated, etc.) are misleading. For example, the tooltip on liquid cargo, for example, "Each ton provides 0.91 tons of capacity" sounds like if I set up a 1-ton bay, I've got 0.91 tons of liquid storage, which isn't the case. According to the Tonnage display at the bottom of the screen I've actually got a 1.5-ton bay with 1 ton of capacity, but according to Unit Validation > Unit Weight Breakdown I've got a 1.1-ton bay with 1 ton of capacity.

Second, MML rounds all capacity up to the nearest half ton. This means there is no way to get a one-ton liquid bay using that interface. Setting the capacity to 0.91 tons should work, but it is rounded up to 1 ton and I end up with 1 ton of liquid storage taking up 1.1 (or actually 1.5) tons on the unit. When I save a unit with a 0.91 ton bay, the resulting blk file shows a capacity of 1 ton. Also, when I make any changes to equipment through the Assign Criticals tab, the weights for cargo are automatically rounded up, so 0.91 turns into 1 ton.

I don't see anything in the Tech Manual about rounding the capacity of a bay to the nearest half-ton, and the vehicles I've looked at with liquid or insulated or refrigerated cargo bays don't round the weights at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant