This issue started when I tried to open a Cp 5 project in Cp 5.5. The animations don't play at all if the "Synchronize with Project" option is On and the anmiation starts at 0 sec on the timeline. Also, there is a visible "blink" between animations on the same slide and between slides.
I've been using Cp 5 for about a year and have worked out my issues with it so these are the things that AREN'T wrong: The transitions for slides and swfs are set to "No Transitions," there is no space between swfs on the timeline that would be making the "blink," there are no blank frames at the end of the timeline in the swf files(inside of Flash), the swfs are AS3, they are only as long as their original timeline, my Preferences are set to no fades on Start and End slides, and my timelines do not extend beyond their content to show white space.
The files work fine in Cp 5. The file animation links are also randomly missing/broken when brought into Cp 5.5 and even after I re-establish them, they periodically turn red (not up to date).
So I figured, "Maybe I can't work with previous version files. I'll just start a new blank project in Cp 5.5." Right? . . . Not right. Swfs still aren't visible when published if they are set to "Synchronize with Project" AND start at the 0 sec mark. They still "blink" between swfs and slides. So maybe I can't use Flash 5 files in Cp 5.5 either. If that is the case, this upgrade was a waste of time and money and should not have been released until these MAJOR issues were resolved.
Someone from support is looking into it, but so far the only advice that I got was "Turn the Sync option off and fade into your next animations." What?! The sync option is very important because that keeps your animations playing correctly when people scrub the playhead. If Cp 5.5 is programmed to do that automatically, then why keep the option button? If not, do you really expect me to NOT want my animations to play consistently when people drag around the playhead? As for the fading, maybe fading out after every animation swf is not an option for me, maybe I need it to be seamless. And to that I was told, "Put all your animations together in one Flash file." Duh, but that was how this needing Cp to assemble my separate swfs started in the first place. If any of you have tried importing 3D rendered pngs into Flash, you know that you can only have so many frames before the program can't handle the load and crashes. I can only support aoubt 250-300 frames of optimized pngs before Flash crashes on me and thats WITH 16GB of ram on a new 64 bit operating system.
If anyone has had this issue and found a fix or some kind of pending patch, please let me know, because by now, I'm wanting a refund.
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:
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.
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.
Europe, Middle East and Africa