After creating a font through the content browser, and importing my chosen font (Akzidenz Grotesque), the font renders fine in the preview window, but in the game/on the HUD it appears to crop some letters at the bottom and the right. I’ve tried playing around with the “Extend box” settings, and the “x & y padding” values, but with no success.
Thanks,
I too have a Custom Font which renders with cut offs, but renders fine in preview. I hope someone can help.
Hey Ineni,
Thanks for your report! Have you been able to reproduce this issue with any of the fonts included in Rocket? They are located in the /Engine/EngineFonts/ folder. Also, are you seeing this issue with just a blueprint using a TextRenderComponent in the world, or is this specifically when working with a HUD? Could you provide a screenshot as well, just so we are on the same page as to the issue you are seeing.
Thanks!
-Steve
Hi Steve,
Engine fonts appear to be fine - we haven’t had any issues with the default “RobotoDistanceFIeld”, both on the HUD and in a textrendercomponent.
I was mistaken in my first post - the node being used in the HUD isn’t a “text render component” but instead is “draw text” (image attached).
Also attached is a screenshot of what we’re seeing. If you look at the base of some characters (the ZERO’s for example) you can see it missing the bottom pixel. Additionally I suspect some of the right hand side of each character is being cut off because the kerning is a bit strange.
Also attached font preview window - we can see the 0’s render fine here.


Hello again,
We have tried to repro this issue again with some of our own fonts but are still unable to reproduce this issue. We would like to attempt to reproduce this issue with the font/font asset you are using–would you mind posting a new thread in this section, checking the option to make it only visible to support staff, and attaching your font’s .uasset or the raw font file? You can include a link to this thread in that new question as well.
Thanks!
-Steve
Hello everyone,
Just wanted to provide an update that we were able to reproduce this issue internally and have implemented a fix. We expect that fix to be included in the next Rocket Beta release.
Thanks!
-Steve