Skip navigation
asura_Bs
asura_Bs
Currently Being Moderated

Animations imported into Captivate 5.5 not playing correctly.

Oct 6, 2011 11:39 AM

Tags: #publishing #not #version #working #files #library #links #visible #captivate #5.5 #in #upgrade #glitches #bugs #problems #broken #previous #swfs #5 #animations #projects #correctly #disappearing

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.

3962 Views   12 Replies   Latest reply: Michelle Lasure, Jan 12, 2012 6:52 AM
 
Replies
  • salvador_sorianojr
    Currently Being Moderated
    1. salvador_sorianojr,
    Nov 3, 2011 11:35 PM   in reply to asura_Bs
    Report

    Hi!

    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.

     

     

    BR

    -Miguel

     
    |
    Mark as:
  • RodWard
    Currently Being Moderated
    2. RodWard,
    Nov 3, 2011 11:59 PM   in reply to salvador_sorianojr
    Report

    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:

    1. Revamp your animation so that it all happens on the main timeline in the Flash FLA file that generates it.
    2. 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.

     
    |
    Mark as:
  • Amy Blankenship
    Currently Being Moderated
    3. Amy Blankenship,
    Nov 4, 2011 5:39 AM   in reply to asura_Bs
    Report

    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.

     
    |
    Mark as:
  • asura_Bs
    Currently Being Moderated
    4. asura_Bs,
    Nov 4, 2011 6:59 AM   in reply to Amy Blankenship
    Report

    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.

     
    |
    Mark as:
  • asura_Bs
    Currently Being Moderated
    5. asura_Bs,
    Nov 4, 2011 7:03 AM   in reply to RodWard
    Report

    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.

     
    |
    Mark as:
  • asura_Bs
    Currently Being Moderated
    6. asura_Bs,
    Nov 4, 2011 7:05 AM   in reply to salvador_sorianojr
    Report

    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:

    https://acrobat.com/#d=bPu41-v4vlKodjGuDDNB*Q

     

    This contains a zip file named AnimationOnLoadFix.zip which contains the following files:

    a) CPSWFGenerator.dll

    b) StopOnDemandLoading.ini

     

    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.

     
    |
    Mark as:
  • salvador_sorianojr
    Currently Being Moderated
    7. salvador_sorianojr,
    Nov 13, 2011 10:24 PM   in reply to asura_Bs
    Report

    Thank you very much, this is indeed a fix.

    I wonder why Captivate Developer's do not have a documentation about this.

     
    |
    Mark as:
  • jkafkaris
    Currently Being Moderated
    8. jkafkaris,
    Dec 3, 2011 4:03 AM   in reply to asura_Bs
    Report

    Could someone please direct me to a solution for this same issue on Mac?

     

    Thanks,

    jk

     
    |
    Mark as:
  • asura_Bs
    Currently Being Moderated
    9. asura_Bs,
    Dec 5, 2011 6:28 AM   in reply to jkafkaris
    Report

    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.

     
    |
    Mark as:
  • jkafkaris
    Currently Being Moderated
    10. jkafkaris,
    Dec 8, 2011 12:10 PM   in reply to asura_Bs
    Report

    Thanks asura_Bs for the reply.  Will look into it.

     
    |
    Mark as:
  • Jim Leichliter
    Currently Being Moderated
    11. Jim Leichliter,
    Dec 9, 2011 10:40 AM   in reply to asura_Bs
    Report

    Someone else had a similar issue but posted in a different forum.  I'm adding a cross reference here:

    http://forums.adobe.com/message/4051322#4051322

     

    Jim Leichliter

     
    |
    Mark as:
  • Michelle Lasure
    Currently Being Moderated
    12. Michelle Lasure,
    Jan 12, 2012 6:52 AM   in reply to asura_Bs
    Report

    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!

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points