Answered by
rh101
Feb 17, 2026
Replies: 5 comments
|
When creating a new issue, there should be a template option named "Bug report", with some information you should fill out. It looks like this: Please always use the template when creating a bug report, since it reminds the poster to fill in some required info, such as the version of Axmol being used. |
0 replies
Here is a link but only works for 3 days |
0 replies
If certain file extensions are not allowed, then try archiving (with ZIP or such), and you may be able to attach that. You could also just create a repo in your own github account, upload a test project to it (or just the font), and link it in your post. |
0 replies
0 replies
Answer selected by
halx99
|
Very nice. Thank you! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment



The corruption occurs at multiples of 10, so 10, 20, 30 etc. etc.. The reason seems to be that the
PixelHallfeticaJP10P-Regular.ttffont file contains bitmap fonts for those sizes. It doesn't seem that Axmol handles the case of bitmap fonts embedded in TTF files.You can see the bitmap fonts contained in it when loading in FontForge:
If you delete the bitmap fonts from the file, and save it back out, then not only does it fix the issue, but it also reduces the file size from 16MB to ~1.4MB. The file with the bitmap fonts removed is in this archive:
PixelHallfeticaJP10P-Regular.zip