I have Rise courses that I have use the Storyline Block interaction to pull in Storyline quizzes. Rise requires that I pull in from Articulate Review. I can only publish Storyline to HTML5 out to Review.
When viewing the published Rise course, the Storyline Quiz has missing font characters. This has been an issue with my courses before and rectified using Flash>HTML5, but not option here.
Why is this happening? Can I correct this give the method I am using above???
So it seems I figured out that I was using the Modern Player, which limits output to HTML5. Switching to the Classic Player, I can now output to Flash with HTML5 backup.
However, the issue still remains that a font character is missing when publishing to HTML5.
Thanks for responding. The unfortunate thing is that would mean a global change to our IE settings for 16k+ learners and having our IT dept implement this. If this is the only solution, I can certainly request this, but if it is the only solution, that's a bummer. I will continue to publish to FLASH>HTML5 but have concerns when Flash is finally retired.
Thanks for the help...gives me some direction and ideas for planning.
It's the only solution today. Our team is working on a fix that's pretty in depth to change how the fonts will display if the output runs into the issues you're seeing. We'll let you know as soon as that fix is ready, but I don't yet have an ETA for it.
I'm having the issue with the font going weird. Tried publishing with flash>html5 but I get a new problem in that it auto scrolls the RISE page down to the SL block?
Try adding a continue button above the Storyline block in your Rise 360 lesson. The continue button will prevent the Storyline block from displaying until the user clicks to Continue after viewing the blocks above.
We are investigating an issue where the lesson will jump directly to the Storyline block when the Storyline interaction is published with Flash as the default output, and Flash Player is enabled in the browser. I'll tag this discussion for updates!
Thanks for the reply. I eventually solved the text issue by publishing as SCORM 2004 instead of SCORM 1.2. So I didn't need to publish as flash in the end.
8 Replies
Some additional information:
So it seems I figured out that I was using the Modern Player, which limits output to HTML5. Switching to the Classic Player, I can now output to Flash with HTML5 backup.
However, the issue still remains that a font character is missing when publishing to HTML5.
Hi Law,
If it's IE specific, take a look at the steps here to allow for the fonts to download. That should fix it!
Hey Ashley,
Thanks for responding. The unfortunate thing is that would mean a global change to our IE settings for 16k+ learners and having our IT dept implement this. If this is the only solution, I can certainly request this, but if it is the only solution, that's a bummer. I will continue to publish to FLASH>HTML5 but have concerns when Flash is finally retired.
Thanks for the help...gives me some direction and ideas for planning.
~L
Hi Law,
It's the only solution today. Our team is working on a fix that's pretty in depth to change how the fonts will display if the output runs into the issues you're seeing. We'll let you know as soon as that fix is ready, but I don't yet have an ETA for it.
I'm having the issue with the font going weird. Tried publishing with flash>html5 but I get a new problem in that it auto scrolls the RISE page down to the SL block?
Any ideas?
Hi there, Matthew. To confirm, it sounds like you're using Flash output in Internet Explorer to avoid font issues you're seeing in HTML5 output.
Try adding a continue button above the Storyline block in your Rise 360 lesson. The continue button will prevent the Storyline block from displaying until the user clicks to Continue after viewing the blocks above.
We are investigating an issue where the lesson will jump directly to the Storyline block when the Storyline interaction is published with Flash as the default output, and Flash Player is enabled in the browser. I'll tag this discussion for updates!
Thanks for the reply. I eventually solved the text issue by publishing as SCORM 2004 instead of SCORM 1.2. So I didn't need to publish as flash in the end.
This discussion is closed. You can start a new discussion or contact Articulate Support.