Forum Discussion
Missing Fonts (according to Storyline) but Fonts Exist in System
When opening my colleague's Storyline file, I get a message box (attached) telling me that the fonts listed are not installed on my PC. They are. I can see them in my fonts list and they are also in my Fonts folder. Once in Storyline, I can even select the font claimed to be missing from the Fonts menu. The problem is that it does not render it consistently or correctly. Is this a common problem and is there an easy solution?
112 Replies
360 SL Version 3.25.18009.0
And the font is available (similar to your image) on Windows control panel > Font.
Any fix to this yet? I submitted a ticket. SL states the "Imago book font" is missing.
Hi there, Cynthia. We had an issue with the "missing fonts" message appearing despite the font being installed in an earlier version of Storyline 360. We released an update that had resolved the issue at that point.
The original issue was only appearing in specific files. Was this file originally on another machine? Could you please test opening a new Storyline 360 project and attempt to use the Imago book font? If that works, please try importing the slides from the original project into a new project.
Let me know how you make out, and we'll determine if we have a new bug to squash. Thanks!
I see this was an issue in the past. I am getting the same Storyline error now stating that a font is missing. I know the font is there. Perhaps we need to re-open this ticket and solve this problem again??
Hi Curt, long time no see. :)
Lee
Hi there, Lee! I've opened a priority support case so our team can explore the error you're receiving. I'll follow the case as well so I can update the community discussion on what we discover. Thanks!
Nothing has changed. This is still very much an issue and I really need help to find a solution.
I would think this would be a priority to solve, but....
Hi Thaine,
That's definitely odd and I haven't run into the same issue using Storyline's latest update and the Velocity template. I'm curious if you could share the version you're using so that I can give that a test?
Also, can you check where the Font files are installed on your computer? They should be in the Font folder within your local Windows install. I'd also like to know if you're seeing an issue with any of the other fonts that are installed when Storyline is installed.
I've done everything on this thread and this is still an issue. I feel like this issue has continued from every iteration of Storyline and this is Still slowing me down. I've updated to Storyline 360, and the issue persists. I use all these fonts daily with no issue, except in Storyline.
You can see in my image that these fonts are clearly in my windows font folder, and yet here is the error message again.
Is there any solution for this issue?
I feel like Articulate says this is fixed in this update and yet here we are again...I find it very frustrating that this issue has been occurring for over two years and yet there is still no resolution.
What can I do to solve this? For real...
It seems like Articulate continues to suggest the same fix to a problem that really needs to be solved. It is getting to the point where I need to remove and reinstall the font every time I open a Storyline file from a different person.
I really wish we could simply solve this problem that is over 3 years old rather than offer a workaround that does not address the problem!
I've reinstalled these fonts at least 12 times, and this is now ridiculous.
Lee
Hi Lee,
I can understand how problematic and labor-intensive it is to reinstall the fonts, again and again, to deal with this issue. I know you've shared details with Cleo in your case, and I believe this issue to be different than the original one discussed here due to the limited number of customers experiencing it.
I've asked Cleo to share your case with our team of Senior Support Engineers so that we can dig in further to your font and the way in which files are shared to shed some light on this!
I found a workaround for this issue. When you see there is a missing font, it really helps to replace that font with a Web Font like Open Sans. Our odd fonts often don't display well in HTML 5. Once you open a file and you get the infamous Missing Font error message from Storyline here is a solution. Use the replace font tool in Storyline 360 to replace your font with a Webfont.
Here is an article on the process: https://community.articulate.com/series/74/articles/articulate-storyline-360-user-guide-how-to-replace-fonts
This isn't always an option. Often corporate branding guidelines specify the use of certain fonts. Also Open Sans was one of the fonts reported as missing in the initial comments.
THIS is STILL very much an issue even with the update to Articulate that came out on 12/17/19. Font (Arial) is installed on the PC with Windows 10 and the message pops up stating it's missing. Articulate just does not have a clue what's wrong, let's be real about that, one can see it from the same response over and over. There is no real resolution.
Hi Jacqueline!
I see that you're working with John, our Senior Support Engineer! You're in great hands!
I'm going to also share with him that you're seeing issues with the font in your courses so that he can help troubleshoot this issue.
I'll be following your case as I'm eager to find the culprit too!
Just to let you know, this is still an issue. I can't get Roboto to work. Any news on this?
Hi Simon!
Sorry, you're running into an issue with the font, Roboto! We're happy to help. I'd recommend connecting with a Support Engineer so they can offer their expertise to find the fix.
I'll keep an eye on your case to see what the solution is!
Still an issue 2 June 2021 - Helvetica showing as missing when it's not.
Is there a manual fix for this?
Hello Tim!
Are you seeing this with every project that uses the font, Helvetica or do other fonts that you have downloaded onto your local computer show up in the missing fonts window?
Would you mind also sharing which version of Storyline you are using? If you're using the latest version, Storyline 360 (Build 3.52.25156.0), I'll update my team to share this is still an issue in the most recent release.
