Font Issue html5

anonymous_user_40af95701 · January 18, 2017, 9:44pm

Hey, I have an issue with an imported font. The font-size in the html5(firefox/chrome/safari) build is screwed up (to small see the screenshot). The font works fine in the standalone build!. I created an example project (blank template) to show and reproduce that issue.

You can clone the project from GitHub under the following Link:

I use Version: 4.14.3-3249277+++UE4+Release-4.14 | macOS Sierra 10.12.2 .

I hope you can reproduce that issue with the demo project.
Thank you for your help.

anonymous_user_e729f54e · January 19, 2017, 6:27pm

Hello solidbot,

I was unable to reproduce this issue on our end. I have a few questions for you that will help narrow down what issue it is that you are experiencing.

Quick questions:

Can you reproduce this issue in a clean project?
If so, could you provide a detailed list of steps to reproduce this issue on our end?
Could you provide screen shots of any widgets/blueprints/settings that may be involved with this issue?

Note: There is a known issue in 4.15 preview dealing with custom fonts reverting back to the default font when packaging. Could you check to make sure this is not the case for you?

Link: Unreal Engine Issues and Bug Tracker (UE-40855)

anonymous_user_40af95701 · January 19, 2017, 10:41pm

Hello ,
Thanks you your reply.
Can you please use this font to reproduce this tissue?

Yes, I reproduced that issue in a clean project, for that reason I created a project and you can download it on Github under the following link: GitHub - solidbot/ue4fontissue

First I add a new font and add the downloaded fontfile to the font.
I just create a Widget with a textblock and change the size to 36px.
In the next step I added a new gamemode and add the widget to the viewport.

thanks for your help and I hope you can reproduce the issue.

anonymous_user_e729f54e · January 24, 2017, 6:12pm

After further testing I was able to reproduce this issue on our end. However, I also tested this on an internal build. It appears that this issue has been resolved and the solution will be available in a later release of the engine. My test results suggest that the issue linked above had the same root cause as the issue on this thread.

Make it a great day