Can anyone assist me with this? Last week my project was previewing and publishing fine. Now, this is all I get when I preview and publish to a web server.
I have the same issue. When previewing locally the pre-loader keeps spinning and the course does not start. When Publishing it and upload it to Moodle or SCORM cloud I have the same issue. I tried switching browsers, disabling plugins and even a fresh installation of Adobe Captivate but nothing works.
Which version do you use?
I am asking this because AutoPlay has been turned off automatically for HTML output. Are you sure the webserver is supporting JSON mime type? Preloading setting are only valid for SWF output. Do you have heavy content on the first slide, like long audio clip, video?
Hi Lieve,
Thank you for getting back to me on such short notice,. I am using Captivate 2019. I have no heavy content such as video or such. I just created a menu and wanted to preview it. The odd thing is when I publish the file and preview it from another computer it works fine so the issue should be local I guess. However I have no idea where to look…
HTML output, like any website, is meant to be viewed from a webserver, not locally. I also had projects where locally viewing, even after publishing, was not showing the real output. Install a webserver on a system and test from it, best solution. I don’t bother anymore looking for causes in local viewing, just upload it.
Okay I will do that. However, when I preview the published version online in Moodle or SCORM cloud I have the same issue and the course will not load.
OK! Missed the real cause, which seems to be linked to the setup on your system. You told that the published version is working fine from another computer.
Difficult to guess. I know that in the past, corrupt fonts caused issues for Captivate. Maybe your profile is corrupt? Could you try to log in with another profile on your system to double-check if it is due to the profile or to the setup of the system?
Hello,
yes. I tried FF,Chrome and IE.
Which browser are you using, and has it been updated lately? Since it did work before, the origin of the problem has to be looked for in external changes. Did anything else change? Did you try multiple browsers?
You must be logged in to post a comment.
