Why does a course quiz with 50+ random questions from pool fail when publishing to HTML5?

[Martin Guttinger]

When I publish my end of course quiz with 55 questions from a master question pool in HTML5, the question slides are generated and I can work through the questions, but when I try to submit, the result page does not show. I have contacted Adobe support three times already: The first time, the support person told me that I should not import questions from other pools into my end course project because that would corrupt the project, the second time I was told that my project is probably corrupt - period, and the third time I was asked to delete the quiz result page and then add it back. This solution works only if I preview the course in a browser, but as soon as I preview the course in HTML5 in a browser or publish it to HTML5 Captivate refuses to show the result page. Has anybody seen this problem before?

Configuration:

• Version: Captivate 9
• OS: Mac OSX Yosemite
• Non responsive project
• Publish to HTML5
• Shuffle answers, submit all, show progress relative, Show result at the end of the quiz activated, allow user to review quiz activated, Hide Playbar in quiz activated, If passing grade set to continue, If failing grade set to continue.

Can anybody help?

Thanks - Martin

[RodWard]

If you move your 55 questions out of the question pool and back into the main project flow, does it then work correctly?

If so, your issue would appear to be related to use of question pools in HTML5 and I would suggest logging this as a bug.

If not, your issue would appear to be related to having too many questions for HTML5 and I would suggest hiding question slides and test publishing to HTML5 until you find the practical limit of how many you can use.

[Martin Guttinger]

Thanks for your reply. I have been chatting with Adobe support a fourth time, and this time, they pushed me through to a Captivate expert, who could not reproduce the problem on his side, but on my box. He is investigating further to see what the issue is. I will update this thread when I hear back. There is definitely something weird going on. Interestingly enough, publishing to SWF works like a charm.

[RodWard]

HTML5 is intended mainly for mobile devices and they usually have a very limited amount of RAM available for e-learning.  I would not be surprised to find your course exceeds this limit and that could be the issue.  However, that would not explain why it was failing on a desktop using HTML5 unless the limitation is now built into the code or browsers somehow.