The original SCORM spec's 1.n gave a file size for the transactions which was a bit on the small size. This is where all the variables are passed.When it was originally proposed bandwidth was a bit more precious than it is now.
This stayed pretty much unchanged through subsequent SCORM standards and does cause some issues. Some of the LMS coders changed it to be larger, some have such hacked systems, they grew from AICC and just tagged SCORM features on, that they can't adapt this without a major rewrite. Of course if you've already bought in to a commercial platform you are unikely to change vendors (it's called vendor lock-in, explains why so many people stick with flawed products). In this case the only recourse is to ask your supplier to fix it, which is honestly unlikely.
The work around or cure is only to pass the variables you need for recording results to the LMS and instead use local variables in the module itself which aren't limited.
This looks to be resolved in the SCORM 2.0 but the standard is a way from being pblished AND vendors will take a long time to update their products. Expect Moodle, Illias etc to have it available within 3 months of release and commercial platforms in years.
The original SCORM spec's 1.n gave a file size for the transactions which was a bit on the small size. This is where all the variables are passed.When it was originally proposed bandwidth was a bit more precious than it is now.
This stayed pretty much unchanged through subsequent SCORM standards and does cause some issues. Some of the LMS coders changed it to be larger, some have such hacked systems, they grew from AICC and just tagged SCORM features on, that they can't adapt this without a major rewrite. Of course if you've already bought in to a commercial platform you are unikely to change vendors (it's called vendor lock-in, explains why so many people stick with flawed products). In this case the only recourse is to ask your supplier to fix it, which is honestly unlikely.
The work around or cure is only to pass the variables you need for recording results to the LMS and instead use local variables in the module itself which aren't limited.
This looks to be resolved in the SCORM 2.0 but the standard is a way from being pblished AND vendors will take a long time to update their products. Expect Moodle, Illias etc to have it available within 3 months of release and commercial platforms in years.