-
Notifications
You must be signed in to change notification settings - Fork 68
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
Big bn::sprite_font
exceeds compiler operation count limit for duplication check
#19
Comments
I'm working on a new font system that stores the UTF-8 characters map in ROM without character limits. I have tested this new font system with a korean font with more than 2400 UTF-8 characters and it seems to work fine, but it would be great if I could test your fonts too. In the examples you have posted I can't find the 3 files needed to create a font ( Could you link them? Thanks. |
I think op put them on the
|
I'm blind :) Thanks. |
That's great. I also have the same idea when I find that they are all loaded to WRAM at once, which is inefficient and consumes much time and space.
Yes, you are right. |
Sadly, I have to break compatibility with old I'll push a Butano 9.0.0 prerelease soon with the new API. These header files have been updated to it: sprite_font.zip |
Could you please push it to a branch first so that I can merge it to mine directly? Thanks a lot. |
Here's your branch: https://github.com/GValiente/butano/tree/utf8_characters_map |
I find the changes on that branch are already on master, so I can merge changes from master directly instead. |
Test with 25000+ characters in 46055a0 and it works fine.
|
butano/butano/include/bn_sprite_font.h
Line 121 in 0e5c422
It exceeds compiler operation count limit here for big
bn::sprite_font
with thousands of utf-8 characters.butano/butano/include/bn_sprite_font.h
Lines 200 to 213 in 0e5c422
The double
for
loop here may need optimization to reduce operation counts.Examples:
Chinese font with 3500 chracters
Japanese font with 1945 characters
Fonts:
c1b8906
Errors:
Note: This issue is opened according to #18 (comment).
The text was updated successfully, but these errors were encountered: