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

Status message about unallocated heat sinks is confusing #770

Closed
NimoStar opened this issue Sep 22, 2020 · 1 comment · Fixed by MegaMek/megamek#2320
Closed

Status message about unallocated heat sinks is confusing #770

NimoStar opened this issue Sep 22, 2020 · 1 comment · Fixed by MegaMek/megamek#2320
Milestone

Comments

@NimoStar
Copy link

NimoStar commented Sep 22, 2020

Fission Engine in my IndustrialMech tells me I can't have over 3 heatsinks there. Yet the interface will not let me have less than 5 heatsinks, thus always invalid. Clicking the down arrow doesn't remove heatsinks below 5. Changing the model to Fission always sets heatsinks to 5 at very least - 2 above its own set "Maximum"

I am guessing it's suppossed to have 5 internal heatsinks and the limit is a misstep (carries over from ICE).

This also has to do with just 1 movement so lower engine ratings.

Environment

47.10 win7 64 bits

Description

2020-09-22 20_16_40-Panoplas Demolisher mtf

@NimoStar
Copy link
Author

Nevermind, I think you need to assign those heatsinks in the chassis. Perhaps the error should be "Unassigned heatsink equipment locations" (as it is with other unassigned equipment) and not "too many engine heatsinks", which makes you believe you need to lower them, which you can't.

@neoancient neoancient added this to the Stable 0.48 milestone Oct 3, 2020
@neoancient neoancient changed the title Fission Engine 5 unremovable heatsinks with 3 as valid limit in Industrialmech (47.10) Status message about unallocated heat sinks is confusing Oct 7, 2020
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.

2 participants