https://helpx.adobe.com/captivate/kb/captivate-responsive-courses-not-autoplay-browsers.html#

Both of the fixes worked for me, but I’m developing a lot of modules. Applying these fixes post-publish introduces a lot of risk and extra work over time. Does anyone think there’s a way for me to make an adjustment in Captivate (or my Program Files) to publish with this code in the output already (rather than applying every single time I publish)?

After publishing, look for file named index_scorm.html and in “function initializeCP” function there will be cpInit();, add an additional function to be something like these:

cp.DoCPInit();
var lCpExit = window[“DoCPExit”];
window[“DoCPExit”] = function()
{
if(cp.UnloadActivties)
cp.UnloadActivties();
lCpExit();
};

if( window.CPYTAPINeeded )
{
var tag = document.createElement(‘script’);
tag.src = “https://www.youtube.com/iframe_api”;
document.getElementsByTagName(‘head’)[0].appendChild(tag);
}
}

cpInit();
cp.movie.play(); (add this line)

initialized = true;
if(isLivePreview() === true)
{
cp.previewFolder = window.location.href.split(“\/”)[4];
setInterval(isLivePreviewDirty, 1000);
}
}

Save and upload (or compress and upload).

Easy way to circumvent Adobe mess up

Just to be clear. This IS a Captivate issue. Not a browser issue. You can publish a Storyline course with video/audio on the first slide and there is no issue.

I found were they made the change. Its in the assests>js>CPM.js file

Look for the following code:

a.passwordAccepted && !a.completed && (a.completed = !0, a.responsive && a.adjustResponsiveItems(a.ReasonForDrawing.kRegularDraw), a.fireModuleReadyEvent(a.currentWindow), a.autoPlayNeedsUserClick() ||
a.D.project_main.autoplay && (a.currentWindow.cpAPIInterface && a.currentWindow.cpAPIInterface.canPlay()) && a.movie.play())

Replace with

a.passwordAccepted && !a.completed && (a.completed = !0, a.responsive && a.adjustResponsiveItems(a.ReasonForDrawing.kRegularDraw), a.fireModuleReadyEvent(a.currentWindow), a.device == a.DESKTOP && a.D.project_main.autoplay && (a.currentWindow.cpAPIInterface &&
a.currentWindow.cpAPIInterface.canPlay()) && a.movie.play())

It works for me

For us, the missing autoplay also is a great problem. We implement HTML5-exports of captivate in an LMS, but we do not use scorm, we just implement the html5. we usually build small modules. Now the user has to select EVERY module in the LMS followed by another stupid click. Some time ago there were “hacks” to remove this page and the click … anyone experience with that? How can the click be removed from the exported file? I will even pay for a solution! the objective is: Get rid of the click (a poster image does not help, becaus I still oblige the user to click). Please help.

You can’t have AutoPlay enabled for HTML output anymore due to decisions like by Apple and Chrome. You can only make the experience bit better by using the workflows I described here: https://elearning.adobe.com/2018/03/get-rid-white-start-screen-black-button-html-output/

How do you disable this. I have content that stops at first slide. Why am i making my users press another button…

Hi Teresa,
We have published a blog on this,
https://elearning.adobe.com/2018/05/captivate-responsive-courses-will-not-auto-play-browsers/
Thanks,
Saurav

Sorry I did not see you answer, however you are missing my point. I do not have audio or anything else that is autoplaying. It is a menu, so every time user gets to menu they have to click to continue. Then click a menu item. Also, if the browser wants to block it so be it, why is Adobe making an assumption about every project to disallow Autoplay.

Already answered your question on the forums. You know that the reason is due to some devices not allowing AutoPlay (and not Audio playing automatically neither). It is not totally fair to blame Captivate for decisions by other companies. I will always add a poster image and replace the play button to fit in with the course. Sometimes I am very annoyed on websites where a video or audio start playing without my control but that is of course a personal opinion.

Does anyone else see this Autoplay issue as a problem. I built a menu in captivate, that launches lessons. So now everytime a user goes back to the menu to select another lesson, they have to click a button to play the file first. I do not have audio or animation so there would be no reason why the browser would force it to autoplay. I am getting more and more frustrated with captivate as an elearning tool. I am going back to developing my menu in html and launch captivate built lessons. This is adding so much more time to my development. The lessons still have the annoying Autoplay issue but at least it is not everytime they go to menu. Also this means my menus will not have same interface as lessons because I used HTML scalable feature in captivate. There needs to be some kind of work around for captivate projects that do not have audio and animation, like my menu.