I am running Captivate 2019 currently. I have created several eLearning projects over the last several years and they are updated every year or two depending upon our software updates. This content is primarily training content for our customers. Until now, I have been publishing the content as an exe file. With the dissolution of Flash, all of these materials are inaccessable. I have been looking through these forums to see how others are handling this and cannot seem to find what I need.
Is there a size limit to what these publications can handle? Is there something else that I need to try? Since I can't seem to figure out what is wrong, I really don't want to dump all of the older content and create it from scratch as I expect it won't work either.
Lastly, if any of you out there are creating content to sell to a customer, how are you distributing the HTML5 content? With the exe file, we were able to send the customer a link to download the content. How can we accomplish something like this with all of the seperate files created during the HTML5 process. I apologize, this part is completely new and foreign to me.
Thank you for any advice and guidance.
HTML5 content is designed to be delivered from a web server. There is currently no known replacement for EXE output. If your clients have access to the internet so that they can download your EXEs then in principle they should also be able to access the same content as HTML5. The difference is that they are not downloading a single file to their local hard drive or network in order to view the content. With HTML5 you 'consume' the content by watching it in the browser. The content is made up of scores if not hundreds of separate files on the web server that all need to work together for the content to play.
If you are having problems publishing projects to HTML5 and they won't complete, there may be some components in your project that are corrupted or incompatible with HTML5. I suggest you find the smallest one of these CPTX files, take a copy of it and play around with it to try and isolate the issue. Try hiding groups of slides and test republishing to HTML5 to see if you can isolate the slide or groups of slides that are causing the issue.