Can’t play the captivate output on chrome browser, Playbarscript.js is missing

June 14, 2018
Explorer 1 posts
Followers: 0 people
3

Can’t play the captivate output on chrome browser, Playbarscript.js is missing

Explorer 1 posts
Followers: 0 people
June 14, 2018

I can’t get my index output file to play from my computer in my local Chrome browser.

index_scorm.html will not play in browser; seems to be missing Overview\assets\playbar\playbarScript.js

I’m using Captivate 9.0.2.437. Help?

Comments (3)
2018-06-20 13:50:58
2018-06-20 13:50:58

Hi, Please try to perform the below steps and see if that makes any difference- - Uninstall Captivate 9 from your machine - Download the new build from the following link- https://adobe.ly/2FyNRyS - Unzip the downloaded file - Once you have unzipped the downloaded file, run the DMG file to install the new build and then launch Captivate and check the issue. Regards, Ajit

Hi,

Please try to perform the below steps and see if that makes any difference-

– Uninstall Captivate 9 from your machine
– Download the new build from the following link- https://adobe.ly/2FyNRyS
– Unzip the downloaded file
– Once you have unzipped the downloaded file, run the DMG file to install the new build and then launch Captivate and check the issue.

Regards,
Ajit

Like
2018-06-15 20:05:58
2018-06-15 20:05:58

Mac High Sierra Google Chrome 67.0.3396.87 (64-bit) The new project, with reporting not enabled, also doesn't play.

Mac High Sierra

Google Chrome 67.0.3396.87 (64-bit)

The new project, with reporting not enabled, also doesn’t play.

Like
2018-06-14 21:32:14
2018-06-14 21:32:14

Hi There, Please confirm which operating system you are using? Is it Windows or Mac OS? Also, try to create a new project and publish HTML5 (without enabling the reporting) and view it on Chrome and see if you are still getting the same error. Regards, Ajit

Hi There,

Please confirm which operating system you are using? Is it Windows or Mac OS?

Also, try to create a new project and publish HTML5 (without enabling the reporting) and view it on Chrome and see if you are still getting the same error.

Regards,
Ajit

Like
Add your comment