Scorm is a particular piece of code which has specific rules governing completion, and much of this is done when the scorm object is created.
It is entirely possible that you've got a scorm object which requires all pages to be viewed before completion is reported to Moodle, but you've also got it allowing users to skip pages in the navigation. In such a case a user will only complete if they view all pages, but could also achieve a score from the scorm object of 100% and still not be reported as complete, if they can skip ahead to the 'test' section in the scorm.
When testing, try to skip pages, or fail to open some hot spots (or reveals... whatever you like to call them), and see if you get a score... AND a completed status.
Try turning on the scorm debug mode in the site administration, and setting your username as the only person who sees it. When you then access a scorm object a new window will pop open - it's the scorm API showing you exactly what is written back to Moodle and what isn't.
But to answer your other point, yes, it is entirely possible that a network glitch is happening.
It is also possible for you to open the scorm object on the same page as the moodle course, or in a new window. It can make a difference as to which you choose... BUT, if your scorm object is created to ALSO open in a new window, you'll get two pop ups appearing. If your users don't like the 'clutter' on their page, and decide to close the one without the content, then all progress will NOT be reported to moodle - this is the scorm player window and must remain open.
Try using moodle to not open in a new window and see if the scorm pops out in a new window anyway - if it does then the scorm has been authored to do so, and can only be changed by re-authoring the scorm.
Closing the scorm player window would be a reason for not getting ANY data back to moodle... and yes, you can still see the scorm content in a new window if the scorm player window has closed. It'll just sit there and work, but not be able to communicate back to moodle.
Scorm is quite an old tool these days, but still very much in use. Moodle only fully works with version 1.2, and not 2004 (the latter has not got all the functionality).
Check to see if you are strictly using the scorm 1.2 standards too - this is also in the site admin under scorm settings. Check to allow it to 'break' the standard, as modern scorm objects tend to need a LOT more data space for things like the 'resume' feature. If you are strictly using 1.2, and your object is attempting to write back more data to moodle than is allowed, it will just fail.
As you can tell - there are many many ways scorm will not work. You need to be clear on how the scorm is authored, and just which settings in moodle will give it the best chance of working, before worrying about network glitches. When scorm works, it works really well, and the team have done a great job (IMO) of making it work at all.
It is entirely possible that you've got a scorm object which requires all pages to be viewed before completion is reported to Moodle, but you've also got it allowing users to skip pages in the navigation. In such a case a user will only complete if they view all pages, but could also achieve a score from the scorm object of 100% and still not be reported as complete, if they can skip ahead to the 'test' section in the scorm.
When testing, try to skip pages, or fail to open some hot spots (or reveals... whatever you like to call them), and see if you get a score... AND a completed status.
Try turning on the scorm debug mode in the site administration, and setting your username as the only person who sees it. When you then access a scorm object a new window will pop open - it's the scorm API showing you exactly what is written back to Moodle and what isn't.
But to answer your other point, yes, it is entirely possible that a network glitch is happening.
It is also possible for you to open the scorm object on the same page as the moodle course, or in a new window. It can make a difference as to which you choose... BUT, if your scorm object is created to ALSO open in a new window, you'll get two pop ups appearing. If your users don't like the 'clutter' on their page, and decide to close the one without the content, then all progress will NOT be reported to moodle - this is the scorm player window and must remain open.
Try using moodle to not open in a new window and see if the scorm pops out in a new window anyway - if it does then the scorm has been authored to do so, and can only be changed by re-authoring the scorm.
Closing the scorm player window would be a reason for not getting ANY data back to moodle... and yes, you can still see the scorm content in a new window if the scorm player window has closed. It'll just sit there and work, but not be able to communicate back to moodle.
Scorm is quite an old tool these days, but still very much in use. Moodle only fully works with version 1.2, and not 2004 (the latter has not got all the functionality).
Check to see if you are strictly using the scorm 1.2 standards too - this is also in the site admin under scorm settings. Check to allow it to 'break' the standard, as modern scorm objects tend to need a LOT more data space for things like the 'resume' feature. If you are strictly using 1.2, and your object is attempting to write back more data to moodle than is allowed, it will just fail.
As you can tell - there are many many ways scorm will not work. You need to be clear on how the scorm is authored, and just which settings in moodle will give it the best chance of working, before worrying about network glitches. When scorm works, it works really well, and the team have done a great job (IMO) of making it work at all.