That does sound unusual as SCORM 2004 V4 should have solved issues with the suspend data exceeding 4096 characters. Have you been able to use the browser console to see what data the module is attempting to write to the LMS. I'm not sure if you are familiar with putting breaks in code via the console, if so, I'd recommend you put a break on the SetData function so you can see what is happening around slide 15.
I only ever see this kind of behaviour when a module has a large assessment and everything is set to resume. This can quickly bloat suspend data.
I'm happy to take a look at what is being written to suspend data if you are able to provide a version of the module (privately). Thanks, Sam.
Hi Sam, thank you for taking the time to respond. SCORM 2004 was not tracking progress at all when I tested it on SCORM CLOUD and not even sure my client's LMS can handle it.
In the end I have gone for a manual work around. The client did not want to force the learners to redo slides on revisiting, especially as some activities can take time. I have therefore set all slides to resume to initial state but added a completed slide variable to any slides that has an activity. This variable is then used to set the slide to 'complete' when they revisit.
As a bonus this means I could potentially add a reset slide to those slides, something I have always wanted.
I still think there is a bug somewhere in SL360 as it makes no sense that it should exceed the limit after only 15 slides.
That being said, I've turned on Debug window, but I am curious to hear more about using the browser console to highlight potential issues? Or is that the same thing?
