January 14, 2019
Preloading issue within Captivate
Comments
(8)
January 14, 2019
Preloading issue within Captivate
Newbie 9 posts
Followers: 2 people
(8)

Hi Everyone,

I’m having a problem with my Captivate HTML5 export. I have build an eLearning a few weeks ago and we are running it in Moodle. Now for new clients I wanted to show the eLearning offline on my laptop. I have done this many times with this same eLearning. When I export now, the eLearning stays preloading and nothing will start. I have changed nothing in my eLearning or export settings. I tried offline and online but still preloading. I’m watching in Chrome and the start screen contains a picture and text. So no video issue or what so ever.

I just started a blank presentation and went to preview and even this presentation stays within the loading screen.

Could anyone help me please?

8 Comments
2019-03-15 20:53:52
2019-03-15 20:53:52

Having same issues when I use Articulate with html5 it works just fine

Like
(1)
>
dtessier
's comment
2019-03-18 08:33:16
2019-03-18 08:33:16
>
dtessier
's comment

Articulate in the HTML wrapper?  Totally different from the full HTML output from Captivate. Always tricky to compare output from two totally different applications.  Your problem can be due to AutoPlay disabling, to webserver limitations (not supporting JSON) etc.

Like
2019-03-11 13:39:10
2019-03-11 13:39:10

I m having the same issue, html5 works locally, not online, stuck in the preloader (when publishing with elearning disable).
The answer from Adobe Help is as follows:

 

Abhigyan:

 
I apologise Rick, then you have to contact your IT team to get your content uploaded on your website, as I can help you to publish it through Captivate, but how to load it on an LMS or to load on a website the IT person would be able to help you with that.

¬¬

Then they were like, it might be that your server does not allow Json files… BS as my website actually uses Json and works fine. Bottom Line they have no idea and they wont help either.

If anyone have a solution, i will appreciate posting it here, Adobe wont be of any helps, as usual.

Like
2019-01-15 11:58:55
2019-01-15 11:58:55

I made a software update and now publishing and previewing works again. Only thing changed is that I first have to push a big play button to start. This I normally only had when viewing the eLearning on a iPad.

Other strange thing is that It speaks about a 2017 version while I have a subscription and on the Captivate site they talk about a 2019 version. I just updated my software but still it tells me it’s 2017.

Like
(1)
>
Vectar
's comment
2019-01-15 12:05:21
2019-01-15 12:05:21
>
Vectar
's comment

You have missed the long discussions about the disabling of AutoPlay. Browsers (Chrome started) tend to disable Autoplay for all websites, and eLearning plays always in a website. For that reason, since the second version of CP2017 AutoPlay is unchecked for all HTML5 output in Captivate. Now I know that you were using the first release of CP2017 

To make the experience better for the learner, have a look at:

https://elearning.adobe.com/2018/05/cope-autoplay-turned-off/

Like
2019-01-15 11:46:11
2019-01-15 11:46:11

I have always previewed my projects with no issues. Video would not work but when placed online it worked. But now when I start a blank project and hit “preview project” it doesn’t even run. I only see a preloader. Chrome was the best browser before that’s why i’m checking it in chrome but I have tried other browsers offline and online with no effect. From one day into an other it stopped working without touching the project or even working in Captivate.

Can’t publish or preview. Big projects, blank project it doesn’t matter. All fail.

Like
(1)
>
Vectar
's comment
2019-01-15 11:52:22
2019-01-15 11:52:22
>
Vectar
's comment

I don’t see the version you are using at this moment. Do you have the most recent one, which are:

10.0.1.285 for CP2017

11.0.1.266 for CP2019

Previewing locally depends, repeating, on both the course and the browser. I had several courses who didn’t display in any browser when viewed locally even after publishing, others did work in some browsers. Even if it worked in the past.

Since you mention more issues, I would recommend to clean the Preferences before tryiing again.

 

Like
2019-01-15 07:45:44
2019-01-15 07:45:44

HTML5 output is never meant to run offline. That was very easy in the past with SWF output, but not with HTML5 output. Locally viewing may work, on some browsers and in some circumstances but often security will prevent this. Did you try at least another browser?

Like
Add Comment