I'm just wondering if this is expected behavior in SCORM 1.2.
I have a Storyline variable that tracks the playhead time of an embedded video. The first time I exit and resume the course, my time variable is retrieved correctly, but it appears that when I exit the course again, the time variable is not being updated in the LMS. When I resume the second time, the time variable still has its value from the first resume.
I using the latest version of Storyline 3.
Edit: I'm testing this in SCORM Cloud and the course works as expected when published to SCORM 2004, but has the problem above with SCORM 1.2.
Thank you for bringing this to our attention. Let's dig in!
Do you have a decimal point variable? I ask because we have an open issue in Storyline 3, where using a numeric variable that includes decimal points is reset upon resume.
If that doesn't match your condition, could you share your .story file with me for testing? You can use this private upload link. I'm eager to find what's causing this in SCORM 1.2!
Thank you for the response! I think you may have pinpointed the problem for me. Yes, I noticed that even though when exiting the course my variable value was 7.2, when the course resumed it would be 7, so that may well be the cause. I don't need to use decimals for this so I will round down the number to the nearest integer. Do you think that will solve my problem? Thanks!
4 Replies
Hi Michael!
Thank you for bringing this to our attention. Let's dig in!
Do you have a decimal point variable? I ask because we have an open issue in Storyline 3, where using a numeric variable that includes decimal points is reset upon resume.
If that doesn't match your condition, could you share your .story file with me for testing? You can use this private upload link. I'm eager to find what's causing this in SCORM 1.2!
Thank you for the response! I think you may have pinpointed the problem for me. Yes, I noticed that even though when exiting the course my variable value was 7.2, when the course resumed it would be 7, so that may well be the cause. I don't need to use decimals for this so I will round down the number to the nearest integer. Do you think that will solve my problem? Thanks!
Unfortunately that did not solve the problem. I'll upload the project file now for you to look at.
Good morning, Michael!
I appreciate you sending the file. Confirming receipt, and I'll be in touch in our case soon!
This discussion is closed. You can start a new discussion or contact Articulate Support.