-
Notifications
You must be signed in to change notification settings - Fork 136
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
Export to PDF Broken on Warships. #1635
Comments
Can you post the log file? I think this might be the issue that was addressed in #1601 . Edit: To clarify, we need the logs from when you try to export a warship PDF. |
megameklab.log |
The logs are empty. |
Printing the Enterprise Super Carrier results in this exception (but a functional PDF), possibly because the RS is two-sided. One-sided WS like the Nightwing causes no errors.
|
Prerequisites and Pre-Issue Checklist
I'm reporting the issue to the correct repository:
MegaMek
MegaMekLab
MekHQ
I've tested the issue against at least the latest MILESTONE version
I've asked on the MegaMek Discord about the error
I've reviewed the BattleTech rules and MegaMekLab documentation, and I've confirmed that something isn't working as intended.
I've searched the Github tracker and haven't found the issue listed
Severity *
Low (Minor/Nuisance): Minor glitches or cosmetic issues that don’t affect gameplay and occur rarely.
Brief Description *
Trying to export a Warship Record Sheet to PDF results in a null point exception and if you attempt to print any warship record sheet after the fact it results in a a null point exception and gives you a corrupted PDF file that is unable to be opened necessitating Mega Mek Lab to be reopened to print a sheet succesfully.
Attempting to print without exporting prior results in the normal function of the process.
Steps to Reproduce
No response
Operating System *
Windows 10
Java Version *
11.0.17
MegaMek Suite Version *
v0.49.19.1
Custom MegaMekLab Version
No response
Attach Files
No response
Final Checklist
The text was updated successfully, but these errors were encountered: