Font I created will not load

A Font I created will not load. I get an error message saying it is not a valid font. This is only the second font I have created and the first one worked fine. Any help would be appreciated.

Not much we can test without the font project.

I am getting an error message when trying to install the font. It says it is not a valid font. This is only my second font I have created but the first one worked fine. Any help would be appreciated. See the font attached.
FONT2052-Regular.ttf (18.5 KB)

The font is a good old symbol font, but it has missing/incorrect naming fields. What software did you use to make it?

It works fine after opening it in the latest version of FontCreator and then exporting it.

Thanks for looking at it. Which naming fields are required? When I export it, it doesn’t load correctly. I get an error message saying it’s not a valid font.

FontCreator 14 ensures all required naming fields are included.

You have not told us which software you used to create the font.

I created the font in FontCReator 14.0 Professional. So how come one other person on this forum could export the font and it will load for them and I cant? That is the magic question and I really need to solve this issue ASAP.

Can you please send us the font project file, so we can try to reproduce it?

I don’t recognize the internal order of font data, so it must be made by an older version 14. Are you sure you are using the most recent update, currently FontCreator 14.0.0.2877?

In FontCreator select Help from the main menu and then click Check for Updates.

Yes its the most recent Font Creator version. Here is the font. It wont load on my computer. Again at a loss for how to fix it.
Font2052-Regular.ttf (18.5 KB)

The FontCreator project file with the *.fcp extension would be more useful.

Please provide reproducible steps how you ended up with this corrupt font, so we can look into this issue.

Here is the FCP font as requested.
Font2052-Regular.fcp (21.4 KB)

That reveals the issue is related to the autohinter. We have to look into it further, but for now just set hinting to No in the export settings.

That solved the problem Erwin, thank you!!!