Difference between published Captivate 5.5 swf and Captivate 7 swf?

Forum|Forum|12 years ago
October 9, 2013
3 replies
828 views

I have a custom SCORM framework built in Flash that handles all of the calls to an LMS, and I simply insert published SWFs from Captivate; everything has been working great for a few years now. The problem I am experiencing now is that content that I have published from Captivate 5.5 shows up just fine, but I upgraded to Captivate 7 and now the SWF files hang during loading, or simply show a black screen. My client uses SumTotal LMS, so I first thought it might be an issue with the LMS, but this is the case in every single LMS I have tested in, so it is definitely some anomaly in the different versions of the published files.

So I guess I am trying to figure out what is different between the two SWFs published in different versions?

This topic has been closed for replies.

W

wcampredocu

Inspiring

Did you ever find a solution to this issue?

RodWard

Community Expert

What issue are you facing specifically? The original poster of this thread had created their own framework and were not using all of the files Captivate created for SCORM support. Since the SCORM drivers changed from 5.5 to later Cp versions this broke their framework.

What is your issue?

N

Nader Omidian

Participant

I don't think so that it is the soulotion for this problem , but you in publish setting/ start and end part (something like this, I don't remember the name completely ) / you can turn off the preloader and fade in at start checkbox and turn on the autoplay.

this can solve the problem temporary till adobe find better way for it .

RodWard

Community Expert

Maybe the issue is that from Cp6 on Adobe introduced totally revamped SCORM drivers from Rustici. So your custom SCORM framework might not now be compatible with Cp7.

J

jdtartAuthor

Participant

I literally am using just the singular swf file, with none of the other support files that Cp7 spits out. I obviously have no clue what is built into that swf when published, but I am guessing that the API calls are in the swf itself?

RodWard

Community Expert

You are correct. Since the calls are being made to a different SCORM driver set, they would likely be different to before.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded