Were you able to solve this issue?
I am currently encountering the same. I have upgraded my Captivate 4 (AS3) Project into Captivate 5.5 none of the publish setting is changed, preview it and all of a sudden none of the swf is working, which previously worked very well in version 4. Unchecking the "Synchronize to Project" makes things different, but unchecking it would result in my swfs flickering at the beginning and the end.
Upgrading project should't result on problems like this.
Or I might just be missing something.
Captivate 5 was a total rewrite from the Captivate 4 software architecture and it introduced a subtle but fundamental change in the way that Flash animations were handled in Captivate published content.
Basically the change means that if your animation was built down a level or two inside a symbol rather than on the main timeline at the top level, then you will find that Captivate 5 or 5.5 loads and executes the animation on the first slide of the movie. This means that by the time you get to the actual slide where you WANTED the animation to perform it's magic, it's already run and finished.
In Captivate 4 this did not happen. The animation was not really loaded until later in the movie timeline so as to be ready for the slide where it was required. It didn't matter if the animation was buried inside a symbol or not.
You have two choices:
- Revamp your animation so that it all happens on the main timeline in the Flash FLA file that generates it.
- Get your Flash programmer to add some ActionScript code to the animation so that it does NOT play completely when first loaded at the beginning of the project at runtime.
I agree that Captivate would have been regarded as less of a beast if this change had NOT been made, as users only find out about it AFTER upgrading projects with animations built as symbols. However, I have to trust that if the change was introduced, there must have been a very good reason.
Why can't you just use Loader in Flash to load your swfs, or ditch the IDE altogether and use Embed? It seems to me that this isn't a problem Captivate was made to solve.
Actually, Captivate 5 played the swfs fine, Captivate 5.5 loads them differently and the Adobe team had to give me a fix file to adjust the program code. So, Captivate 5.5 made this problem.
I noticed the timeline issue and that wasn’t the case. All the animations were on the main timeline. The issue was, and I had no way of knowing this, Captivate 5.5 loads swfs differently (one at a time when the timeline got to them) while Captivate 5 loaded the swfs at opening and waited to play them. So my “jumps” in between swfs and slides was 5.5 taking the time to load them individually. Adobe support had to give me fix file to adjust the program code.
Adobe support gave me a fix file. The issue was, and I had no way of knowing this, Captivate 5.5 loads swfs differently (one at a time when the timeline got to them) while Captivate 5 loaded the swfs at opening and waited to play them. So my “jumps” in between swfs and slides was 5.5 taking the time to load them individually.
You can get the fix file from here:
This contains a zip file named AnimationOnLoadFix.zip which contains the following files:
Following steps are needed in order to use the fix:
1. Close all instances of Adobe Captivate 5.5
2. Open Windows Explorer and go to Captivate installation folder (eg. C:\Program Files\Adobe\Adobe Captivate 5.5)
3. This folder already contains CPSWFGenerator.dll.
4. Please rename this file to CPSWFGenerator_old.dll.
5. Now extract AnimationOnLoadFix.zip and copy/paste files CPSWFGenerator.dll & StopOnDemandLoading.ini to the installation folder (eg. C:\Program Files\Adobe\Adobe Captivate 5.5)
6. Start Captivate 5.5 and check out your scenario.
Thank you very much, this is indeed a fix.
I wonder why Captivate Developer's do not have a documentation about this.
Could someone please direct me to a solution for this same issue on Mac?
You are going to have to contact the Bug Report specialists at Adobe. Fill out a bug report on the site and add the link that I posted. Ask them for the same thing, but formatted for a Mac.
Thanks asura_Bs for the reply. Will look into it.
We ran into the same problem. All we did was move the animation to 0.1 second on the timeline and it worked just fine. We kept the sync setting as well, which is imperative for us. Whew!
I have interjected a swf animation slide in between others in a Captivate 5.5 project.
I published it and put it up into our LMS.
When the project plays and arrives at the swf slide I slide the progress bar ahead to the end of the swf slide.
The slide goes white and then there's no way to progress further.
If I allow the swf slide to progress all the way through by itself it progresses fine.
Would the https://acrobat.com/#d=bPu41-v4vlKodjGuDDNB*Q file mentioned above help with this issue or do I need to do something different?
Also, where is this "sync" setting described above and should it be synced or not?