[rtext] Add option to load TTF fonts without anti-aliasing (LoadFontExBitmap) #5402
+51
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds optional support for loading TTF fonts without anti-aliasing, addressing issue #5385.
Fixes #5385
Raylib currently always loads TTF glyphs using
FONT_DEFAULT, which applies anti-aliasing.Pixel-style fonts such as Monogram become blurry when scaled or used in low-resolution UI.
This PR introduces a simple and non-breaking addition that allows users to explicitly request bitmap/no-AA font loading.
A shared internal function handles both AA and non-AA paths:
2. Existing APIs remain unchanged
LoadFontFromMemory()andLoadFontEx()still default to anti-aliasing:3. New public API for bitmap/no-AA loading
This function loads TTF glyphs using
FONT_BITMAP, producing crisp pixel-aligned rendering without smoothing.Usage Example
Visual Comparison