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

[Issue] Unable to Customize units in the MekLab [50.02] #5814

Open
5 tasks done
Kromkar opened this issue Jan 18, 2025 · 2 comments
Open
5 tasks done

[Issue] Unable to Customize units in the MekLab [50.02] #5814

Kromkar opened this issue Jan 18, 2025 · 2 comments
Labels
Bug Parts/Repair/Refit Severity: Critical Issues described as critical as per the new issue form

Comments

@Kromkar
Copy link

Kromkar commented Jan 18, 2025

Brief Description *

When attempting to customize any unit (Mek, Tank, Infantry, Dropship) in the MekLab via the Customize right click menu in the hangar, an uncaught exception error is thrown and the unit is not placed into the MekLab, nor does the MekLab tab appear.

3. Steps to Reproduce

  1. Right click any unit in Hangar
  2. Click "Customize", then "Customize in MekLab"
  3. Get an Uncaught java.lang.IndexOutOfBoundsException detected error

Attach Files

Issue Files for Cannot Customize Unit in Meklab.zip

Severity *

Critical (Game-breaking/Crash): The game crashes or a core feature (like saving, loading, or network connection) is completely unusable.

MekHQ Suite Version *

MekHQ v0.50.02

Operating System *

Platform: Windows 11 10.0 (amd64)

Java Version *

Java Vendor: Eclipse Adoptium     Java Version: 17.0.12

Final Verification

  • I confirm this is a single, unique issue that hasn't been reported before
  • I have filled and provided all necessary information above
  • I have included any and all logs, custom units, and CPNX (save) files
  • I have asked on MegaMek Discord about this issue
  • I have confirmed this issue is being opened on the correct repository: MegaMek, MegaMekLab, or MekHQ
@Kromkar
Copy link
Author

Kromkar commented Jan 19, 2025

Update: Did some testing today. If I make a new campaign, this issue does not occur, so it's likely related to save migration issues from 50.00 to 50.02

@Kromkar
Copy link
Author

Kromkar commented Jan 19, 2025

On attempting to export the Campaign Subset (all units, personnel, etc.) in an attempt to circumvent this issue after confirming it doens't exist in a new campaign, it failed. I presume this is likely related.
mekhq.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Parts/Repair/Refit Severity: Critical Issues described as critical as per the new issue form
Development

No branches or pull requests

2 participants