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

NPE: Advance Day stuck #2427

Closed
HomoLiberatorus opened this issue Feb 18, 2021 · 4 comments · Fixed by #2430
Closed

NPE: Advance Day stuck #2427

HomoLiberatorus opened this issue Feb 18, 2021 · 4 comments · Fixed by #2430
Assignees
Milestone

Comments

@HomoLiberatorus
Copy link

MekHQ 0.47.17
Windows 10
Java 11

When clicking the Advance Day button, the day doesn't advance along the top of the screen.
The Daily Activity Log does show a day advance but only appends the log directly below the previous day.
13241

I have no idea how to reproduce this. It does work as intended after loading a save in my experience, but, when it happens, clicking on "Advance Day" would simply continue to write in the activity log in the same way. (and write more of the same NPEs in the mekhqlog.txt)

Lucre Lancers30200313.zip
Save file inside. No customs.
megameklog.txt
mekhqlog.txt

@HammerGS
Copy link
Member

Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
	at mekhq.campaign.parts.Part.getQualityName(Part.java:257)
	at mekhq.campaign.Campaign.doMaintenance(Campaign.java:6358)
	at mekhq.campaign.Campaign.processNewDayUnits(Campaign.java:3273)
	at mekhq.campaign.Campaign.newDay(Campaign.java:3411)
	at mekhq.campaign.CampaignController.advanceDay(CampaignController.java:82)
	at mekhq.gui.dialog.PersonnelMarketDialog.lambda$initComponents$1(PersonnelMarketDialog.java:258)

@HammerGS
Copy link
Member

Also lots of errors like this:

10:26:08,393 ERROR [megamek.client.ratgenerator.RATGenerator] {AWT-EventQueue-0}
parseModelNode(), line 1054 : Jump Platoon (GL) not found.

10:26:08,409 ERROR [megamek.client.ratgenerator.RATGenerator] {AWT-EventQueue-0}
parseModelNode(), line 1054 : Peregrine (2969) not found.

10:26:08,493 ERROR [megamek.client.ratgenerator.RATGenerator] {AWT-EventQueue-0}
parseModelNode(), line 1054 : Jump Platoon (GL) not found.

10:26:08,509 ERROR [megamek.client.ratgenerator.RATGenerator] {AWT-EventQueue-0}
parseModelNode(), line 1054 : Peregrine (2969) not found.

10:27:21,858 ERROR [mekhq.module.atb.AtBEventProcessor] {AWT-EventQueue-0}
addRecruitUnit(), line 225 : Personnel market could not find BattleArmor for recruit from faction FS

10:27:24,559 ERROR [mekhq.module.atb.AtBEventProcessor] {AWT-EventQueue-0}
addRecruitUnit(), line 225 : Personnel market could not find ProtoMek for recruit from faction LA

10:27:24,559 ERROR [mekhq.module.atb.AtBEventProcessor] {AWT-EventQueue-0}
addRecruitUnit(), line 225 : Personnel market could not find ProtoMek for recruit from faction FS

10:27:33,544 ERROR [mekhq.module.atb.AtBEventProcessor] {AWT-EventQueue-0}
addRecruitUnit(), line 225 : Personnel market could not find BattleArmor for recruit from faction FS

10:29:52,025 ERROR [mekhq.module.atb.AtBEventProcessor] {AWT-EventQueue-0}
addRecruitUnit(), line 225 : Personnel market could not find BattleArmor for recruit from faction ARC

10:29:52,025 ERROR [mekhq.module.atb.AtBEventProcessor] {AWT-EventQueue-0}
addRecruitUnit(), line 225 : Personnel market could not find ProtoMek for recruit from faction TC

10:30:45,682 ERROR [mekhq.campaign.parts.Refit] {AWT-EventQueue-0}
calculate(), line 490 : null missing part for Cargo Bay #1 during refit calculations

10:33:27,361 ERROR [mekhq.module.atb.AtBEventProcessor] {AWT-EventQueue-0}
addRecruitUnit(), line 225 : Personnel market could not find BattleArmor for recruit from faction LA

I'll look into the unit errors.

@sixlettervariables
Copy link
Contributor

sixlettervariables commented Feb 19, 2021

That part error means either:

A. There is no campaign object for the part, or
B. There are no campaign options for the campaign

Both of which I did not believe was possible.

@sixlettervariables
Copy link
Contributor

I can't seem to reproduce this with the provided campaign. Perhaps a save-reload fixes this very odd corner case.

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

Successfully merging a pull request may close this issue.

3 participants