Have the output settings been changed in Captivate 2017?
Projects that I publish to HTML from 2017 take a lot longer to load in a browser than similar sized projects that I produced in previous versions. When I look into the download speed it seems to be that the browser/s are taking ages to read the json files.
Could the json files be causing the projects to load slowly and if so how can I work around it?
How big is the project in terms of megabytes?
Hi Rod - it is happening to a broad range of projects from 5mb to 30+ it does not seem to be the size that effects the speed so much as the file type. The .json files just seem to make everything freeze up in the browser.
Since one of the later minor updates to Captivate 9 all HTML5 output now uses JSON files to deliver PNG or GIF files. JPG files are still delivered the normal way.
I have not seen any real issues with JSON files making output freeze or delaying playback unduly. If anything I think JSON tends to speed up the playback. The change to using JSON files was made because previously every single small PNG or GIF file required for the HTML5 user interface or content had to be requested separately from the LMS or Web Server. There can be hundreds of such files in a typical elearning module. With JSON there is only ONE file to request and that's why Adobe decided to go that route.
How did you establish that the delay or freezing is due to JSON?
Thanks for your reply. Your description of the move to JSON files all makes sense.
We established that the JSON might be a problem by using developer tools in Google Chrome and seeing what files take the longest to read.
If you are talking about the CPM.js file then that is the main file in the entire project that contains most of the data determining what goes where on which slide. It's usually the largest (non-video or audio) file in the project.