Launcher Stalls, does launch output web project

Feb 05, 2014

Storyline 1.05

When publishing a project as a Web output including HTML5 and Mobile Output. The project will work perfectly if the destination is the same folder as the Storyline source file. However when selecting an alternate publish location or copying the output folder to another location the Launcher.html file will no longer execute and pop-up the project. 

The launcher hangs on the initial windows with the orange Launch button displayed. The project will launch from the appropriate story.html or story_HTML5.html file. Although it will pop-up an activeX warning after accepting it the presentaiton will play leaving all of the menu's and toolbars visible :(

Can someone point me in the right direction to fix this problem?

7 Replies
Ashley Terwilliger-Pollard

Hi Timothy,

I'm not sure I'm following where you'll be hosting your published content - if you need users to access it from a local drive, yes you'll want to publish for CD. Are the keyboard triggers you're referring to set up within data entry fields? That is a known issue described here. 

If you do need to host your content on a web server, there are a few options mentioned in this article where you could host the content such as in a public Dropbox folder. 

If you're having difficulty with other triggers within your publish to CD output that work fine otherwise in the web publish set up, are you able to share your .story file with us? If you'd prefer not to share it here in the forums I can send you directions on how to share it with me privately. 

Timothy Smith

This must be hosted locally (no network access) for many of our presentations as well as online. When attempting to host this locally the tested and proven triggers for keyboard actions simply do not work when launched from the .exe edition. Any keypress during the presentation has very unpreditible results or not action at all. 

I would love to share the file, however due to corporate confidentiality of the content and intellectual property restrictions I can not share the file here.

This discussion is closed. You can start a new discussion or contact Articulate Support.