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

[0.49.19] "Sorry can't save" + broken autosaves #4046

Closed
repligator opened this issue May 1, 2024 · 3 comments
Closed

[0.49.19] "Sorry can't save" + broken autosaves #4046

repligator opened this issue May 1, 2024 · 3 comments
Labels
Bug Duplicate Please list duplicate issue number in comments.

Comments

@repligator
Copy link
Collaborator

repligator commented May 1, 2024

Environment

[0.49.19], Linux, Java 17.0.10

Description

Playing a new campaign in .19. Started today, only a few hours in. I attempted to manually save and got an error message (apologies, I should screen-capped it) that said something along the lines of "Sorry, the game can't be saved, please submit a bug report". I closed and reopened mekhq. I was saddened to find that all of the auto-saves seem to be broken as well. I hadn't made a manual save yet. I was quite enjoying that campaign too. Is there any chance I can manually repair the save files>

All of the autosaves end in
<c3i_link link="
like they just got cut off somehow. I've attached the newest and oldest autosave, as well as the mekhq log.
Autosave-1-Lyran3067-30680822.cpnx.gz
Autosave-1-Lyran3067-30680818.cpnx.gz
mekhq.log

@kuronekochomusuke
Copy link
Collaborator

duplicate of #4034

A work around for this may be to regenerate bot forces to get one without any c3master, c3i, or nc3 units. Or just remove the scenarios until you get ones that save.

@gsparks3
Copy link
Collaborator

gsparks3 commented May 1, 2024

Think this is the same issue we found a little earlier: #4034

It looks like there is a workaround, but only if you can clear out the offending C3i units before saving or closing the program. If the units are in your own forces rather than enemy forces as for the linked issue, that's not good; every save you tried to make without just deleting the units would hit the bug.

@gsparks3 gsparks3 added Bug Duplicate Please list duplicate issue number in comments. labels May 1, 2024
@IllianiCBT
Copy link
Collaborator

Looks good in 49.20 -- the duplicate issue has been closed for a while. Closing this as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Duplicate Please list duplicate issue number in comments.
Projects
None yet
Development

No branches or pull requests

4 participants