It looks like you're viewing the course in HTML5. Is that right? Do you have any options selected for modifying the browser window size for your course?
If so, you may want to take a look at the information below and the full chart for HTML5 support:
Please note that If I setup storyline to create a launch page and open scorm in new window nothing changes.
The launch page doesn't appear. Is this a bug or I'm doing something wrong ? See my configuration in the image below.
If I change the manifest of the generated scorm in order to force loading the launch page, it works and the margin problems disappear. In this way everything seems to be ok. BUT......... my LMS (Docebo) stop tracking the course.
Hmm. Looks like it may be a combination of things. It may be best if we can take a look a the files and test it on our end. Are you able to share the project with us, so we can see what may be causing this? You'll be able to attach the .STORY file on the second page of the following form:
Please be sure to include a description of your issue. Please also include the URL for this thread in the form. Also, please share the case number with me. You're welcome to do so here, or in a private message. This way I can follow the progress of the case and update this thread.
SCORM Cloud works well. The issue is we are using Docebo and it resizes the elearning player and content to be quite large. Can't seem to find a setting that changes this
12 Replies
sorry.
My docebo version is 3.6.0.3
Hi Riccardo. Welcome to E-Learning Heroes!
It looks like you're viewing the course in HTML5. Is that right? Do you have any options selected for modifying the browser window size for your course?
If so, you may want to take a look at the information below and the full chart for HTML5 support:
Articulate Support > Comparing Storyline's Flash, HTML5, and Articulate Mobile Player output
yes I'm using html5 version on Ipad.
Please note that If I setup storyline to create a launch page and open scorm in new window nothing changes.
The launch page doesn't appear. Is this a bug or I'm doing something wrong ? See my configuration in the image below.
If I change the manifest of the generated scorm in order to force loading the launch page, it works and the margin problems disappear. In this way everything seems to be ok. BUT......... my LMS (Docebo) stop tracking the course.
Any ideas ?
thanks
Hi Riccardo,
Hmm. Looks like it may be a combination of things. It may be best if we can take a look a the files and test it on our end. Are you able to share the project with us, so we can see what may be causing this? You'll be able to attach the .STORY file on the second page of the following form:
Articulate Support - Submit a Support Case
Please be sure to include a description of your issue. Please also include the URL for this thread in the form. Also, please share the case number with me. You're welcome to do so here, or in a private message. This way I can follow the progress of the case and update this thread.
Thanks!
case posted.
case number is
Normal 0 14 false false false oNotPromoteQF /> IT X-NONE X-NONE 00325635
thank you
Thanks Riccardo!
Looks like Sid is already working with you on this. I'll be sure to follow the progress.
Also, if you haven't received Sid's message, just let me know.
Any chance the solution to this issue could be posted, I believe I'm getting the same kind of resizing issue
Hi Lewis! I took a look at Riccardo's case for you and it was related to his LMS.
Have you tested your content in SCORM Cloud to see if you experience the same issue?
SCORM Cloud works well. The issue is we are using Docebo and it resizes the elearning player and content to be quite large. Can't seem to find a setting that changes this
Ah, thanks for the update. I'm not familiar with Docebo, so hopefully someone in the community will be able to chime in and assist here.
It seems I've figured a work around for it.
I think I just wasn't taking into account all the extra padding the player puts into the screen size.
Thanks for your help.
Thanks for the update Lewis. Glad to hear that you found a workable solution.
This discussion is closed. You can start a new discussion or contact Articulate Support.