HTML5 export launching blank screen at beginning of published project

June 22, 2018
B.S. Computer Integrated Technologies, M.A. e-learning Design and Development, 10+ years as TD/ID in e-learning industry
Newbie 1 posts
Followers: 0 people
Sr. Technical Developer / Sr. Instructional Designer
4

HTML5 export launching blank screen at beginning of published project

B.S. Computer Integrated Technologies, M.A. e-learning Design and Development, 10+ years as TD/ID in e-learning industry
Newbie 1 posts
Followers: 0 people
June 22, 2018

Recently one of my colleagues upgraded Captivate to the latest release, 10.0.1.285, and since then whenever she publishes to HTML5 and then launches the index file the project starts  and pauses on a blank slide that is NOT part of the project.  After considerable testing of her instance, my instance and an instance from a 3rd user in our team I had her reload the previous version 10.0.0.192. The problem went away. I intern updated my version to 10.0.1.285 and am experiencing the same issue of the exported project launching and pausing on a blank screen.  Before I too return to the earlier Captivate version I wanted to reach out to the community to see if there is something that we need to do to 10.0.1.285 to force Captivate to publish the project as expected.

Comments (4)
2018-06-23 22:10:45
2018-06-23 22:10:45

Thanks for the post and the response. This is an issue we experienced.

Like
(1)
>
Shelly Gooden
's comment
2018-06-24 08:50:36
2018-06-24 08:50:36
>
Shelly Gooden
's comment

You’re welcome!

Like
2018-06-23 12:07:40
2018-06-23 12:07:40

CP2017, version 10.0.1.285 has disabled AutoPlay for HTML output, also for non-responsive projects. Reason: Chrome browser, recent version did disable AutoPlay, and it looks like this will e the same in the foture for other browsers.
You can make the experience more pleasant for the learner, by following the guidelines in this post:
https://elearning.adobe.com/2018/03/get-rid-white-start-screen-black-button-html-output/
You can also roll back to the previous version of 2017, to have a (temporary) solution and enable AutoPlay for desktop/laptops. It was always disabled for responsive projects, because many mobile browsers do not allow AutoPlay neither.

Like
(1)
>
Lieve Weymeis
's comment
2018-06-25 17:02:09
2018-06-25 17:02:09
>
Lieve Weymeis
's comment

Thanks Lieve, that explains a lot and will give my team the information they need to move forward. A little more work for each project, but we can work with that.

Like
Add your comment